Skip to main content
Ask the owner to approve access again when a feature needs more permissions or accounts than they have shared.

Choose the required scopes

A scope is a permission name, such as profile:read. Check the operation’s API reference. Request the new scopes your feature needs. Existing approved creator scopes and accounts remain granted. Every successful code exchange includes a refresh token. A missing_scope response means the token lacks a required scope. additional_consent_required means the selected account has not approved that scope. Both require the owner to approve access.

Start authorization again

Generate a new state value and an S256 PKCE challenge to protect the request. Then open the authorization URL with the same environment’s client ID. The owner reviews the additional scopes and chooses which accounts receive them. A new scope is not added to unselected accounts. Check the callback on your backend. Then exchange its one-use code for tokens. The authorization keeps its identity after approval. The new code exchange issues an independent credential with the newly approved scopes; older credentials do not gain scopes. New account grants are available to existing credentials only within their issued scopes and each account’s approved actions.

Update your saved access

Store the new token response, then list granted accounts through the resource API and follow every page. Use the returned scopes rather than assuming everything requested was granted. Handle authorization.updated to update shared accounts and their actual granted scopes. Removing an account or revoking an authorization is a separate explicit action in OFAuth; narrower sign-in consent does not remove creator access. See lifecycle events. Next, make a request with an account that approved the operation’s scope.