Skip to main content
POST
Launch a package from a template

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

x-workspace-id
string

The workspace the key was issued for, as returned by GET /api/v1/workspaces. Optional: omitting it acts in the key's workspace, and any other id is rejected with 401.

Body

application/json
templateId
string
required

The id of the template to launch.

Minimum string length: 1
Example:

"K7dQm2xPz9Lw"

recipients
object[]
required

One recipient per template role. At least one and at most 100.

Required array length: 1 - 100 elements
externalId
string

Your own reference for the package, up to 255 characters and unique within the organisation. Repeating it returns the existing package instead of creating another, and sends it when it is still a DRAFT and status is "sent", so a retry after a failed send completes it.

Required string length: 1 - 255
Example:

"crm-deal-48213"

status
enum<string>
default:draft

"draft" leaves the package unsent; "sent" dispatches it to recipients immediately. Defaults to "draft".

Available options:
draft,
sent
Example:

"sent"

scheduledAt
string<date-time>

An ISO 8601 time to send the package automatically. Leaves it SCHEDULED, and cannot be combined with status: "sent".

Example:

"2026-10-01T20:00:00.000Z"

fields
object

Merge field values keyed by merge field key. Each is checked against its field's type and list options, and a bad or missing required value is rejected with 422 under fields.<key>. A blank value takes the field's default. Keys the template does not ask the sender for are rejected under unknownFields.

Example:
workflowAnswers
object

The sender's answers to the template's workflow questions, keyed by question id. port names the picked answer for a choice question; value carries the typed input for an open one. Omit it when nothing branches: only the default documents are included.

Example:
documentAnswers
object

Answers to the questions the template's documents ask, keyed by document id and then question id, so two documents asking a question with the same id are answered apart. They decide which conditional content each document includes. A document question the workflow also asks is answered once, here or in workflowAnswers; giving it two different answers is refused.

Example:
metadata
object

Custom field values keyed by custom field key, set over the template's defaults. Every key must be a live custom field that applies to this package. An empty string clears a value. Unknown keys are rejected with 422, and so are missing required values when the package is sent or scheduled.

Example:

Response

Success

data
object
required