Format
Common API Errors
Include the
request_id (if present), timestamp (UTC), and a minimal cURL reproduction when contacting support.Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
📊 New: Free research datasets — 10+ years of Ethereum token transfers, open to everyone. Explore the free datasets →
HTTP statuses and error bodies returned by BlockDB REST endpoints.
{
"error": {
"code": "INVALID_ARGUMENT",
"message": "from_block must be <= to_block",
"details": { "field": "from_block" },
"request_id": "req_01HXYZ..."
}
}
| HTTP | Code | Meaning | Action |
|---|---|---|---|
| 400 | INVALID_ARGUMENT | Body failed validation | Fix the field noted in details |
| 401 | UNAUTHENTICATED | Missing/invalid token | Send Authorization: Bearer token |
| 403 | PERMISSION_DENIED | Not allowed for plan/scope | Request access or adjust scope |
| 404 | NOT_FOUND | Resource not found | Verify endpoint or identifiers |
| 409 | CONFLICT | Mutually exclusive filters | Choose one filter set |
| 429 | RATE_LIMITED | Too many requests | Backoff and retry; request higher limits |
| 500 | INTERNAL | Unexpected error | Retry with jitter; include request_id |
| 503 | UNAVAILABLE | Temporary outage | Retry after a short delay |
request_id (if present), timestamp (UTC), and a minimal cURL reproduction when contacting support.Was this page helpful?