Skip to main content

Fix a 401 or 403 API response

Separate authentication problems from role, feature, namespace and source-access denials.

A 401 and a 403 require different checks. Neither is resolved by repeatedly sending the same broad data request.

401: check authentication

  1. Confirm the destination is https://api.oddswire.io.

  2. For REST data reads, send exactly one X-API-Key header using your current account-owned key.

  3. Check whether the key was rotated or revoked, or whether the integration still has an old value.

  4. Do not substitute a browser session token, put a key in the URL or send multiple credential types.

403: check authorization

The credential may be valid while the request is outside the account’s role, feature, namespace, source, region, purpose or expiry. Use the free entitlements check and signed-in Coverage page. New accounts intentionally start without data grants.

Separate products need separate approval. For example, REST access does not unlock history, streaming, Terminal or alerts. A stopped source or expired review can remain denied even when another source works.

Contact support

Include the operation, request ID, approximate UTC time and redacted error code/detail. Do not send the key or Authorization header. Changing a namespace is appropriate only if it is actually approved for your account. See the error reference.

Did this answer your question?