---
title: "Invalid API Key"
description: "The request has no X-API-Key header, or its key is unknown or belongs to a blocked account. Send a valid key alone in X-API-Key."
canonical: "https://signatureapi.com/docs/v1/errors/invalid-api-key"
source: "https://signatureapi.com/docs/v1/errors/invalid-api-key.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T11:41:57Z"
---

# Invalid API Key

The request has no X-API-Key header, or its key is unknown or belongs to a blocked account. Send a valid key alone in X-API-Key.

_Last verified against API version 1.18.0._

## What Happened

The API could not authenticate the request. Every public API authentication failure returns this error, whatever the cause. The usual causes are:

- The `X-API-Key` header is missing or empty.
- The key does not match any API key.
- The account that owns the key is blocked.

## Example response

```json 401 Unauthorized (application/problem+json)
{
  "type": "https://signatureapi.com/docs/v1/errors/invalid-api-key",
  "title": "Invalid API Key",
  "status": 401,
  "detail": "Please provide a valid API key in the X-Api-Key header."
}
```

## How to Fix

- Check that the key is complete and not truncated. API keys start with `key_test_` or `key_live_`, and the prefix is part of the key.
- Send the key alone in the `X-API-Key` header. Do not add a `Bearer` prefix, use the `Authorization` header or put the key in the query string.
- Confirm in your [Dashboard](https://dashboard.signatureapi.com) that the key still exists and has not been deleted or regenerated.
- If the key is correct and current, contact support. Authentication also fails for a blocked account.
- See [Authentication](https://signatureapi.com/docs/api/authentication) for an example request.

Still stuck? [Contact support](https://signatureapi.com/support).
