Skip to main content
The Paycrest API uses standard HTTP status codes and provides detailed error information to help you troubleshoot issues quickly.

​
HTTP Status Codes

CodeStatusDescription
200OKRequest successful
201CreatedResource created successfully
400Bad RequestInvalid parameters or request format
401UnauthorizedInvalid or missing API key
403ForbiddenInsufficient permissions for this action
404Not FoundResource not found
409ConflictResource conflict (e.g., duplicate order)
422Unprocessable EntityValidation failed
429Too Many RequestsRate limit exceeded
500Internal Server ErrorServer error
503Service UnavailableNo providers available to handle the request

​
Error Response Format

All error responses follow a consistent 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

​
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

When you receive a 503 error:
  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

If you’re experiencing persistent errors:
  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
When reporting errors, please include the complete error response, request details, and your API key (with sensitive parts redacted).
⌘I