About Us
Error Handling
Charge API uses standard HTTP response codes and returns structured JSON error objects for consistent error handling across all endpoints.
Robust error handling is essential for EV charging applications where reliability directly impacts driver experience and fleet operations.
HTTP Status Codes
Code | Status | Description |
---|---|---|
200 | OK | Request succeeded |
400 | Bad Request | Invalid parameters or request format |
401 | Unauthorized | Invalid or missing API key |
403 | Forbidden | Insufficient permissions |
404 | Not Found | Resource doesn’t exist |
409 | Conflict | Resource conflict (e.g., duplicate) |
429 | Too Many Requests | Rate limit exceeded |
500 | Internal Server Error | Charge server error |
Error Response Structure
All errors return a standardized JSON object:
Getting Help
Include the request
ID when contacting support:
- Request ID:
req_123abc456def
(from error response) - Error Code:
fleet_not_found
(for specific issues) - Documentation: Check
doc_url
for detailed guidance