Windows app and game catalog research
Mit Microsoft Store-Endpunkten verwandelst du windows app and game catalog research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn Microsoft Store's own JSON APIs — the same calls apps.microsoft.com itself makes — into normalized data for Windows app/game intelligence, ASO research, and storefront monitoring. Covers apps, games, devices, passes, fonts, and themes across 14 endpoints. Credential-free.
Extract Microsoft Store app, game, and device listings, category browse, search, charts, spotlight shelves, publisher catalogs, and reviews as structured JSON.
Endpunkt-Familien
6
Dokumentierte Parameter
77
Beispiele
14
Live-Katalog-Snapshot
Aktive Endpunkte
14
Methoden
GET
Pflichtparameter
24
Schema-Referenzen
14
{
"platform": "Microsoft Store",
"endpoint": "microsoftstore-categories",
"method": "GET",
"path": "/microsoftstore/categories",
"auth": "apiKey"
}Use Cases
Extract Microsoft Store app, game, and device listings, category browse, search, charts, spotlight shelves, publisher catalogs, and reviews as structured JSON.
Mit Microsoft Store-Endpunkten verwandelst du windows app and game catalog research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Microsoft Store-Endpunkten verwandelst du store ranking and chart monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Microsoft Store-Endpunkten verwandelst du review and rating analysis in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Microsoft Store-Endpunktkatalog — 14 Endpunkte, 77 dokumentierte Request-Parameter und 14 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
14 documented Microsoft Store endpoints, grouped into 13 request families — Reviews, Categories and Category, plus 10 more.
77 request parameters are documented across those Microsoft Store endpoints, 24 of them required — the full input contract is public before you write any integration code.
14 of the 14 Microsoft Store endpoints ship a recorded example response, and 14 carry a documented response schema — you can code against the real JSON before the first request.
Microsoft Store endpoints document their error responses (400, 404 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
14 hosted MCP tools back the Microsoft Store endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
Diese Karten werden aus dem aktiven Endpunktkatalog generiert, damit die Landingpage dieselbe API-Oberfläche widerspiegelt, die auch Docs und Playground nutzen.
/microsoftstore/reviews
/microsoftstore/categories
/microsoftstore/category
/microsoftstore/charts
/microsoftstore/editorial
/microsoftstore/events
Ausgewählte Endpunkte
/microsoftstore/categoriesReturns every accepted category for a department, and -- apps only -- each category's own finer subcategories (e.g. Books & reference -> E-reader, Fiction, Nonfiction, Reference). This is the discovery endpoint for the category/subcategory values accepted by /microsoftstore/search, /microsoftstore/category, and /microsoftstore/charts. Subcategories are apps-only: games categories have none. Credential-free public Microsoft Store data, live-verified and pinned rather than a passthrough call.
MCP-Tool microsoftstore_categories
/microsoftstore/searchReturns a page of Microsoft Store search results (apps, games, devices, and other listings) for a keyword, with cursor-based pagination and per-item publisher, rating, price, and media. media_type selects the department (apps, games, devices, passes, fonts, themes, tencent-android, tencent-mini, or all); category further filters within that department (the accepted set depends on media_type -- see the markdown doc for the full per-department lists). Pass the previous response's next_cursor to fetch the next page. Credential-free public Microsoft Store data, read directly from the store's own web API.
MCP-Tool microsoftstore_search
/microsoftstore/categoryReturns a page of a single department+category listing, cursor-paginated, with no search keyword required -- the credential-free way to list an entire category (search requires a non-empty query and returns nothing for an empty one). category is required; the accepted set depends on media_type (see /microsoftstore/search's markdown doc for the full per-department lists). media_type defaults to apps; all is not accepted here since it has no category filter upstream. Credential-free public Microsoft Store data, read directly from the store's own category-filter API.
MCP-Tool microsoftstore_category
/microsoftstore/suggestReturns typeahead-style Microsoft Store search suggestions for a partial search term: plain-text completions plus a short list of matching products (id, title, icon, department, and store URL). Credential-free public Microsoft Store data, read directly from the store's own autocomplete API.
MCP-Tool microsoftstore_suggest
/microsoftstore/productReturns normalized Microsoft Store listing details for a single product id: title, description, publisher, category, media type, aggregate rating and content-rating breakdown, price and SKU summary, size, supported platforms/languages, capabilities, version/release/update timestamps, feature callouts, and media (icon, poster art, screenshots, trailers). Credential-free public Microsoft Store data, read directly from the store's own page-data API.
MCP-Tool microsoftstore_product
/microsoftstore/chartsReturns a curated Microsoft Store chart (top free, top paid, top grossing, trending, deals, new releases, getting-started picks, or -- apps only -- most popular), optionally scoped to a category/subcategory and, for games, by Xbox Game Pass availability or player count. Some charts (notably NewAndRising) can legitimately return fewer items than page_size even at the first page -- that reflects real upstream sparsity for that chart, not a parsing gap. Credential-free public Microsoft Store data, read directly from the store's own curated-list API.
MCP-Tool microsoftstore_charts
Verwandte APIs
App Stores
Collect Chrome Web Store extension discovery, listing, review, permission, and privacy signals as normalized JSON for app intelligence and browser-extension research workflows.
App Stores
Run App Store search queries and turn App Store listings, rankings, reviews, and developer pages into structured JSON for app intelligence, ASO research, and competitor monitoring workflows.
App Stores
Build Android app intelligence workflows with structured Google Play data.
So scrapst du Microsoft Store
Every Microsoft Store endpoint reads directly from the store's own same-origin JSON APIs at apps.microsoft.com/api/... — the same calls the live site makes to render search, category, chart, and product pages — so no API key, cookies, or browser impersonation is needed upstream. Coverage spans 8 departments (apps, games, devices, passes, fonts, themes, tencent-android, tencent-mini).
/microsoftstore/categories returns the live-verified category/subcategory taxonomy for a department, feeding the category values /microsoftstore/search, /microsoftstore/category, and /microsoftstore/charts all accept.
/microsoftstore/search takes a keyword (optionally scoped by media_type and category); /microsoftstore/category lists an entire category from scratch with no keyword required, cursor-paginated.
/microsoftstore/charts returns curated lists (top free, top paid, trending, and more); /microsoftstore/spotlight returns the hero banner shelf; /microsoftstore/events returns the Special Events promotional shelf — three distinct shelves the real site itself keeps separate.
/microsoftstore/product returns full listing details for a product id; /microsoftstore/publisher lists everything one publisher has shipped; /microsoftstore/related returns products related to a seed product id.
/microsoftstore/reviews returns one page of written reviews for a product; /microsoftstore/reviews/summary returns its aggregate rating distribution, most-critical, and most-favorable review.
FAQ
Eight media types: apps, games, devices, passes, fonts, themes, tencent-android, and tencent-mini. Most endpoints default to apps or all; category listing, charts, and special events each restrict which departments they support (for example /microsoftstore/events only supports apps and games, matching what the live site itself offers).
/microsoftstore/search requires a non-empty query keyword. /microsoftstore/category is the credential-free way to list an entire department+category from scratch, with no keyword, cursor-paginated.
/microsoftstore/charts returns ranked lists (Top Free, Top Paid, Trending, and more, optionally by category). /microsoftstore/spotlight returns the large featured hero banners shown at the top of the store or a department landing page. /microsoftstore/events returns the smaller, separate "Special events" promotional shelf. All three are distinct shelves on the real site.
Only from a product that carries one — there's no standalone discovery endpoint for editorial ids. Call /microsoftstore/editorial with an editorial_id found embedded in that product's own award.editorial_id field, returned by search, category, charts, publisher, or related.
No. These endpoints read the same public, credential-free JSON APIs the live apps.microsoft.com storefront itself calls to render its pages — no Microsoft account, developer credentials, or the separate (developer-facing) Microsoft Store Submission API is used. Crawlora API authentication is still required.