Skip to content

HubSpot: Batch create objects — postal Mail batch Create Postal Mail

HubSpot postalMail.batchCreatePostalMail: arguments, response, policy and SDK examples.

← Postal mail operations · Get started

Operation hubspot.postal_mail_batch_create_postal_mail

Provider route: POST /crm/objects/2026-09/postal_mail/batch/create. 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["postalMail"]["batchCreatePostalMail"]>[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.postalMail.batchCreatePostalMail(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.postal_mail.batch_create_postal_mail(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
bodyModelRequired within parentExpand Batch create objects — postal Mail batch Create Postal Mail — request body — body

Referenced models: Batch create objects — postal Mail batch Create Postal Mail — 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
$JSONRoot
$ (anyOf 1)ModelAlternativeExpand Read batch objects — postalMail.batchGetPostalMail — response body — status: CANCELED, COMPLETE, PENDING, PROCESSING — Postal Mail Batch Response Simple Public Object
$ (anyOf 2)ModelAlternativeExpand Read batch objects — postalMail.batchGetPostalMail — response body — status: CANCELED, COMPLETE, PENDING, PROCESSING — Postal Mail Batch Response Simple Public Object With Errors

Referenced models: Read batch objects — postalMail.batchGetPostalMail — response body — status: CANCELED, COMPLETE, PENDING, PROCESSING — Postal Mail Batch Response Simple Public Object, Read batch objects — postalMail.batchGetPostalMail — response body — status: CANCELED, COMPLETE, PENDING, PROCESSING — Postal Mail Batch Response Simple Public Object With Errors

5 more schemas are linked from the tables above, on the schema pages.

Read batch objects — postalMail.batchGetPostalMail — response body — status: CANCELED, COMPLETE, PENDING, PROCESSING — Postal Mail Batch Response Simple Public Object
FieldTypePresenceDescription and constraints
$objectRootA public object batch response object
completedAtstringRequired within parentThe date and time when the batch operation was completed, in ISO 8601 format.
Format: date-time
linksobjectOptionalA map of link names to associated URIs, providing additional information or actions related to the batch operation.
Additional keys: see wildcard field
links.*stringAdditional keys
requestedAtstringOptionalThe date and time when the batch operation was requested, in ISO 8601 format.
Format: date-time
resultsarrayRequired within parentAn array of SimplePublicObject items that represent the results of the batch operation.
results[]ModelEach itemExpand Merge objects — postal Mail merge — 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: Merge objects — postal Mail merge — response body

Read batch objects — postalMail.batchGetPostalMail — response body — status: CANCELED, COMPLETE, PENDING, PROCESSING — Postal Mail Batch Response Simple Public Object With Errors
FieldTypePresenceDescription and constraints
$objectRootRepresents the result of a batch operation on CRM objects, including the processing status, batch results, timestamps, and a list of any errors encountered during the operation.
completedAtstringRequired within parentThe date and time when the batch operation was completed, in ISO 8601 format.
Format: date-time
errorsarrayOptionalAn array of errors that occurred during the batch operation, each represented as a StandardError.
errors[]ModelEach itemExpand Read batch objects — postalMail.batchGetPostalMail — response body — status: CANCELED, COMPLETE, PENDING, PROCESSING errors item
linksobjectOptionalA map of link names to associated URIs related to the batch operation.
Additional keys: see wildcard field
links.*stringAdditional keys
numErrorsJSONOptional
numErrors (anyOf 1)integerAlternativeThe number of errors that occurred 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 results from the batch operation, each represented as a SimplePublicObject.
results[]ModelEach itemExpand Merge objects — postal Mail merge — 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: Merge objects — postal Mail merge — response body, Read batch objects — postalMail.batchGetPostalMail — response body — status: CANCELED, COMPLETE, PENDING, PROCESSING errors item

Batch create objects — postal Mail batch Create Postal Mail — request body — body
FieldTypePresenceDescription and constraints
$objectRootRepresents a batch input for creating multiple simple public objects in a single request. This component is used to streamline the process of adding new objects to a HubSpot account by allowing multiple entries to be created at once.
inputsarrayRequired within parentAn array of objects, each containing the properties and associations necessary to create a simple public object. Each item in the array is of type SimplePublicObjectBatchInputForCreate.
inputs[]ModelEach itemExpand Batch create objects — postal Mail batch Create Postal Mail — request body — body inputs item

Referenced models: Batch create objects — postal Mail batch Create Postal Mail — request body — body inputs item

Merge objects — postal Mail merge — response body
FieldTypePresenceDescription and constraints
$objectRootA simple public object.
archivedbooleanRequired within parentA boolean indicating whether the object is archived.
archivedAtstringOptionalThe date and time when this object was archived, in ISO 8601 format.
Format: date-time
createdAtstringRequired within parentThe date and time when this object was created, in ISO 8601 format.
Format: date-time
idstringRequired within parentThe unique identifier for this object, represented as a string.
objectWriteTraceIdstringOptionalAn identifier used to trace the creation or update request of the CRM object.
propertiesobjectRequired within parentA map of property names to their values, where each value is a string.
Additional keys: see wildcard field
properties.*stringAdditional keys
propertiesWithHistoryobjectOptionalA map of property names to arrays of their historical values, each entry containing a value and its timestamp.
Additional keys: see wildcard field
propertiesWithHistory.*arrayAdditional keys
propertiesWithHistory.*[]ModelEach itemExpand Merge objects — postal Mail merge — response body — properties With History value item
updatedAtstringRequired within parentThe date and time when this object was last updated, in ISO 8601 format.
Format: date-time
urlstringOptionalA string representing the URL of the object.
warningsarrayOptionalAn array of warnings related to the object, each containing a category, message, and context.
warnings[]ModelEach itemExpand Merge objects — postal Mail merge — response body — warnings item

Referenced models: Merge objects — postal Mail merge — response body — warnings item, Merge objects — postal Mail merge — response body — properties With History value item

Read batch objects — postalMail.batchGetPostalMail — response body — status: CANCELED, COMPLETE, PENDING, PROCESSING errors item
FieldTypePresenceDescription and constraints
$objectRootRepresents a standard error response in the HubSpot API, providing detailed information about an error that occurred during an API request.
categorystringRequired within parentA string that categorizes the error.
contextobjectRequired within parentAn object containing additional context about the error, 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 individual errors.
errors[]ModelEach itemExpand Batch insert events — response body — errors item errors item
idstringOptionalA string representing the unique identifier for the error.
linksobjectRequired within parentAn object mapping link names to associated URIs that provide 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 that provides more specific categorization of the error.

Referenced models: Batch insert events — response body — errors item errors item

Batch create objects — postal Mail batch Create Postal Mail — request body — body inputs item
FieldTypePresenceDescription and constraints
$objectRootAn input object that contains a collection of objects to be created together in a batch.
associationsarrayRequired within parentAn array of objects defining the associations between the CRM objects being created and other existing objects. Each association specifies the target object and the type of association.
associations[]ModelEach itemExpand Create — postal Mail create Postal Mail — request body — body associations item
objectWriteTraceIdstringOptionalA string identifier used to trace the write operations for the objects being created. This is optional and can be used for tracking purposes.
propertiesobjectRequired within parentAn object containing key-value pairs where keys are property names and values are the corresponding property values for the CRM objects being created.
Additional keys: see wildcard field
properties.*stringAdditional keys

Referenced models: Create — postal Mail create Postal Mail — request body — body associations item

Archive a batch of contacts — request body — body inputs item
FieldTypePresenceDescription and constraints
$objectRootContains the Id of a Public Object
idstringRequired within parentThe unique identifier for the object, represented as a string.

SDK function policy ID: hubspot.postal_mail_batch_create_postal_mail. Catalog operation: postal_mail_batch_create_postal_mail. 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: ["crm.objects.contacts.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.