err:unkey:authentication:key_not_foundExample response
Likely causes
- The root key was deleted or rotated.
- The token has a typo or was copied incompletely.
- You sent one of your own API keys instead of a root key. Then
detailis justThe provided root key is invalid., without the second sentence.
How to fix
- Check the token against the root key you created in the dashboard. Root keys start with
unkey_. - If you rotated or deleted the key, create a new one and update every service that uses it.
- Don’t send your own API keys in the header. They go in the body of
keys.verifyKey.
err:unkey:data:key_not_found. A keys.verifyKey result of valid: false with code NOT_FOUND isn’t an error: the call worked and is telling you about one of your keys.
Related errors
err:unkey:authorization:key_disabled: the root key exists but is disabled.err:unkey:authorization:workspace_disabled: the key’s workspace is disabled.err:unkey:data:key_not_found: a key referenced in a request body or path doesn’t exist.