Kashimi’s API Error Handling
Kashimi’s API uses standard HTTP response codes to indicate the success or failure of API requests.2xx Range (Success) Codes in this range indicate a successful API request. The requested operation was completed as expected.
4xx Range (Client Errors) Codes in this range indicate an error related to the client’s request. These errors may occur due to missing required parameters, payment failures, or other client-specific issues.
5xx Range (Server Errors) Codes in this range indicate an issue with Kashimi’s servers. When you encounter a code in this range, it means the problem is on our side, not the client’s request.
Understanding these response codes will help you handle different scenarios appropriately and ensure smooth integration with Kashimi’s API.
HTTP Status Code Summary
Status Code | Title | Description |
|---|---|---|
| 400 | Bad Request | The request is malformed or missing the required fields. |
| 400 | Bad Request | One or more fields in the request failed validation. |
| 401 | Unauthorized | Invalid credentials. |
| 403 | Forbidden | Your credentials do not have permission to perform this action. |
| 404 | Not Found | The requested resource does not exist. |
| 409 | Conflict | Payment with this end-to-end ID already exists. |
| 422 | Unprocessable Entity | Payment object is invalid for the selected provider. |
| 429 | Too Many Requests | Too many requests have been sent in a short period of time. |
| 500 | Internal Server Error | An unexpected error occurred. |
| 503 | Service Unavailable | The service is temporarily unavailable, usually due to maintenance or overload. |
Error Fields
Field | Type | Required | Description |
|---|---|---|---|
title | string | ✅ | Short label describing the error |
httpStatusCode | integer | ✅ | HTTP status code (e.g., 400 = Bad Request) |
message | string | ✅ | Human-readable explanation of the error |