Skip to main content
POST
curl
See Batches in the event ingestion guide. The device lane has the same per-item outcomes for SDK flushes: see SDK event submission.

Authorizations

x-api-key
string
header
required

Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is missing, wrong, revoked or expired; 403 means the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.

Body

application/json
events
object[]
required

1 to 500 events. Each item follows MonitoringEventCreateRequest, including the 7-day past and 5-minute future window on occurred_at.

Required array length: 1 - 500 elements

Response

No item was rejected: every item is accepted or replayed.

accepted_count
integer
required

Items stored and evaluated.

Required range: x >= 0
replayed_count
integer
required

Items already stored with the same content.

Required range: x >= 0
rejected_count
integer
required

Items not stored.

Required range: x >= 0
results
object[]
required

One entry per item, in request order.