Understand common API errors and how to resolve them efficiently
SingleView Open Banking APIs use standard HTTP response codes to indicate the outcome of an API request. Successful requests return a success response, while unsuccessful requests return an appropriate error code along with details describing the issue.
Use the information below to identify, troubleshoot, and resolve common integration issues.
When an error occurs, the API returns an error response containing information about the failure.
{ "success": false, "error": { "code": "INVALID_CONSENT", "message": "The specified consent could not be found." } }HTTP Status Code | Error | Description | Possible Cause | Resolution |
|---|---|---|---|---|
200 | OK | The request was processed successfully. | Request completed successfully. | No action required. |
400 | Bad Request | The request contains invalid or missing parameters. | Missing required fields, invalid values, malformed request. | Verify request parameters and payload structure. |
401 | Unauthorized | Authentication failed. | Missing, invalid, or expired access token. | Generate a new access token and retry. |
403 | Forbidden | Access to the requested resource is not permitted. | Insufficient scopes, permissions, or consent access. | Verify consent permissions and application scopes. |
404 | Not Found | The requested resource could not be located. | Invalid consent ID, account ID, or endpoint URL. | Verify resource identifiers and endpoint path. |
405 | Method Not Allowed | The HTTP method is not supported by the endpoint. | Incorrect use of GET, POST, PUT, or DELETE. | Use the supported HTTP method specified in the API documentation. |
408 | Request Timeout | The request exceeded the processing time limit. | Network latency or temporary service delays. | Retry the request. |
409 | Conflict | The request conflicts with the current resource state. | Duplicate resource creation or conflicting operation. | Review the resource status before retrying. |
422 | Unprocessable Entity | The request is valid but cannot be processed. | Business validation failure or unsupported operation. | Verify business rules and request data. |
429 | Too Many Requests | API rate limit has been exceeded. | Excessive request volume. | Reduce request frequency and retry later. |
500 | Internal Server Error | An unexpected server-side error occurred. | Temporary platform or processing issue. | Retry the request. Contact support if the issue persists. |
502 | Bad Gateway | Invalid response received from an upstream service. | Temporary bank or provider connectivity issue. | Retry the request after a short delay. |
503 | Service Unavailable | The service is temporarily unavailable. | Maintenance or temporary outage. | Retry the request later. |
504 | Gateway Timeout | Upstream service did not respond in time. | Bank API or network timeout. | Retry the request. |
Before contacting support, verify the following:
If an issue persists after troubleshooting: