Standard response format
Every API response is wrapped in the following structure:| Field | Type | Description |
|---|---|---|
status | boolean | true if the request was successful, false otherwise |
message | string | A human-readable description of the result |
code | string | The response code (e.g., "200", "400", "403") |
version | string | The API version |
reference | string | A unique reference for the request, useful for support queries |
data | object | The response payload — varies per endpoint |
error | object | null | Error details when status is false |
Error response format
When a request fails,status is false and the error object contains details:
Common error codes
| Code | Meaning | Description |
|---|---|---|
200 | Success | Request completed successfully |
400 | Bad Request | The request was invalid — check the error.message for details |
403 | Forbidden | Authentication failed, insufficient permissions, or IP not whitelisted |
500 | Server Error | Something went wrong on our end — contact support if the issue persists |
Handling errors
- Always check the
statusfield to determine if the request was successful - Use the
error.messagefield for user-facing error messages or debugging - Include the
referencevalue when contacting support — it helps us trace the request - All endpoints return HTTP 200 at the transport level; the business-level status is indicated by the
statusandcodefields in the response body
Pagination
Endpoints that return lists support pagination via query parameters:| Parameter | Type | Default | Description |
|---|---|---|---|
pageNumber | integer | 1 | The page to retrieve |
pageSize | integer | 50 | Number of records per page |