HTTP 401Invalid API key

invalid_api_key

A credential was presented but it is not a live key — it was revoked, rolled, expired, or never existed.

This page is where the problem type URI https://usepostify.com/docs/api/problems/invalid-api-key resolves.

Common causes

  • The key was rolled or revoked in Settings → API keys and the old secret is still deployed.
  • The key was truncated or whitespace-mangled when copied into your secret store.
  • You're using a key from a different workspace or environment.

How to fix

  • Mint or roll a key in Settings → API keys and update your secret store — keys are shown once at mint.
  • Compare the key's prefix and last characters against the key list in settings.
  • After a roll with overlap, finish the migration before the overlap window ends.

Example response

401 · application/problem+json
{
  "type": "https://usepostify.com/docs/api/problems/invalid-api-key",
  "title": "Invalid API key",
  "status": 401,
  "code": "invalid_api_key",
  "detail": "The provided API key is not valid.",
  "request_id": "req_6f1f8a2b40d34cd2a6f1e2c9b8d7a601"
}

Related