Platform Release 17 April 2019
Stores beta let you model the context your customers shop in, e.g. physical retail locations, brand stores, or country-specific stores. Currently, a store holds carts and orders. During the Beta phase, we plan to let the store define what subset of resources within a project is available in the context of the store. For example, which products are sold at what price, and which currency or shipping methods can be used.
Additionally, a store can be used for permissions. With an OAuth scope like
manage_orders:acme-inc:luxury-brand, an API client can only work with carts and orders inside the
luxury-brand store, but not within the
budget-brand store. See the GraphQL section for more details. Coming soon to the Merchant Center, a team can be given permission to only work with orders from one store.
- [API] Added the new resource Store.
- [API] Added the type KeyReference.
- [API] Cart and Order have a new field
- [API] When creating a Cart, the
storecan be referenced by its ID or key.
- [API] New OAuth scopes
- [API] New store-based OAuth scopes
- [GraphQL API] Added Stores, and the
storefields on the types
[GraphQL API] Added the query fields
inStores, as well as a
storeKeyargument to cart and order mutations. These can be used with the new store-based OAuth scopes.
- [Doc] Documented Reference expansion on GraphQL.
- [Doc] Documented Extension error responses.