HTTPS status codes

When an API request fails, Nexpay returns both an HTTP status code and a structured JSON error response that includes one or more internal error codes with human-readable messages. This combined approach helps you quickly identify what went wrong and take the appropriate action.

How errors are reported

HTTP status codes indicate the general class of error:

Error structure in JSON format

Data structure for errors object:

Examples

In addition to the HTTP status, the API returns a JSON body with one or more error objects:

{
  "errors": [
    {
      "code": -32600, 
      "message": "Invalid Request", 
      "data": "Unknown symbol BTCUSD"
    }
  ],
  "traceId": "b1d88d60011a9bda350b0eef7dc8dcbb"
}

{
  "errors": [
    {
      "code": 30240, 
      "message": "Invalid cryptocurrency address"
    }
  ],
  "traceId": "092b0d1cf5dfadac6f148039d40851ea"
}

Common error categories

Nexpay defines a set of internal error codes, each associated with a clear message describing the issue:

1. HTTP 403 - authentication & authorization errors

These codes indicate problems with authentication headers or API key state.

2. HTTP 400 - request validation errors

These errors point out malformed or logically incorrect payload data that needs to be fixed before retrying.

3. HTTP 500 - server errors

Returns when an unexpected server problem occurs during processing