Skip to main content

​
invalid_token

Common causes:
  • Mistyped or truncated token. Re-copy from your password manager and retry.
  • The token was minted in a different environment (live vs test) than the one you’re hitting. Double-check the prefix (scripe_sk_live_ vs scripe_sk_test_).
  • The token was revoked very recently and the cached row was already evicted, so the request makes it past the cache and finds no live row. Mint a new key.
  • (Rare) the workspace was deleted or its Clerk org binding broke. We fail closed in that case to avoid leaking row-existence signals.
If you’ve copy-pasted from a password manager, ensure no leading or trailing whitespace was included. Many secret stores strip newlines on copy but not on autofill.