Send a batch of activities directly
POST/v1/activities
For senders that speak in catalogue activities, with any write key: the catalogue says which activities each key class may send. A browser key may be sent in the body as writeKey, since a beacon cannot set headers. The batch is accepted or refused as a whole. Refusals (4xx) concern the key, the owner or the limits and store nothing. Events that are well-formed enough to attribute but fail validation are acknowledged and quarantined, so a sender never retries something that fails every time.
Request
Responses
- 202
- 400
- 401
- 403
- 413
- 429
- 503
Every event is durably stored.
Response Headers
Malformed request, or an event the key may not send or that names no valid owner. Nothing was stored.
Missing, unknown or revoked write key.
A browser key, which sends tracking calls instead.
Request body over 500 KB.
Rate limit of the key exceeded. Retry after the number of seconds in Retry-After.
Response Headers
The log could not take the batch. Nothing was stored; retry.