Error Codes
The Fyndera API uses standard HTTP status codes and returns detailed error information in JSON format to help you understand and resolve issues.Error Response Format
All error responses follow this consistent format:HTTP Status Codes
2xx Success
- 200 OK - Request successful
- 201 Created - Resource created successfully
- 204 No Content - Request successful, no content returned
4xx Client Errors
- 400 Bad Request - Invalid request parameters or malformed request
- 401 Unauthorized - Authentication required or invalid API key
- 403 Forbidden - Valid authentication but insufficient permissions
- 404 Not Found - Requested resource not found
- 422 Unprocessable Entity - Valid request format but semantic errors
- 429 Too Many Requests - Rate limit exceeded
5xx Server Errors
- 500 Internal Server Error - Unexpected server error
- 502 Bad Gateway - Server acting as gateway received invalid response
- 503 Service Unavailable - Server temporarily unavailable
- 504 Gateway Timeout - Server acting as gateway timed out
Common Error Codes
Authentication Errors
object
Validation Errors
object
Rate Limiting Errors
object
Server Errors
object
Error Handling Best Practices
1. Always Check Status Codes
2. Handle Rate Limiting
3. Implement Retry Logic
4. Log Request IDs
Always include therequestId from error responses when contacting support:
Troubleshooting Common Issues
Invalid API Key
- Verify the API key is correct and active
- Check that youβre using the
Bearerprefix - Ensure there are no extra spaces or characters
Invalid Parameters
- Check parameter names are spelled correctly
- Verify enum values match the allowed options
- Ensure date formats are
YYYY-MM-DD
Rate Limiting
- By default, we process a maximum of 1.000 requests per hour
- If you need different limits, contact api-support@fyndera.be
- Implement exponential backoff for retries
Network Issues
- Check your internet connection
- Verify the API endpoint URL is correct
- Try the request again after a short delay
Getting Help
If you encounter errors not covered in this documentation:- Contact support: api-support@fyndera.be
- Include request details: Always provide the
requestIdfrom error responses