200 | OK | The request succeeded and the response contains the expected payload. |
201 | Created | OneKhusa created the requested resource, such as a transaction or payout. |
202 | Accepted | OneKhusa accepted the request and queued it for further processing. Notification will be sent through email and/or webhook when process is complete. |
204 | No Content | The request succeeded and no response body is returned (for example, querying/retrieving a transaction which does not exist) |
400 | Bad Request | The request payload malformed due to business validation rules implemented in OneKhusa. |
401 | Unauthorized | The supplied OneKhusa credentials were missing, expired, or invalid. |
402 | Request Failed | The request was well-formed but OneKhusa could not complete it due to business rule validation. |
403 | Forbidden | The authenticated principal lacks permission to call this OneKhusa endpoint. |
404 | Not Found | The referenced OneKhusa resource could not be located. |
409 | Conflict | The request conflicts with the current state of the resource (for example, duplicate idempotency key). |
424 | External Dependency Failed | OneKhusa could not complete the request because a downstream provider returned an error. |
429 | Too Many Requests | The rate limit for this API key or tenant was exceeded; retry with exponential backoff. |
500, 502, 503, 504 | Server Errors | OneKhusa encountered an unexpected error; retries usually succeed once the service stabilizes. |