scope_exceeds_creator means you tried to create an API key with a scope you do not hold yourself. Read this page if key creation fails with a 403 that names a scope.
What happened
Route:POST /v1/keys.
A key can never do more than the account that created it. OpenType checks every scope in scopes against the scopes of the caller: your role when you use the console, or the calling key’s own scopes when you create keys with a key. At least one requested scope is missing, and the message names it. No key was created.
A
member, for example, cannot create a key with billing_write or members_write.
How to fix
- Remove the named scope from
scopes, if the key does not need it. - If the key does need it, ask an owner or admin to create the key.
- If you create keys with a provisioning key, that key’s own scopes are the ceiling. Create the provisioning key with the scopes you intend to hand out, and
keys_write.
Example
secret_prefix to see which scopes it holds, then handle the refusal when you create a key. Listing keys needs keys_read; creating one needs keys_write.
Related
- Scopes and roles - which role holds which scope.
- Scopes - every scope and the routes it unlocks.
- API keys in the console - create a key from a preset scope set.
- Problem codes - every code, its status, and whether a retry can help.