Looking for the Microsoft Store service-to-service REST reference (collections, purchase, clawback, grant, recurrences)? It lives in the API tab under Microsoft Store REST APIs.
In this section
Getting started
Overview, product types, Partner Center setup, testing, licensing, and troubleshooting.
Fundamentals
Basic store operations, DLC, trials, consumables, bundles, DWOB, and updates.
Manage from your services
Authenticate services, query entitlements, subscriptions, refunds, and User Store IDs.
PC-specific considerations
DRM, license tokens, mismatched-store-account handling, and sandbox switching.
Microsoft Store REST APIs
Reference for the v8/v9 collections, purchase, clawback, grant, and recurrences endpoints. Full reference now lives in the API tab under Microsoft Store REST APIs.
Franchise game hubs
Group multiple products under a single Store franchise hub.
Big picture: how the pieces connect
- Partner Center — where you create products (base games, add-ons, bundles, season passes, subscriptions, consumables), define pricing and availability, and assign identifiers (StoreId, Product ID, BigId, SKU ID).
MicrosoftGame.config— ships inside your title package and binds the running executable to the Store product viaTitleId,StoreId, andMSAAppId.- XStore runtime APIs (
XStore*) — client-side calls made from your game to enumerate products, query licenses and entitlements, show purchase UI, and report consumable fulfillment. - XPackage APIs (
XPackage*) — mount and license optional packages (DLC), install chunks, and observe package state changes. - Microsoft Store S2S REST APIs — server-side endpoints your backend calls to authoritatively query entitlements, fulfill consumables, grant products, look up subscriptions, and process refunds/clawbacks.
- User Store ID (UserStoreId) — a short-lived key your title obtains via
XUserGetTokenAndSignatureAsync(orXStoreGetUserCollectionsIdAsync/XStoreGetUserPurchaseIdAsync) and hands to your service so the service can call the Store on behalf of that user.
Client versus service
Almost every Store scenario has both a client-side (XStore) and a service-side (S2S REST) path. Use the client for real-time UX (show the buy button, unlock content, report a consumable spend); use the service when authority matters (fulfilling a virtual-currency spend that must survive title reinstalls, granting a promo item, detecting Game Pass, processing a refund). A reliable pattern:- Client detects the purchase or spend and shows immediate UX.
- Client sends a UserStoreId to your service.
- Service calls the Store S2S API to confirm the entitlement or fulfill the consumable and updates your database of record.