Error Response Format
All errors return a JSON response with an error type and message:HTTP Status Codes
| Code | Name | Description |
|---|---|---|
| 200 | OK | Request successful |
| 400 | Bad Request | Invalid parameters or malformed request |
| 401 | Unauthorized | Missing or invalid API key |
| 404 | Not Found | Vessel or resource not found |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Internal Server Error | Server-side error |
Common Errors
400 Bad Request
Invalid parameters in your request:- Verify IMO numbers are 7 digits
- Verify MMSI numbers are 9 digits
- Check date formats match ISO 8601
- Ensure required parameters are provided
401 Unauthorized
Authentication failed:- Include the
x-api-keyheader - Verify your API key is correct
- Check if your key has been revoked
404 Not Found
Vessel or resource doesn’t exist:- Verify the IMO/MMSI number is correct
- Check if the vessel is still active
- Try searching by name first
429 Rate Limited
Too many requests:- Implement exponential backoff
- Cache responses when possible
- Use bulk endpoints
Error Handling Example
Debugging Tips
- Check the response body - Error messages provide specific details
- Verify parameters - Use the API playground to test requests
- Check your credits - Some errors may be due to insufficient credits
- Review rate limits - Check
X-RateLimit-Remainingheader