Add Shop User Token, Analytics Queryable, Deprecate Scheduled Changes

3/6/2026, 12:01:15 AM

The schema now includes a shopUserAccessTokenCreate mutation that accepts a user email and returns a Shop Users API access token, its expiration, a refresh token, token type, and any user errors. New types MetafieldCapabilityAnalyticsQueryable and MetafieldCapabilityAnalyticsQueryableInput expose whether a metafield definition is eligible and enabled for analytics querying. The MetafieldCapabilities type gets an analyticsQueryable field returning the new capability object. The InventoryLevel.scheduledChanges field is marked deprecated and will be phased out in a future release, so clients should avoid relying on it. Clients using shopUserAccessTokenCreate should store the returned token for authenticated requests to the Shop Users API. These changes require developers to update queries to use the new analyticsQueryable field and plan for the removal of scheduled changes support.

Mutation Changes

βž• Added Mutations (1)

shopUserAccessTokenCreate

Creates a Shop Users API access token for a specific Shop user.

Type Changes

βž• Added Types (3)

πŸ—οΈMetafieldCapabilityAnalyticsQueryableβž• AddedOBJECT

The analytics queryable capability of a metafield definition.

Fields: eligible, enabled
πŸ“₯MetafieldCapabilityAnalyticsQueryableInputβž• AddedINPUT_OBJECT

The input fields for the analytics queryable capability.

πŸ—οΈShopUserAccessTokenCreatePayloadβž• AddedOBJECT

Return type for shopUserAccessTokenCreate mutation.

Fields: accessToken, expiresIn, refreshToken, tokenType, userErrors

πŸ”„ Modified Types (2)

πŸ—οΈInventoryLevelπŸ”„ Modified
πŸ”„ Field modified: scheduledChanges
πŸ—οΈMetafieldCapabilitiesπŸ”„ Modified
βž• Field added: analyticsQueryable

Indicate whether a metafield definition can be queried in analytics.