Skip to main content
The Poelis Public API uses standard HTTP status codes and returns structured error responses to help you handle errors gracefully.

Error Response Format

All error responses follow this structure:

Common Error Codes

400 Bad Request

Invalid request parameters or malformed request body.

401 Unauthorized

Missing or invalid REST API key.

403 Forbidden

Valid REST API key but insufficient permissions to access the resource.

404 Not Found

Resource not found or not accessible.

405 Method Not Allowed

HTTP method not allowed for this endpoint.

422 Unprocessable Entity

Validation error (e.g., invalid data format).

429 Too Many Requests

Rate limit exceeded. See Rate Limiting. Response includes Retry-After and X-RateLimit-* headers.

500 Internal Server Error

Server-side error. If this persists, contact support.

Request ID

All responses include an X-Request-ID header for tracking and debugging:
Include this ID when contacting support about errors.

Error Handling Best Practices

Check Status Codes

Always check HTTP status codes before processing responses

Log Request IDs

Log X-Request-ID for debugging and support requests

Getting Help

If you encounter persistent errors:
  1. Check the X-Request-ID header in the error response
  2. Review the error message and details
  3. Contact support@poelis.com ↗︎ with:
    • The X-Request-ID
    • The error code and message
    • Steps to reproduce