Skip to content

HubSpot: Transactional email schemas

6 HubSpot schemas with complete fields and constraints.

← Transactional email operations · All schemas

Create a SMTP API token — request body — body

FieldTypePresenceDescription and constraints
$objectRoot
campaignNamestringRequired within parentA name for the campaign tied to the SMTP API token.
createContactbooleanRequired within parentIndicates whether a contact should be created for email recipients.

Create a SMTP API token — response body

FieldTypePresenceDescription and constraints
$objectRoot
campaignNamestringRequired within parentA name for the campaign tied to the token.
createContactbooleanRequired within parentIndicates whether a contact should be created for email recipients.
createdAtstringRequired within parentTimestamp generated when a token is created.
Format: date-time
createdBystringRequired within parentEmail address of the user that sent the token creation request.
emailCampaignIdstringRequired within parentIdentifier assigned to the campaign provided in the token creation request.
idstringRequired within parentUser name to log into the HubSpot SMTP server.
passwordstringOptionalPassword used to log into the HubSpot SMTP server.

Query SMTP API tokens by campaign name or an email Campaign Id — response body

FieldTypePresenceDescription and constraints
$objectRoot
pagingModelOptionalExpand Query SMTP API tokens by campaign name or an email Campaign Id — response body — paging
resultsarrayRequired within parentAn array of SMTP API token objects, each representing a token with its associated details.
results[]ModelEach itemExpand Create a SMTP API token — response body

Referenced models: Create a SMTP API token — response body, Query SMTP API tokens by campaign name or an email Campaign Id — response body — paging

Query SMTP API tokens by campaign name or an email Campaign Id — 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 Query SMTP API tokens by campaign name or an email Campaign Id — response body — paging next

Referenced models: Query SMTP API tokens by campaign name or an email Campaign Id — response body — paging next

Query SMTP API tokens by campaign name or an email Campaign Id — 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 used to retrieve the next page of results. It indicates the position after the last item on the current page.
linkstringOptionalA string containing the URL link to the next page of results.

Send a single send transactional email asynchronously — request body — body

FieldTypePresenceDescription and constraints
$objectRoot
contactPropertiesobjectRequired within parentThe contactProperties field is a map of contact property values. Each contact property value contains a name and value property. Each property will get set on the contact record and will be visible in the template under {{ contact.NAME }}. Use these properties when you want to set a contact property while you’re sending the email. For example, when sending a reciept you may want to set a last_paid_date property, as the sending of the receipt will have information about the last payment.
Additional keys: see wildcard field
contactProperties.*stringAdditional keys
customPropertiesobjectRequired within parentThe customProperties field is a map of property values. Each property value contains a name and value property. Each property will be visible in the template under {{ custom.NAME }}.
Note: Custom properties do not currently support arrays. To provide a listing in an email, one workaround is to build an HTML list (either with tables or ul) and specify it as a custom property.
Additional keys: see wildcard field
customProperties.*objectAdditional keys
emailIdintegerRequired within parentThe content ID for the transactional email, which can be found in email tool UI.
Format: int64
messageModelRequired within parentExpand Send an email — request body — body message

Referenced models: Send an email — request body — body message

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.