Signals. Infra
Error types

Invalid API key

HTTP 401 · `invalid-key` — what it means and what to do about it.

HTTP 401 · type: https://docs.signals.ai/errors/invalid-key

The Bearer token did not match a live key. The key is malformed, unknown, or belongs to a deleted account.

What to do

Check the header is Authorization: Bearer sk_live_… (or sk_test_…) and that the value is the full secret, not just the 16-character prefix. Mint a replacement at developers.signals.ai. Do not retry unchanged.

The response shape

Every error is RFC 9457 application/problem+json and carries a request_id, which is also returned as the X-Request-Id header on every response, success or failure. Quote it when contacting support.

{
  "type": "https://docs.signals.ai/errors/invalid-key",
  "title": "Invalid API key",
  "status": 401,
  "detail": "…",
  "request_id": "req_9f2c…",
  "instance": "/v1/…"
}

See all error types for the full catalog.

On this page