Getting Started
Error handling
When using the Geonode Proxy API, you may encounter various HTTP status codes. Understanding these codes helps you handle errors gracefully and implement robust error handling in your applications.
HTTP Status Codes
Status Code | Description | Solution |
---|---|---|
200 | OK – The request was successful | No action needed |
403 | Forbidden – Access denied | Check your access permissions and subscription level |
407 | Unauthorized – Incorrect or missing API key/token | Check your authentication credentials and ensure they’re properly formatted |
429 | Too Many Requests – Rate limit exceeded | Implement rate limiting in your code or reduce request frequency |
466 | Bandwidth Limit Reached | Recharge your bandwidth allocation or upgrade your plan |
5xx | Server Errors – Temporary issues on our side | Implement retry logic with exponential backoff |
Best Practices
-
Always Implement Error Handling
- Never assume requests will succeed
- Handle both expected and unexpected errors
-
Use Retry Logic
- Implement exponential backoff for 5xx errors
- Respect rate limits and Retry-After headers
-
Log Errors Appropriately
- Include relevant request details
- Don’t log sensitive information
-
User Feedback
- Provide clear error messages to end users
- Include actionable steps for resolution
Support
If you encounter persistent errors or need assistance, contact our support team at Support.