Skip to main content
Fetch Hive returns JSON errors for invalid or failed public API requests. Runtime public API errors include a human-readable message, a stable code, and error as a compatibility alias.

Error response format

Some plan and rate-limit responses also include code for compatibility with existing clients. New clients should read error_code. See Error Codes for the complete code list, catalog endpoint, and client handling guidance.

Common status codes

401 Unauthorized

Fetch Hive returns 401 when the Authorization header is missing, invalid, or uses a revoked API key. Example:

404 Not Found

Fetch Hive returns 404 when the resource does not exist for your account. Example workflow run response:
Example request lookup response:

422 Unprocessable Entity

Fetch Hive returns 422 when the request is authenticated but invalid for that endpoint. Examples:

502 Bad Gateway

Fetch Hive returns 502 when a provider fails while processing a prompt or agent request. Example:

Rate limits and concurrency

Fetch Hive tracks two independent daily meters (UTC midnight reset):
  1. Public API — counts requests authenticated with an API key through public/stream endpoints. Cap comes from plan.rate_limit_per_day.
  2. Provider tools — counts costly third-party workflow tool runs (Google/Bing/Exa search, website scrape, etc.) from the dashboard, schedules, and public workflow API. Cap comes from plan.provider_tool_calls_per_day. Growth, Pro, and Enterprise have no provider-tool cap (nil).
Workflow failures from provider-tool caps return a plain error string in the run payload (same style as credit-cap errors). The structured code provider_tool_rate_limit_exceeded is returned by the internal agent pre-flight endpoint.

Public API daily cap

Public API requests count against your plan daily API call cap. If you exceed that cap, Fetch Hive returns 429 Too Many Requests before running the request. Example daily API cap response:

Provider tool daily cap

Example workflow failure message:

Workflow concurrency

Workflow concurrency depends on your plan. If you exceed your concurrency cap, Fetch Hive returns 429 Too Many Requests. Example:
If you see this response on a workflow request, retry later or switch to callback delivery so Fetch Hive can queue the run.