Skip to content

Errors

The API uses standard HTTP status codes. Error responses are returned as plain text with a short description.

Example error response:

Key Not Found

Error bodies are plain text, not JSON. Handle them as text unless an endpoint page documents a different response body.

Terminal window
curl -i 'https://api.echovalue.dev/kv/default/missing' \
-H 'x-token: mytoken'
HTTP/1.1 404 Not Found
x-cost: 1
x-balance: 97
Key Not Found
CodeNameWhen it occursWhat to check
400Bad RequestThe request is malformed, missing required parameters, or uses an invalid field combinationBody shape, content type, required fields, URL/query parameters
401UnauthorizedThe x-token header is missing, too short, or invalidSend the exact token in x-token; create a new token if needed
402Payment RequiredThe wallet has insufficient creditsCheck balance with GET /token or create a recharge link
404Not FoundThe key, webhook, or resource does not existConfirm the bucket/key, webhookId, and path
405Method Not AllowedThe HTTP method is not supported for this endpointCompare the method with the endpoint reference
409ConflictA resource already existsUse a different webhookId or update the existing webhook
CodeNameWhen it occursWhat to do
500Internal Server ErrorUnexpected server-side failureRetry later and check Logs
502Bad GatewayA utility request could not complete successfullyRetry later or reduce request complexity
503Service UnavailableThe requested service is temporarily unavailableRetry later
SituationStatus codeTypical body
Missing x-token header401Unauthorized
Token doesn’t exist401Unauthorized
No credits left402Insufficient credits
GET on a key that was never set404Key Not Found
Create a webhook with an existing webhookId409Short conflict message
GET webhook list when none is configured200JSON with an empty webhooks array
DELETE webhook with missing or unknown webhookId400 or 404Short validation or not-found message
Calling an endpoint with the wrong HTTP method405Short method error
  • Use Response Headers to read x-cost and x-balance when they are present.
  • Use Logs to inspect recent failed calls for the same token.
  • 429 Too Many Requests can occur when a caller exceeds protective rate limits.