OAuth and HTTP guides

Compare requested and granted OAuth scopes from a saved response

·

When an OAuth integration has fewer permissions than expected, compare the scope names recorded by your app and provider. Then check whether a missing name was declined, normalized under another scope, or supplied for a different provider.

OAuth Scopes Reference

Reconcile five GitHub scope names

Choose Compare lists and Load example. The requested value is read:user user:email read:org example:custom. The granted value is user:email read:user gist. The example represents two saved lists and contains five distinct names.

Choose Compare scope lists. Expect two names in both lists, two in Requested only and one in Granted only. example:custom is an invented name for this example and appears outside the snapshot. read:org is in the GitHub reference even though this recorded grant omits it.

Open Export the comparison and download the JSON. Check that both is ordered as read:user, then user:email, following the requested list. Each result includes an inReference field for the selected provider.

Reconcile five GitHub scope names
Result groupExpected names
Both listsread:user, user:email
Requested onlyread:org, example:custom
Granted onlygist

RFC 6749, section 3.3, Access Token ScopeGitHub OAuth Apps scopes and normalization

Check whether a broader scope covers a missing name

Change Requested scopes to user user:email and Granted scopes to user. The tool reports user:email as requested only because it compares literal values. GitHub documents that user already includes user:email and can store only the broader scope.

Find both names under Browse scopes and open the GitHub source. A provider can normalize a list or allow a user to grant less than requested. Determine the effective access from the provider's rules and the endpoint your app uses.

GitHub Apps use a separate permission model. For Microsoft Graph, check the delegated and application columns separately. For Slack, verify whether the method and scope apply to the saved bot or user grant.

GitHub OAuth Apps scopes and normalizationMicrosoft Graph permissions referenceSlack OAuth scopes reference

Choose a scope for the operation

Search the provider and the resource together. For example, under Google, compare the selected-file access of https://www.googleapis.com/auth/drive.file with the broader file visibility of https://www.googleapis.com/auth/drive.readonly. Check whether your workflow opens specific files or needs to find existing files across Drive.

For an identity integration, verify the provider's sign-in documentation separately from data access. For example, the Microsoft identity platform treats openid and offline_access differently from the Graph delegated scope Mail.Read.

Paste decoded scope names into the comparison. Choose Commas for a comma-separated capture. Preserve case and punctuation such as the dots in Microsoft and X scope names. Look up unknown names in the provider's current documentation.

OAuth 2.0 scopes for Google APIsMicrosoft identity platform scopes and permissionsX API OAuth 2.0 scopes

Common questions

Which fields should I export for a scope review?

Export the provider, reference date, comparison groups and exact scope names from the JSON. Use the recorded scope list and keep credentials out of the review.

Can I treat a scope match as proof that an API call will work?

A match shows that the recorded names agree. The provider still evaluates the app, grant type, consent, user permissions and target resource.

Why does Stripe list both read_only and read_write?

The Connect OAuth reference lists both values and limits read_only to registered extensions. Connect platforms must explicitly request read_write. Stripe Apps use a different permission model.

Sources

Put it into practice.

Related guides