List disputes
List disputes
Overview
List disputes
Returns card payment disputes for your organization with optional status and date filters.
When to use this
Use for support queues, reconciliation, and automation on DISPUTE_* webhooks.
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 /disputes
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 |
|---|---|---|---|---|
pageSize | query | No | - | |
page | query | No | - | |
endDate | query | No | - | |
startDate | query | No | - | |
status | query | No | - |
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 |
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/disputes?pageSize=1&page=1" \
-H "X-API-KEY: $LOMI_SECRET_KEY"OpenAPI
- operationId:
DisputesController_findAll - Operation:
GET /disputes
Full schemas and Try it: API reference. Machine-readable contract: repo apps/docs/openapi.json.