Section
3 guides
Event Ingestion
Record usage events reliably at any volume.
Every charge in ABAXUS is driven by usage events. This section explains how to get those events into the system reliably — whether you’re ingesting them one at a time from a hot path, batching them for efficiency, or loading historical data to correct the record. All three modes share the same idempotency model, so every submission is safe to retry without risking double-counting.
In this section
1
Ingesting Events
Send usage events to ABAXUS using the single or batch ingestion endpoints.
2
Idempotency & Reliability
How idempotency keys protect against double-counting on retries and network failures.
3
Backfilling Historical Data
Load historical events and correct past usage data without corrupting current aggregates.