Skip to content

HubSpot: Batch assign members

HubSpot teams.batchAddTeamMembers: arguments, response, policy and SDK examples.

← Teams operations · Get started

Operation hubspot.teams_batch_add_team_members

Provider route: POST /settings/teams/2026-09/{teamId}/members/batch. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/hubspot with npm, or alter-sdk-hubspot with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { HubSpotIntegration } from "@alter-ai/hubspot";
async function execute(input: Parameters<HubSpotIntegration["teams"]["batchAddTeamMembers"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new HubSpotIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.teams.batchAddTeamMembers(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_hubspot import HubSpotIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = HubSpotIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.teams.batch_add_team_members(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
pathobjectRequired within parentAdditional keys: not allowed
path.teamIdstringRequired within parent
bodyModelRequired within parentExpand Batch assign members — request body — body

Referenced models: Batch assign members — request body — body

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Batch assign members — response body

Referenced models: Batch assign members — response body

Batch assign members — request body — body
FieldTypePresenceDescription and constraints
$objectRoot
inputsarrayRequired within parentAn array of team member assignments, where each item specifies the details of a team member to be assigned. Each item is of type 'TeamMemberAssignment'.
inputs[]ModelEach itemExpand Add Team Members — request body — body

Referenced models: Add Team Members — request body — body

Batch assign members — response body
FieldTypePresenceDescription and constraints
$objectRoot
completedAtstringRequired within parentThe date and time when the batch operation was completed, in ISO 8601 format.
Format: date-time
errorsarrayOptionalAn array of StandardError objects detailing any errors that occurred during the batch operation.
errors[]ModelEach itemExpand Batch assign members — response body — errors item
linksobjectOptionalA map of link names to associated URIs providing additional information about the batch operation.
Additional keys: see wildcard field
links.*stringAdditional keys
numErrorsJSONOptional
numErrors (anyOf 1)integerAlternativeThe number of errors encountered during the batch operation.
Format: int32
numErrors (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
requestedAtstringOptionalThe date and time when the batch operation was requested, in ISO 8601 format.
Format: date-time
resultsarrayRequired within parentAn array of TeamMemberResponse objects representing the results of the batch operation.
results[]ModelEach itemExpand Add Team Members — response body
startedAtstringRequired within parentThe date and time when the batch operation started, in ISO 8601 format.
Format: date-time
statusstringRequired within parentThe current status of the batch operation. Valid values include 'PENDING', 'PROCESSING', 'CANCELED', and 'COMPLETE'.
Known values: CANCELED, COMPLETE, PENDING, PROCESSING

Referenced models: Add Team Members — response body, Batch assign members — response body — errors item

Add Team Members — request body — body
FieldTypePresenceDescription and constraints
$objectRoot
typestringRequired within parentThe type of team member assignment. It is a string and can be either 'DEFAULT' or 'EXTRA'.
One of: DEFAULT, EXTRA
userIdstringRequired within parentThe unique identifier for the user being assigned to the team. It is a string.
Add Team Members — response body
FieldTypePresenceDescription and constraints
$objectRoot
typestringRequired within parentThe type of membership the user has in the team. Valid values are 'DEFAULT' and 'EXTRA'.
Known values: DEFAULT, EXTRA
userIdstringRequired within parentThe unique identifier for the user, represented as a string.
Batch assign members — response body — errors item
FieldTypePresenceDescription and constraints
$objectRootYe olde error
categorystringRequired within parentA string representing the category of the error.
contextobjectRequired within parentAn object containing additional context about the error condition, with keys as context names and values as arrays of strings.
Additional keys: see wildcard field
context.*arrayAdditional keys
context.*[]stringEach item
errorsarrayRequired within parentAn array of ErrorDetail objects providing further information about the error.
errors[]ModelEach itemExpand Batch assign members — response body — errors item errors item
idstringOptionalA string that uniquely identifies the error instance.
linksobjectRequired within parentAn object mapping link names to associated URIs that contain documentation or recommended remediation steps for the error.
Additional keys: see wildcard field
links.*stringAdditional keys
messagestringRequired within parentA string containing a human-readable message describing the error.
statusstringRequired within parentA string indicating the status of the error.
subCategoryobjectOptionalAn object providing more specific details about the error category.

Referenced models: Batch assign members — response body — errors item errors item

Batch assign members — response body — errors item errors item
FieldTypePresenceDescription and constraints
$objectRootRepresents detailed information about an error that occurred in the API. This component is used to provide additional context and specifics about errors, typically as part of an error response.
codestringOptionalThe status code associated with the error detail.
contextobjectOptionalContext about the error condition, represented as an object with additional properties that are arrays of strings.
Additional keys: see wildcard field
context.*arrayAdditional keys
context.*[]stringEach item
instringOptionalThe name of the field or parameter in which the error was found.
messagestringRequired within parentA human readable message describing the error along with remediation steps where appropriate. This is a required field.
subCategorystringOptionalA specific category that contains more specific detail about the error.

SDK function policy ID: hubspot.teams_batch_add_team_members. Catalog operation: teams_batch_add_team_members. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Required provider scopes: ["settings.users.teams.write"]

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.