List customer transactions
List customer transactions
Overview
List customer transactions
Returns transactions linked to a single customer ID for statements and dispute handling.
When to use this
Use on customer detail pages or when answering support questions tied to one buyer.
See also
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 /customers/{id}/transactions
Base URLs:
https://sandbox.api.lomi.africahttps://api.lomi.africa
Request
Path parameters
| Name | Required | Schema | Description |
|---|---|---|---|
id | Yes | - | UUID du client |
Query parameters
No query parameters.
Headers
| Name | In | Required | Schema | Description |
|---|---|---|---|---|
Lomi-Account | header | No | - | Optional lomi. Network account id (acct_...). When present, the API key acts as the Operator and the request targets the connected Member Account. |
Responses
| Status | Description |
|---|---|
200 | Success |
401 | Invalid or missing API key |
404 | Resource not found |
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/customers/value/transactions" \
-H "X-API-KEY: $LOMI_SECRET_KEY"OpenAPI
- operationId:
CustomersController_getTransactions - Operation:
GET /customers/{id}/transactions
Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.