Common Errors
Authentication Errors
- 401 Unauthorized: This typically means your authentication token is invalid or has expired.
- Solution: Request a new token using the login endpoint.
- "Invalid credentials": This means the email or password provided to the login endpoint is incorrect.
- Solution: Verify your credentials and try again.
Request Errors
- 400 Bad Request: This usually means there's an issue with your request parameters.
-Solution: Check the error message for details about which parameter is missing or invalid.
- 404 Not Found: This means the endpoint URL is incorrect.
- Solution: Verify the endpoint URL and ensure it matches the documentation.
- 429 Too Many Requests: This means you've exceeded the rate limit for API requests.
- Solution: Implement exponential backoff and retry logic in your code.
Response Parsing Errors
- JSON Decode Error: This occurs when trying to parse a non-JSON response.
- Solution: Check if the API returned an error message or if the endpoint doesn't return JSON.
Debugging Tips
1. Enable Verbose Logging: Set up detailed logging for API requests and responses to help identify issues.
2. Check Request Headers: Please make sure all required headers are included in your requests.
3. Validate Parameters: Verify that all required parameters are included and formatted correctly.
4. Test with cURL: Use cURL commands to test API endpoints directly before implementing in your code.
5. Check Token Expiration: Ensure your authentication token hasn't expired before making requests.
Support Resources
If you encounter persistent issues with the API, contact support through one of these channels:
- Email: [email protected]