Skip to main content
POST
Start sequence blueprint

First time? Set up Authentication

Learn how to authenticate your API requests with your API key.
Starts a dynamic outreach sequence workflow for the given blueprint and candidate ids. The blueprint must belong to a sourcing in your workspace and should contain valid steps created with Create sequence blueprint or Update sequence blueprint.

Path parameters

string
required
Sequence blueprint id to start.

Request body

array
required
Candidate ids to enroll in the sequence. The array must contain at least one id.

Response

When success is true, data contains:
  • started — whether the workflow was dispatched
  • blueprintId — started blueprint id
  • candidateCount — number of candidates requested
Poll progress with Get candidate dynamic sequence status using each candidateId.

Prerequisites

  • The blueprint must have at least one valid step.
  • Every candidateId must belong to the same sourcing as the blueprint.
  • Required outreach channels must be connected and synced in Kalent.
  • LinkedIn steps require a connected LinkedIn account.
  • WhatsApp steps require a connected WhatsApp account.
  • Email steps require a connected Gmail, Outlook, or IMAP account.

LinkedIn InMail sender

A LinkedIn InMail step without a chosen sender is sent from the LinkedIn account of the user who owns the API key. An InMail sender already chosen in Kalent is always kept. The blueprint itself is not modified. That user must have a synced LinkedIn account with InMail capability (Recruiter or Sales Navigator). Otherwise the start fails with linkedin_not_connected_or_syncing or linkedin_inmail_not_available in error.details.code.
The default sender is the owner of the API key. If several people share one key, InMails go out from the key owner’s LinkedIn account.

Errors

For forbidden errors caused by missing or disconnected outreach accounts, error.details.code indicates the blocked provider, such as linkedin_not_connected_or_syncing, whatsapp_not_connected_or_syncing, or email_not_connected_or_syncing. When the workspace plan does not include outreach integrations, the API returns plan_upgrade_required with billing remediation details: