Skip to main content
Send a batch of events with one request. Each event uses the same fields as POST /capture-event. Tensile reports each row’s outcome so you can retry rejected events without resending accepted ones.

Headers

Body

The body contains an events array. Each event must include event_id and session_id; other event fields are described in the single-event reference.

Response

A valid batch request returns HTTP 202 Accepted. The response includes totals and a result for every input row. index is zero-based and refers to the row in events.
For a rejected row, status is rejected and reason explains the failure (for example, session_id is required). Retry only rejected rows after addressing their reason. A temporary enqueue failure includes a Retry-After header; accepted rows should not be sent again.

Errors

  • More than 500 events returns HTTP 400 for the whole request.
  • Missing or invalid API key returns HTTP 401.
  • Invalid JSON or a request body that is too large is rejected before processing rows.
Batch ingestion confirms that events reached the ingestion endpoint. Captured events may appear in operational views, but ingestion does not by itself create a pack, approve an evaluator, or activate evaluator-pack scoring. See Evaluator packs for the review and validation workflow.