Record a usage event

Overview

Record a usage event

Idempotent usage ingest. Events are processed asynchronously and update meter balances when matched.

When to use this

Call from your app whenever billable usage occurs; use a stable transaction_id per logical event.

Good to know

Returns 202 Accepted. Confirm processing_status via webhooks or polling GET /usage-events/{id}.

See also

Usage billing guide · Create meter · Create usage subscription

Authentication

Merchant routes require an API key in the X-API-KEY header (see Integration overview). Use a test key against https://sandbox.api.lomi.africa and a live key against https://api.lomi.africa.

Endpoint

POST /usage-events

Base URLs:

• https://sandbox.api.lomi.africa
• https://api.lomi.africa

Request

Path parameters

No path parameters beyond the URL pattern.

Query parameters

No query parameters.

Request body

No application/json body for this operation.

Responses

Errors

Errors follow the standard JSON error format (status code and machine-readable message). Validate inputs before calling; 401 indicates a missing/invalid key, 404 a missing resource for this organization, 429 rate limiting. For safe retries on create-style calls, send an idempotency key when your flow supports it.

Example

curl -sS -X POST "https://sandbox.api.lomi.africa/usage-events" \
  -H "X-API-KEY: $LOMI_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

OpenAPI

• operationId: UsageEventsController_ingest
• Operation: POST /usage-events

Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.