YesGraph uses conventional HTTP response codes to indicate success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that resulted from the provided information (e.g. a required parameter was missing, a query failed, etc.), and codes in the 5xx range indicate an error with YesGraph’s servers.

Status Code Interpretation What To Do
200 OK Everything worked as expected. High five!
201 Created The item was created as requested.  
202 Accepted We’ve accepted your request successfully and will process it in the background.  
400 Bad Request We did not understand your request syntactically. Issue a well-formed request. Curly brace for impact.
401 Unauthorized No valid API key was provided. Send a valid API key via the HTTP header. See Authentication.
403 Forbidden You were authenticated successfully but do not have permissions to request/change the resource. If you don’t have access, nothing will help. Check that you’re using the correct keys.
404 Not Found The requested item could not be found. Double-check your request.
405 Method Not Allowed This endpoint does not support the HTTP method you used (GET, POST, etc.) Try using a different HTTP method. Check the documentation for the endpoint in question.
422 Unprocessable Entity The request was well-formed, but something else was wrong with it. Often this means params are missing. The error details in the API response should describe the problem.
500 Internal Error Something went wrong on our end. You can assume we were informed and already fixing it. If the problem persists, email