Combined revenue metrics
Combined revenue metrics
Overview
Combined revenue metrics
Returns MRR, usage revenue, and one-time revenue for a date range.
When to use this
Use for finance reporting that combines subscription MRR with metered usage and one-off charges.
Good to know
Requires start_date and end_date query parameters.
See also
Organization metrics · Usage billing guide
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-billing/revenue
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 |
|---|---|---|---|---|
end_date | query | Yes | - | |
start_date | query | Yes | - |
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-billing/revenue?end_date=value&start_date=value" \
-H "X-API-KEY: $LOMI_SECRET_KEY"OpenAPI
- operationId:
UsageBillingController_getRevenue - Operation:
GET /usage-billing/revenue
Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.