HTTP status codes
Error response format
All error responses return a JSON body with amessage field:
Common errors
400 — Invalid address format
0x..., 40 hex characters). Use ethers.getAddress(address) to checksum an address.
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
HTTP error codes returned by the Autheo Chain REST API and how to handle them.
| Code | Meaning | Common cause |
|---|---|---|
200 OK | Success | Request completed successfully |
400 Bad Request | Invalid parameters | Malformed address, invalid block number, or missing required parameter |
404 Not Found | Resource not found | Address has no data, block doesn’t exist, or transaction hash not found |
422 Unprocessable Entity | Validation error | Parameter value is out of range or wrong type |
429 Too Many Requests | Rate limited | Too many requests in a short period |
500 Internal Server Error | Server error | Retry with backoff |
message field:
{
"message": "Not found"
}
{"message": "Invalid address hash"}
0x..., 40 hex characters). Use ethers.getAddress(address) to checksum an address.
{"message": "Not found"}
async function apiRequest(path) {
const response = await fetch(`https://evm-explorer.autheo.com/api/v2${path}`);
if (!response.ok) {
const error = await response.json().catch(() => ({ message: "Unknown error" }));
throw new Error(`API error ${response.status}: ${error.message}`);
}
return response.json();
}
try {
const data = await apiRequest("/addresses/0x<address>");
console.log(data);
} catch (err) {
console.error(err.message);
}