err:unkey:data:identity_not_foundExample response
Likely causes
- You attached a key to an
externalIdbefore creating the identity. - The ID or
externalIdhas a typo or a case difference.externalIdis matched exactly. - On
keys.createKey,keys.updateKey, orkeys.migrateKeys, the identity is in a different from the keyspace. - Your root key can’t read the identity.
identities.updateIdentityandidentities.deleteIdentityreturn this 404 instead of a 403. A key that can read the identity but lacks the action gets a 403err:unkey:authorization:insufficient_permissionsthat names the missing permission.
How to fix
- Create the identity with
identities.createIdentitybefore you attach keys to it. - Check the
externalIdfor typos and case.identities.listIdentitiesshows what exists. - On
identities.updateIdentityoridentities.deleteIdentity, check the root key’s permissions before you decide the identity is gone.
Related errors
err:unkey:data:identity_already_exists: an identity with thatexternalIdalready exists.err:unkey:data:key_not_found: the key doesn’t exist.