Events

Ingest events

Changed on

Ingest usage events for metering and billing purposes.

Events are deduplicated by (event_id, customer_id) — re-sending the same pair will not be double-counted. If timestamps differ across duplicates, the event with the latest timestamp is used.

By default, any invalid event rejects the entire batch. Set allow_partial_failures to true to ingest valid events and receive per-event failure details in the response body.

post/api/v1/events/ingest

Request

  • The document declares no server URL.
  • Auth
    HTTP bearer

Request body

allow_backfillingboolean nullable

Allow events with timestamps more than 1 day in the past. Defaults to false.

allow_partial_failuresboolean nullable

Accept the batch even if some events fail validation. Defaults to false. When true, valid events are ingested and failures are reported in the response body. When false (default), any invalid event rejects the entire batch.

Example request

{
  "events": [
    {
      "properties": {
        "region": "us-east-1",
        "tier": "pro",
        "bytes": "1048576"
      },
      "timestamp": "2026-01-15T10:30:00Z"
    }
  ]
}

Response

Events ingested successfully

Changes

  • v156373a72fa12Revision changes
    • info

      added the new optional request property

  • v1de35c02bb0d2Revision changes
    • warning

      added the new TOO_MANY_REQUESTS enum value to the response property for the response status

    • warning

      added the new TOO_MANY_REQUESTS enum value to the response property for the response status

    • info

      added the non-success response with the status