How to handle errors with our API endpoints
Finvera’s API provides clear and structured error responses to help developers diagnose and resolve issues efficiently. Below is a breakdown of common errors, their meanings, and best practices for handling them.
All error responses follow a standardized JSON format:
HTTP Status Code | Error Type | Description |
---|---|---|
400 Bad Request | Invalid Parameters | The request contains malformed or missing parameters. |
401 Unauthorized | Invalid API Key | Authentication is missing or incorrect. Ensure you include the Bearer token. |
403 Forbidden | Insufficient Permissions | The request is valid but the API key does not have access to the requested resource. |
404 Not Found | Resource Not Found | The requested endpoint or data does not exist. |
429 Too Many Requests | Rate Limit Exceeded | The request limit has been reached; slow down requests or upgrade your plan. |
500 Internal Server Error | Unexpected Error | A server-side issue occurred; retry later or contact support. |
429 Too Many Requests
or 500 Internal Server Error
.By following these guidelines, you can ensure smooth and resilient API integrations. For persistent issues, contact Finvera Support for assistance.