An overview of all Greenspark API errors.
The Greenspark API uses standard HTTP status codes to represent the result of your requests.
|200||OK||The request succeeded.|
|201||Created||The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests.|
Client error responses
|400||Bad Request||The server cannot process the request due to something that is perceived to be a client error. For example: malformed request syntax, wrong parameter type.|
|401||Unauthorized||Indicates a problem with your provided Greenspark API key.|
|403||Forbidden||You don't have the right plan to use the Greenspark API.|
|404||Not Found||The server can not find the requested resource. This means that the endpoint is valid but the resource itself does not exist.|
Server error responses
|500||Internal Server Error||The server has encountered a situation it does not know how to handle.|