No account required

See the exact request before you sign up

UsageBox ingestion is one POST. Change the sample value, switch between the minimal and explicit forms, and copy the same request shape you would send in production. Nothing on this page is sent anywhere.

Your use case

Unit: requests
Only value is required. UsageBox can infer omitted resource keys when your account has one safe candidate for each.
Create a free key and send this for realSee event limits

Free tier: no credit card. Your article intent is carried into setup.

API Requests

One POST records the usage event. UsageBox handles duplicates, late events, raw history, and explainable monthly rollups.

sum · requests
curl -X POST 'https://api.usagebox.com/api/v1/usage' \
  -H 'x-api-key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '[{"value":1}]'
Why both forms? The minimal event is ideal for the first proof-of-life call. The explicit form is what you use once your integration has multiple meters or catalog objects and you want deterministic routing.

What happens after this POST?

  1. The event is authenticated and recorded with idempotency protection.
  2. Late events remain attributable to the period they actually belong to.
  3. Raw history stays available for reconciliation and disputes.
  4. UsageBox produces the meter rollup; pricing and invoicing can remain in whichever biller you use.
Read the full ingestion contract →