# Error Codes

When an error occurs, the **HTTP status code** is returned both as a response header and in the response body.

The response body also includes a *Signable-specific* error code and a message explaining why the request failed.

#### Response body example


```json
{  
    "http": 400,  
    "code": 10555,  
    "message": "To be able to update branding options you must pass in at least one option"  
}
```

## General Error Codes

The following generic errors can be served from any endpoint.

| Code | Message |
|  --- | --- |
| 10001 | Invalid HTTP Method. Please use either GET, POST, PUT or DELETE |
| 10002 | Authentication failed. Please enter the correct API Key and password. |
| 10003 | The URL you are looking for does not exist. |
| 10004 | Authentication failed. Your API access has been suspended please contact [help@signable.co.uk](mailto:help@signable.co.uk) |
| 10005 | Authentication failed. This API key has been removed. If you feel this is in error, please contact [help@signable.co.uk](mailto:help@signable.co.uk) |
| 10006 | Authentication failed. This API key has been removed. If you feel this is in error, please contact [help@signable.co.uk](mailto:help@signable.co.uk) |
| 10007 | Invalid Content Type. You have sent a POST request however you haven't set the Content Type to `application/x-www-form-urlencoded` |
| 10008 | Forbidden. You need to have a partner enabled API key to access this |
| 10009 | Authentication failed. Your account needs to be on a plan that includes API access. |


> 💡 See **sub-pages** for errors from specific resources.