How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

HubSpot Marketing Transactional Single Send API

HubSpot Marketing Transactional Single Send — 6 operation(s) from HubSpot's published OpenAPI.

HubSpot Marketing Transactional Single Send API is one of 144 APIs that HubSpot publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 692 JSON Schema definitions.

Tagged areas include Marketing, Transactional, Single, and Send. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, code examples, and 692 JSON Schemas.

This API exposes 6 operations across 4 paths, organized into 2 resource areas, and defines 11 schemas. It is described by OpenAPI 3.0.1, at version 2026-09.

Requests are made against a single base URL, https://api.hubapi.com.

6 operations 4 paths 11 schemas 1 DELETE2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
2026-09
Base URL
https://api.hubapi.com
Authentication
API Key, OAuth 2.0, API Key, API Key
Resource Areas
2

Authentication & Security 4

HubSpot Marketing Transactional Single Send API declares 4 security schemes for authenticating requests. An API key is passed in the query as hapikey (developer_hapikey). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope. An API key is passed in the header as private-app (private_apps). An API key is passed in the header as private-app-legacy (private_apps_legacy).

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 3 POST. They span 2 resource areas: Send transactional email, SMTP Tokens. Each is listed below with its method, path, parameters, and response codes.

Send transactional email 1
POST
/marketing/transactional/2026-09/single-email/send
Send a single send transactional email asynchronously.
post-/marketing/transactional/2026-09/single-email/send_sendEmail body → 200default
SMTP Tokens 5
GET
/marketing/transactional/2026-09/smtp-tokens
Query SMTP API tokens by campaign name or an emailCampaignId.
get-/marketing/transactional/2026-09/smtp-tokens_getTokensPage 4 params → 200default
POST
/marketing/transactional/2026-09/smtp-tokens
Create a SMTP API token.
post-/marketing/transactional/2026-09/smtp-tokens_createToken body → 201default
GET
/marketing/transactional/2026-09/smtp-tokens/{tokenId}
Query a single token by ID.
get-/marketing/transactional/2026-09/smtp-tokens/{tokenId}_getTokenById 1 param → 200default
DELETE
/marketing/transactional/2026-09/smtp-tokens/{tokenId}
Delete a single token by ID.
delete-/marketing/transactional/2026-09/smtp-tokens/{tokenId}_archiveToken 1 param → 204default
POST
/marketing/transactional/2026-09/smtp-tokens/{tokenId}/password-reset
Reset the password of an existing token.
post-/marketing/transactional/2026-09/smtp-tokens/{tokenId}/password-reset_resetPassword 1 param → 200default

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are EmailSendStatusView (8 properties), Error (7 properties), SmtpApiTokenView (7 properties), PublicSingleSendEmail (6 properties). Each schema is shown below with its type and property counts.

CollectionResponseSmtpApiTokenViewForwardPaging
object
2 properties 1 required
EmailSendStatusView
object
8 properties 2 required
Error
object
Represents an error response returned by the API when an operation fails. This component is used in various endpoints to provide detailed information about the…
7 properties 3 required
ErrorDetail
object
Represents detailed information about an error that occurred in the API. This component is used to provide additional context and specifics about errors, typic…
5 properties 1 required
EventIdView
object
2 properties 2 required
ForwardPaging
object
Paging information for forward-only pagination. Contains the next page reference when more results are available; omitted or empty on the last page.
1 property
NextPage
object
Specifies the paging information needed to retrieve the next set of results in a paginated API response
2 properties 1 required
PublicSingleSendEmail
object
6 properties 3 required
PublicSingleSendRequestEgg
object
4 properties 4 required
SmtpApiTokenRequestEgg
object
2 properties 2 required
SmtpApiTokenView
object
7 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hubspot-marketing-transactional-single-send-api-openapi.yml Raw ↑

Other APIs HubSpot publishes across the network.

HubSpot URL Redirects API
HubSpot Pipelines API
HubSpot Products API
HubSpot Line Items API
HubSpot Quotes API
HubSpot CRM Properties API
HubSpot Owners API
HubSpot CRM Imports API
HubSpot Custom Objects API
HubSpot Marketing Events API
HubSpot Forms API
HubSpot Workflows API
Where this information came from

This is an independent, third-party profile of HubSpot Marketing Transactional Single Send API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.