When interacting with OrbitFlare RPC endpoints, you may encounter the following standard HTTP error codes. This guide helps you understand what these errors mean and how to resolve them.

​
HTTP Status Codes

Error CodeError MessageDescriptionSolution
401UnauthorizedInvalid API key or authentication token.- Verify your API key is correct
- Check if your API key has the required permissions
- Ensure your API key is properly set in the request headers
403ForbiddenAccess denied due to insufficient permissions or IP restrictions.- Verify your IP is whitelisted if IP restrictions are enabled
- Check if your subscription plan allows the requested operation
429Too Many RequestsYou’ve exceeded the rate limits for your subscription tier.- Implement request rate limiting in your application
- Consider upgrading to a higher tier with increased limits
- Check your current usage in the dashboard
500Internal Server ErrorAn unexpected error occurred on our servers.- Retry the request after a short delay
- If the issue persists, contact our support team
502Bad GatewayTemporary issue with our upstream services.- Retry the request after a few moments
- If persistent, check our status page for any ongoing incidents
503Service UnavailableService is temporarily unavailable or under maintenance.- Retry with exponential backoff
- Check our status page for maintenance announcements
504Gateway TimeoutRequest timed out while waiting for a response.- Check your network connection
- Consider reducing the complexity of your request
- Try breaking large requests into smaller chunks

​
JSON-RPC Errors

Error CodeMessageDescriptionSolution
-32700Parse errorInvalid JSON receivedCheck your request format and ensure it’s valid JSON
-32600Invalid requestJSON is valid but request format is wrongVerify your request matches the RPC method specification
-32601Method not foundThe requested method doesn’t existCheck the method name and our API documentation
-32602Invalid paramsMethod parameters are invalidReview the parameters required for the method
-32603Internal errorInternal JSON-RPC errorRetry the request; if persistent, contact support
-32000Server errorGeneric server-side errorRetry with exponential backoff
-32001Transaction simulation failedTransaction failed during simulationCheck transaction parameters and account states
-32002Account not foundRequested account doesn’t existVerify the account address is correct
-32003Block not foundRequested block not availableCheck if the block is within available history
-32004Node unhealthyRPC node is not in a healthy stateTry a different RPC endpoint

​
Best Practices

  1. Implement Retry Logic
    • Use exponential backoff for retries
    • Set appropriate timeout values
    • Handle rate limits gracefully
  2. Error Handling
    • Always check error responses
    • Log error details for debugging
    • Implement proper fallback mechanisms
  3. Monitoring
    • Monitor error rates in your application
    • Set up alerts for unusual error patterns
    • Track API usage and rate limit consumption

​
Support

If you encounter persistent issues or need help understanding specific errors, please:
  1. Check our status page for system status
  2. Join our Discord community for quick help
  3. Contact our support team for detailed assistance
For real-time updates on system status and maintenance, follow us on Twitter.