Error Handling

This explains how to handle common API errors.

General information

Each request returns a requestId field with a unique identifier for the request. You can use this requestId to track your requests and get technical support from Chargeflow, if needed.

Please include your requestId when you contact Chargeflow's support for better assistance.

400 Bad request

The 400 Bad Request error means that the server cannot process your request due to errors on your end.

Such errors are usually due to malformed syntax or incorrect parameters in the request. This error often occurs when submitting incomplete data. Make sure to check your formatting and data for errors if you encounter this error message.

401 Unauthorized

401 Unauthorized error suggests that your request requires authentication, but it couldn't be validated due to missing or invalid credentials or authentication tokens.

This error often occurs when you try to access restricted resources without proper authentication (API key and HMAC signature).

Please read Getting Started for more information on how to correctly authenticate requests to Chargeflow API.

403 Forbidden

The 403 Forbidden error means that the server understands your request but refuses to authorize it, typically because of insufficient permissions or access limitations.

If you see this error, you're trying to access resources that you don't have the necessary permissions for.

404 Page not found

The 404 Not Found error shows that the server couldn't find the resource that you requested. This could be due to a misspelled URL, deleted resource, or incorrect routing configuration.

In case of such an error, ensure that the URL you're trying to reach exists.

429 Too Many Requests

The 429 Too Many Requests error indicates that you've sent too many requests within a short period, exceeding the rate limits set by the Chargeflow API.

This error often happens when you make excessive requests rapidly. If you receive this error, consider reducing your request rate or implementing backoff strategies.

500 - Internal server error

This error appears when the server encounters unexpected issues that prevent it from fulfilling your request.

Such issues may include programming glitches, configuration difficulties, resource exhaustion, or problems with the database.

502 - Bad gateway

The 502 Bad Gateway error appears when a server, acting as a gateway or proxy, receives an invalid response from an upstream server. This error might occur when there are communication issues between servers, such as timeouts, network failures, or incorrect proxy settings.