If you are unfamiliar with HTTP requests, please read more here.
Overview
Errors
Troubleshoot problems with API calls.
The ZBD API follows standard HTTP response codes for handling success and error requests.
Was this page helpful?
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Troubleshoot problems with API calls.
| HTTP Response Group | Status Code Range |
|---|---|
| Informational Responses | 100-199 |
| Successful Responses | 200-299 |
| Redirects | 300-399 |
| Client Errors | 400-499 |
| Server Errors | 500-599 |
| Status Code | Details | Response Description |
|---|---|---|
200 | Success | Request was successful. |
400 | Bad Request | Either incorrect or missing parameters provided for the Request. |
401 | Unauthorized | Request is not authorized. Make sure correct API Key is provided. |
403 | Forbidden | Request is forbidden. Make sure your IP is located in a region/country that ZBD services are available in. |
404 | Not Found | The requested endpoint/resource was not found. |
422 | Missing Parameter | The requested endpoint expected a specific parameter to be provided. |
429 | Rate Limited | Too many requests in short time-frame. |
500 | Server Error | Something went wrong in the ZBD API servers. |
{
"success": false,
"message": "Error creating Withdrawal Request: The \"amount\" property (in millisatoshis) is required.",
}
Was this page helpful?