Look up API errors and usage limits
Use the response error code to find the right action, and check body size, timeout, and usage accounting rules.
On this page
Find the action for an error code
| Code | Meaning | Action |
|---|---|---|
| invalid_api_key | The key is invalid | Buyer checks X-Invokora-Key or rotates a lost key in the workspace |
| endpoint_not_allowed | The plan does not grant this endpoint | Check the purchased plan, HTTP method, and path |
| rate_limit_exceeded | The short-term request limit was reached | Wait for the reported reset and lower the request rate |
| object_quota_exceeded | A Hard object allowance is exhausted | Check remaining units; wait for reset or choose a suitable plan |
| bandwidth_payment_required | Free-plan bandwidth exceeded without a payment method | Buyer can enable paid excess bandwidth in the workspace |
| origin_unavailable | The origin could not complete the request | Merchant checks origin availability, routing, and connectivity |
Understand access and metering
active means the subscription is active; each call still needs valid permissions and available quotas and rate limits. paused means access is paused. canceled means new calls have stopped.
A complete original origin response below 500 confirms associated object usage, including origin 4xx responses. Origin 5xx, failures, timeouts, incomplete responses, and client interruptions do not confirm object usage. Forwarded requests still consume the rate-limit window, and actual transmitted bandwidth is metered separately.
Object headers x-ratelimit-{name}-limit, remaining, and reset report the allowance, remaining units, and seconds until reset. In-flight dynamic Hard calls may exceed the allowance. Subsequent calls are blocked, without Hard overage charges.
Request, bandwidth, and retention limits
| Item | Limit or rule |
|---|---|
| OpenAPI document | Up to 5 MiB; self-contained OpenAPI 3.0.x / 3.1.x |
| Request and response bodies | Up to 50 MB each; the merchant may set a lower limit |
| Origin timeout | 1–180 seconds |
| Bandwidth | 10 decimal GB of combined requests and responses per subscription cycle, then USD 1/GB |
| Request logs | Metadata retained for 30 days; no query, headers, or bodies |
| Service attachments | Up to 5 per upload, 25 MB each; retained up to 180 days after terminal order status |