Skip to main content
Effective error handling is essential for ensuring a smooth developer experience and building robust applications. This guide provides an overview of the errors you may encounter when interacting with the IXO Spatial Web API.
Errors that occur due to client-side issues.

Common Errors

  • 400 Bad Request: Malformed request or invalid parameters
  • 401 Unauthorized: Authentication required or failed
  • 403 Forbidden: Insufficient permissions
  • 404 Not Found: Resource not found
  • 429 Too Many Requests: Rate limit exceeded
Errors that occur due to server-side issues.

Common Errors

  • 500 Internal Server Error: Unexpected server condition
  • 502 Bad Gateway: Invalid response from upstream
  • 503 Service Unavailable: Server temporarily unable to handle request

​
Error Response Structure

The IXO Spatial Web API provides informative error responses in JSON format: 
{
  "error": {
    "code": 400,
    "message": "Invalid request parameters",
    "details": [
      {
        "field": "entityId",
        "error": "Missing required parameter"
      }
    ]
  }
}

​
Response Fields

  • code: HTTP status code
  • message: Human-readable error description
  • details: Additional error information

​
Best Practices

Rely on HTTP status codes to understand error types and handle them appropriately.
For 5xx errors, implement retry logic with exponential backoff.
Validate all input parameters before sending requests to minimize 400 errors.
Monitor and respect rate limits to avoid 429 errors.

​
Common Error Solutions

400 Bad Request

Solution: Double-check request syntax and parameters

401 Unauthorized

Solution: Verify access token and re-authenticate if needed

403 Forbidden

Solution: Verify user permissions and roles

500 Internal Server Error

Solution: Retry after delay or contact support
Always log and monitor errors to identify patterns and improve error handling in your applications.