auth_invalid

API key not valid

Code: auth_invalid · HTTP status: usually 401

A credential was sent, but it is not a current STOQ API key for any store.

How to fix

Copy the key again from the STOQ app’s API key page and resend. A rotated or revoked key stays invalid.

Example response

{
  "code": "auth_invalid",
  "type": "https://docs.stoqapp.com/v2/docs/api-v2/errors/auth-invalid/",
  "title": "API key not valid",
  "status": 401,
  "detail": "Invalid API key. The credential sent is not a current STOQ API key: it was mistyped, rotated or revoked. Copy the key again from STOQ → Back in stock alerts → Integrations → API Key and resend; see https://docs.stoqapp.com/docs/api-key/",
  "errors": [
    "Invalid API key"
  ],
  "details": [
    {
      "code": "auth_invalid",
      "message": "Invalid API key",
      "path": null,
      "value": null,
      "expected": null
    }
  ]
}

Every API v2 and MCP failure carries code and a type link to its page here. See Errors & Responses for the full envelope.