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

CodeStatusDescription
200OKRequest succeeded
400Bad RequestInvalid parameters or request format
401UnauthorizedInvalid or missing API key
403ForbiddenInsufficient permissions
404Not FoundResource doesn’t exist
409ConflictResource conflict (e.g., duplicate)
429Too Many RequestsRate limit exceeded
500Internal Server ErrorCharge server error

​
Error Response Structure

All errors return a standardized JSON object: 
{
  "object": "error",
  "message": "The fleet ID provided does not exist.",
  "code": "fleet_not_found",
  "param": "fleet",
  "request": "req_123abc456def",
  "doc_url": "https://docs.chargeapi.co/errors#fleet_not_found"
}

​
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