Status and Error Codes

When working with the Chargetrip API, your keys can be visible to anyone who makes an effort to look for it. That is why we recommend adding a layer of restrictions to build secure applications and prevent unauthorized use.

API Response Codes

Our API uses the following response status codes, as defined in the RFC 2616 and RFC 6568.


200	The request succeeded. The client can read the body.
201	The request is created. A new resource will be created.
202	The request is accepted. The client has to wait until it’s done processing.
204	The request has succeeded but returns no message body.
304	Not modified.
400	The request could not be understood by the server due to malformed syntax.
401	The request requires authentication.
403	The server understood the request, but is refusing to fulfill it.
404	The requested resource could not be found.

API Error Objects

When an error occurs, our API returns a generic GraphQL error with an extension. Inside the extension object you can find an error description.

Authorization / Headers

          { "errors": [  {   "message": "The vehicle was not found in the database",   "locations": [   {   "line": 2,   "column": 3   }   ],   "path": [   "addReview"   ],   "extensions": {   "exception": {   "response": "VEHICLE_NOT_FOUND",   "status": 500,   "message": "No vehicle was found with the provided ID",   "code": "VEHICLE_NOT_FOUND"   }   }  } ], "data": null}