Errors

​

HTTP Status Codes

​

Error Response Format

{
  "status": "error",
  "message": "Human-readable error description",
  "data": [
    {
      "field": "field_name",
      "message": "Specific validation error"
    }
  ]
}

​

Common Error Scenarios

​

400 Bad Request

• Invalid parameters: Missing required fields, invalid formats
• Unsupported combinations: Token/currency pairs not supported
• Amount validation: Amounts outside provider limits
• Provider issues: Provider not found or misconfigured
• Provider queue: providerId and providerIds sent together, more than 3 entries, duplicates, or an entry that can’t serve the corridor — see Pin a provider queue

​

503 Service Unavailable

• No provider available: When no providers can handle the specific request
• Service temporarily unavailable: During maintenance or high load
• Geographic restrictions: Service not available in your region

​

Handling Service Unavailability

1. Check request parameters: Verify token, amount, and currency combinations
2. Try different amounts: Some providers have minimum/maximum limits
3. Retry later: Provider availability may change over time
4. Contact support: If the issue persists, reach out to our team

​

Getting Help

1. Check the error response for specific details
2. Review our documentation for endpoint requirements
3. Join our developer community on Telegram
4. Contact support at [email protected]
5. Report issues on GitHub