egdata API

v1 Problem Details

Error fields, stable codes, and client recovery steps.

v1 errors use application/problem+json (RFC 9457). Use the stable code for handling and the requestId for support. type identifies the problem category; it is an identifier, not a deployment signal. title, status, and detail describe the failure. Optional instance and errors add request and field-level context. Field issues can include pointer, parameter, code, and message.

{
  "type": "https://api.egdata.app/problems/invalid-query",
  "title": "Bad Request",
  "status": 400,
  "detail": "The query parameters are invalid.",
  "code": "INVALID_QUERY",
  "requestId": "req_example",
  "errors": [{ "parameter": "limit", "code": "INVALID", "message": "Expected an integer." }]
}
CategoryExamplesClient action
Invalid requestINVALID_PATH, INVALID_QUERY, INVALID_BODY, MALFORMED_JSONCorrect the indicated path, parameter, or JSON body.
CursorINVALID_CURSORRestart pagination with the same filters and a fresh cursor; do not edit opaque cursors.
Missing/invalid credentialsMISSING_API_KEY, INVALID_API_KEY, INVALID_AUTHORIZATION, CONFLICTING_CREDENTIALSSupply one valid key in X-API-Key or Authorization: Bearer; remove conflicting credentials.
Permission or entitlement deniedSCOPE_DENIED, PLAN_ENTITLEMENT_REQUIRED, or IP/origin/method/path/revocation codesCheck key permissions and project plan entitlements. Repeating a denied request does not grant access or consume quota.
Missing resourceNOT_FOUND, OFFER_NOT_FOUND, ITEM_NOT_FOUND, BUILD_NOT_FOUND, SANDBOX_NOT_FOUND, MEDIA_NOT_FOUND, BUNDLE_NOT_FOUND, EVENT_NOT_FOUND, PROMOTION_NOT_FOUND, SELLER_NOT_FOUNDCheck the identifier and operation in the deployed contract.
Unsupported method/contentMETHOD_NOT_ALLOWED, UNSUPPORTED_MEDIA_TYPEUse the documented method and content type; consult Allow where present.
Bounded workCATALOG_ROOT_TOO_LARGE, CATALOG_HYDRATION_TOO_LARGE, MANIFEST_NOT_COMPARABLEReduce requested work or choose comparable resources as described by the operation.
Quota exhaustedRATE_LIMITED, MONTHLY_QUOTA_EXCEEDED, PERIOD_QUOTA_EXCEEDED, EXPENSIVE_BUDGET_EXCEEDEDWait for Retry-After (60s minute window, 00:00 UTC calendar-month reset, or paid billing-period reset); inspect RateLimit, RateLimit-Policy, and X-RateLimit-Policy, or manage your plan in the dashboard.
Quota uncertainQUOTA_UNAVAILABLERetry after the indicated delay. The request was not forwarded without confirmed admission.
Upstream/service unavailableORIGIN_UNAVAILABLE, SEARCH_UNAVAILABLE, NATURAL_LANGUAGE_SEARCH_UNAVAILABLE, INTERNAL_ERRORRetry with backoff where appropriate; report persistent failures with the request ID.
Operator configuration/provenanceORIGIN_NOT_CONFIGURED, WORKER_AUTH_NOT_CONFIGURED, UNTRUSTED_WORKER, MISSING_KEY_CONTEXT, INVALID_KEY_CONTEXT, NATURAL_LANGUAGE_SEARCH_NOT_CONFIGUREDContact the operator. Never obtain or send private Worker-to-origin credentials.

The deployed operation's response schemas and examples are available in the developer explorer. Response errors still count as attempted endpoint usage when a known request passed authentication, permissions, and quota admission. Authentication/permission failures, quota denials, unknown paths, and preflights are excluded from alert relevance.