Changelog

New guidance on customer context in the GraphQL Storefront API

Thanks to user feedback, the GraphQL Storefront API docs now explain when and how an authenticated customer shapes a request.

• New Customer Context page. A dedicated page covers how customer context works: how it can change a response (such as customer-specific pricing), when it’s required for an operation to work at all, and how to establish it client-side (session cookie) or server-side (the X-Bc-Customer-Access-Token header). It includes a reference table of known operations that require customer context, and holds the customer access token instructions previously kept on the Authentication page.
• Overview callout. The GraphQL API Overview now flags that some operations depend on customer context even though the schema doesn’t show it, calling out non-obvious cases like registerCompany.

For details, see Customer context in the GraphQL Storefront API.

GraphQL Schema Updates

The Storefront GraphQL schema adds a way to list a store’s enabled payment methods and a display-friendly shipping provider name. These fields are alpha and marked deprecated in the schema: do not use them in production yet.

Storefront GraphQL

• Enabled payment methods (alpha): the new paymentMethods connection on the Site type lists the payment methods enabled for the current store and channel, returned as the new PaymentMethod type (with entityId and name).
• Shipping provider display name (alpha): the OrderShipment type adds shippingProviderDisplayName, a human-readable version of the existing shippingProviderName.
• B2B company-user fields removed: the alpha companyUser query, the updateCompanyUser mutation, and the search filter on CompanyOrdersFiltersInput have been removed from the schema.

For schema details, browse the Storefront GraphQL API reference.