GrapheneDB uses conventional HTTP response codes to indicate the success or failure of an API request, always following the guidelines of RFC 2616. The codes listed below have additional meaning for our API:
Immediate, synchronous responses from GET, PUT.
New entities created via POST.
Costly operations from PUT, POST are asynchronous.
Empty content from PUT, DELETE.
The client provided a bad request payload (eg. format or schema issues) to a POST, PUT operation.
The client is unauthorized.
The resource path does not exist in the API.
The client used an undefined HTTP method on a resource.
There’s another operation in progress on the same resource.
There was an error on our side.
The operation hasn’t been implemented yet.
The public API received an unexpected response from our internal infrastructure.
The public API didn’t receive a response from the internal infrastructure.