List usage events
List usage events
Overview
List usage events
Lists ingested usage events with pagination and optional filters for customer, code, and processing status.
When to use this
Use for support, reconciliation, or debugging failed usage ingest.
See also
Record usage event · Get usage event
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
GET /usage-events
Base URLs:
https://sandbox.api.lomi.africahttps://api.lomi.africa
Request
Path parameters
No path parameters beyond the URL pattern.
Query parameters
| Name | In | Required | Schema | Description |
|---|---|---|---|---|
status | query | No | - | |
code | query | No | - | |
customer_id | query | No | - | |
page_size | query | No | - | |
page | query | No | - |
Responses
| Status | Description |
|---|---|
200 | Success |
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 GET "https://sandbox.api.lomi.africa/usage-events?status=pending&code=value" \
-H "X-API-KEY: $LOMI_SECRET_KEY"OpenAPI
- operationId:
UsageEventsController_findAll - Operation:
GET /usage-events
Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.