Batches - TIKT

With the Batches format (set under More options when you create a destination), TIKT groups the events it has for you and sends up to 100 per request. It saves requests when a cycle finds many leads at once; n8n and your own code handle it well. Zapier, Make, Clay and Slack prefer one request per event.

The batch envelope

A batch has the same envelope as an event, with type set to batch and the events in data.events:

{
  "id": "5f2c0d8e-7a6b-4c1d-9e3f-0a1b2c3d4e5f",
  "type": "batch",
  "created_at": "2026-10-06T20:04:10Z",
  "api_version": "2026-10-01",
  "workspace_id": "6c1f0e2a-9b8d-4e7f-8a6b-5c4d3e2f1a0b",
  "data": {
    "events": [
      { "id": "…", "type": "lead.created", "created_at": "2026-10-06T20:03:41Z", "api_version": "2026-10-01", "workspace_id": "…", "data": { "…": "…" } },
      { "id": "…", "type": "lead.engaged_again", "created_at": "2026-10-06T20:03:44Z", "api_version": "2026-10-01", "workspace_id": "…", "data": { "…": "…" } }
    ]
  }
}

Field	Meaning
`id`	The batch’s identifier. It is also its `webhook-id`, the same on every attempt.
`created_at`	When the batch was sent.
`data.events`	From 1 to 100 events, each a complete event envelope, in the order TIKT wrote them.

The x-tikt-event header says batch.

Good to know

A batch is delivered, retried and resent as a whole. If your endpoint fails on one event of the batch, answer with an error: the whole batch comes back.
A batch heavier than 5 MB is split in two before it is first sent. Each half is a batch with its own id.
The same event is never in two batches for the same destination. Like single events, a batch can arrive twice (after a timeout): use its id — or each event’s id — to ignore a duplicate.