app
Downgrades granted optional write access scopes to their matching read access scopes. For example,
downgrading removes and keeps , so the app can keep reading
products without asking the merchant to grant again.
Revoking a write scope with
also removes its read access when the read scope was only granted through the write scope. Use this
mutation instead when the app still needs read access.
The mutation always acts on the calling app's own installation on the shop. Only write scopes that the app declares as optional can be downgraded. Required scopes can't be downgraded. Write scopes that aren't currently granted are ignored.
Learn more about managing app permissions.
Arguments
- scopes ([String!]!)
- Anchor to scopesscopes•[String!]!required
The handles of the write scopes to downgrade, for example
. Each granted write scope is replaced with its matching read scope.
- downgraded ([AccessScope!])
- userErrors ([AppDowngradeAccessScopesUserError!]!)
- Anchor to downgradeddowngraded•[Access
Scope!] The write scopes that were downgraded. The app keeps the matching read scope for each one.
Show fields
- Anchor to userErrorsuser•[App
Errors Downgrade Access Scopes User Error!]! non-null The list of errors that occurred from executing the mutation.
Show fields