Starting November 20, 2026, the and mutations reject online access tokens for users who don't have access to the app. The change applies to all GraphQL Admin API versions.
What changed
Both mutations now require an offline access token, or an online access token for a user who has access to the app. The , , and access scope requirements don't change.
When the check fails, the mutation returns an access denied error and no payload, and the server pixel's endpoint stays the same. The error message is the same one you get for a missing access scope, so it doesn't mention user access.
Who's affected
This affects apps that call these mutations with an online access token for a staff member who doesn't have access to the app. Offline access tokens, and online access tokens for users who have access to the app, work as before.
If your app calls these mutations with online access tokens, then make sure the staff member has access to your app in the Shopify admin, or call the mutations with an offline access token, for example from a background job. Handle the access denied error either way.
Why this matters
The update mutations now make the same user access check that and already make, so only a user who has access to an app can change where its server pixel sends events. This is a security fix, so it applies to all API versions without a deprecation period.