> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tuco.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Drip (bulk shock-absorber)

> Same body as POST /api/messages, built for bulk/bursty CRM enrollment fan-out — never 429s, fast-acks 202, drips out safely per line. Bearer-token auth, JSON.

<Note>
  Use this instead of [`POST /api/messages`](/api-reference/endpoint/send-message)
  for **bulk** sends (HubSpot/CRM parallel enrollment, list blasts). **Same request
  body — change only the URL.** It never `429`s a blast, acks `202` immediately, and
  drips the sends out safely per line. Full guide: [Drip](/api-reference/drip).
</Note>

## Authentication

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

```bash theme={null}
Authorization: Bearer tuco_sk_xxxxxxxxxxxxx
```

## 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).

<Tip>
  For **low-volume, send-now** traffic where you want the real delivery status back
  immediately, use [`POST /api/messages`](/api-reference/endpoint/send-message)
  instead.
</Tip>