HTTP Error Responses

When using our unified API, you might encounter various HTTP error responses. The examples below illustrate some scenarios that could occur during your interactions. Please note that these examples do not cover every possible error; individual services (such as RPC or Blockbook endpoints) may return additional or more specific error messages.

401 Unauthorized

This status indicates that authentication has failed. This may occur because:

Missing API Key: No API key was provided either in the URL (for RPC endpoints) or via the HTTP header.
Invalid API Key: The API key provided is either incorrectly formatted, incomplete, or does not match a valid key.

401

{
  "message": "Missing API Key"
}

404 Not Found

This error indicates that the endpoint you attempted to access does not exist. It may be caused by a typo or an incorrect value in the URL path. For example, if the there is an incorrect product or network identifier in the URL, the API will not recognize the route.

Troubleshooting Tips:

Verify the URL: Double-check the path in your request URL to ensure that the network identifier and other path parameters are correctly spelled.
Consult the Documentation: Refer to the API documentation to confirm the correct endpoint structure for your request.
Contact Support: If you continue to receive this error despite verifying your request, please contact our support team for assistance at suuport@jetnodes.com.

404

{
  "message": "Route POST:/rpc/btcr/28xoqRS5IcBcYY4urRPbHNnTXy5aoaxC6f1-PX1v38Wfnlxa7oaVjgHE not found",
  "error": "Not Found",
  "statusCode": 404
}

429 Too Many Requests

This status indicates that your request has been blocked because you have exceeded your allowed API credits. This can happen if either your monthly API credits or your API credits per second have been surpassed. Please review your usage on the Pricing and Rate Limit page and consider adjusting your subscription plan if necessary.

429

{
  "message": "Rate limit exceeded"
}

502 Bad Gateway

This status means that the unified API was unable to receive a valid response from an underlying service. It typically points to a communication issue between the API and the service you are trying to access.

502

{
  "message": "Bad Gateway"
}