Skip to main content
POST
Drip (bulk shock-absorber)
Use this instead of POST /api/messages for bulk sends (HubSpot/CRM parallel enrollment, list blasts). Same request body — change only the URL. It never 429s a blast, acks 202 immediately, and drips the sends out safely per line. Full guide: Drip.

Authentication

Pass your workspace API key as a Bearer token (same key as /api/messages).

How it differs from /api/messages

  • Not rate-limited — exempt from the 60/min send limit; a bulk blast is never rejected.
  • Always 202 — the request is buffered and the message is created a moment later, then sent still later (paced per line by the ban protector: ~7 new/hr, ~50 new/day, 150 total/day).
  • Response is 202 { status, correlationId, scheduledDate, jitterMs } — no messageId (the message doesn’t exist yet at ack time); use correlationId to correlate in your webhooks.
  • Idempotency-Key header is honored (HubSpot retries return the first ack).
For low-volume, send-now traffic where you want the real delivery status back immediately, use POST /api/messages instead.