GET /lookups/*
The /lookups namespace exposes a set of read-only enumerations the API uses internally. These are useful when you need to render a dropdown, validate input, or interpret a status code without hard-coding values in your client.
All lookup endpoints are GET requests, require a Bearer token, and return JSON arrays.
Available Endpoints
| Endpoint | Returns |
|---|---|
GET /lookups/brands | All brands. See Get Brands for the full schema. |
GET /lookups/providers | All product providers (e.g. MTN, Vodacom, Eskom). |
GET /lookups/transaction-status | All transaction statuses. See Transaction Status. |
GET /lookups/transaction-item-status | Per-item statuses inside a transaction. |
GET /lookups/channel-types | Channel types (USSD, MOBILE, POS, etc.). |
GET /lookups/partner-types | Partner type classifications. |
GET /lookups/funding-methods | Supported funding methods. |
GET /lookups/funding-request-status | Funding request statuses. |
GET /lookups/integrations | Available integration types. |
GET /lookups/environments | Environment identifiers (sandbox, production). |
GET /lookups/authentication-types | Authentication types supported by the platform. |
GET /lookups/simple-entity-types | The set of entity types supported by the lookup service itself. |
Request
GET /api/v1/lookups/transaction-status
Authorization: Bearer <ACCESS_TOKEN>
Response
Each endpoint returns either an array of strings (for enum-only responses) or an array of objects with at least id, code, and description. Always treat unknown values gracefully — new entries may be added without a major version bump.
[
"PENDING",
"PROCESSING",
"COMPLETED",
"FAILED"
]
Last updated: April 2026