Skip to content

HubSpot: Teams schemas

13 HubSpot schemas with complete fields and constraints.

← Teams operations · All schemas

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 — 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

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.

Create Team — request body — body

FieldTypePresenceDescription and constraints
$objectRoot
membersarrayRequired within parentAn array of team members to be assigned to the new team. Each member is represented by a TeamMemberAssignment object. This is a required field.
members[]ModelEach itemExpand Add Team Members — request body — body
namestringRequired within parentThe name of the team to be created. This is a required field and must be a string.
parentTeamIdstringOptionalThe unique identifier of the parent team, if the new team is a sub-team. This is an optional field and must be a string if provided.

Referenced models: Add Team Members — request body — body

Create Team — response body

FieldTypePresenceDescription and constraints
$objectRoot
idstringRequired within parentThe unique identifier for the team, represented as a string.
namestringRequired within parentThe name of the team, represented as a string.
parentTeamIdstringOptionalThe unique identifier of the parent team, if applicable, represented as a string.

List members — response body

FieldTypePresenceDescription and constraints
$objectRoot
pagingModelOptionalExpand List teams — response body — paging
resultsarrayRequired within parentAn array of team member responses, each represented by a TeamMemberResponse object.
results[]ModelEach itemExpand Add Team Members — response body

Referenced models: Add Team Members — response body, List teams — response body — paging

List teams — response body

FieldTypePresenceDescription and constraints
$objectRoot
pagingModelOptionalExpand List teams — response body — paging
resultsarrayRequired within parentAn array of team responses, each representing a team object.
results[]ModelEach itemExpand Create Team — response body

Referenced models: Create Team — response body, List teams — response body — paging

List teams — response body — paging

FieldTypePresenceDescription and constraints
$objectRootPaging information for forward-only pagination. Contains the next page reference when more results are available; omitted or empty on the last page.
nextModelOptionalExpand List teams — response body — paging next

Referenced models: List teams — response body — paging next

List teams — response body — paging next

FieldTypePresenceDescription and constraints
$objectRootSpecifies the paging information needed to retrieve the next set of results in a paginated API response
afterstringRequired within parentA string token representing the cursor position after the last successfully read resource. This is used to fetch the next set of results.
linkstringOptionalA string URL that provides the direct link to the next page of results.

Update team — request body — body

FieldTypePresenceDescription and constraints
$objectRoot
nameobjectRequired within parentAn object representing the new name for the team.
parentTeamIdobjectRequired within parentAn object representing the ID of the parent team to which this team will be associated.

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.