API-Triggered Sequences

POST /api/v1/sequences/:id/execute

• Auth: API key
• Required scope: sequences:execute
• Body accepts contact objects (email-first payload)
• Limit: up to 100 contacts per request

POST /api/sequences/:id/execute

• Auth: signed-in app session
• Body accepts existing contactIds
• Limit: up to 500 contacts per request

curl -X POST "https://your-domain.com/api/v1/sequences/SEQUENCE_ID/execute" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "contacts": [
      {
        "email": "customer@example.com",
        "firstName": "Jane",
        "lastName": "Doe",
        "phone": "+15551234567"
      }
    ]
  }'

Execution is blocked when:

• Sequence is not Active
• Sequence has no steps
• All submitted contacts are invalid/unsubscribed

If A/B testing is enabled and configured, API enrollment can split traffic between Sequence A and Variant B based on your configured percentage.

For setup details, see A/B Testing Sequences.

• Start with 1-3 test contacts before bulk execution
• Ensure your sequence includes at least one deterministic first step
• Include monitoring around API errors and retry logic in your integration layer
• Keep contact identity consistent (same email/phone formatting)