API Documentation
Errors
Blockradar’s API is RESTful and as such, uses conventional HTTP response codes to indicate the success or failure of requests.
HTTP Codes
| Code | Description |
|---|---|
| 200 | Request was successful and intended action was carried out. |
| 201 | A resource has successfully been created. |
| 400 | A validation or client side error occurred and the request was not fulfilled. |
| 401 | The request was not authorized. This can be triggered by passing an invalid api key in the x-api-key header or the lack of one. |
| 404 | Request could not be fulfilled as the requested resource does not exist. |
| 5xx | Request could not be fulfilled due to an error on Blockradar’s end. This shouldn’t happen so please report as soon as you encounter any instance of this. |
Not sure where to look? Try search
Type the error or keywords into the search bar above. If you don’t find what you’re looking for, contact us, we’re happy to help.
Type the error or keywords into the search bar above. If you don’t find what you’re looking for, contact us, we’re happy to help.