Ingest Billable Events
The event ingestion endpoint accepts a list of up to 100 events per request. Each event is passed
with a client-defined uniqueId which acts as an idempotency key, allowing you to send the same events
multiple times without worrying about duplicate data.
Event Format
Uniquely identifies the billable event, with a maximum length of 255 characters. It is recommended to use an ID format that is collision resistant, such as a UUID.
Associates the billable event with a customer account. This can either be the Alguna account ID, or an alias that you have defined for the account.
The name of the event, used to logically group when creating a metric.
An optional map of keys and values that further describe the event. These can either be used to segment the event when creating a metric through filtering, or describe attributes on which the metric is calculated. The properties object can contain up to 50 key-value pairs, all keys must be strings and values must be strings, integers or floats. Is is not possible to nest properties.
The time at which the event occured, in RFC3339 format. If not provided, the current time will be used.
Response
The list of uniqueId values that were successfully ingested.
The list of uniqueId values that were not ingested, if any.