Nintendo Game Store - Switch Catalog

Nintendo Game Store - Switch Catalog is the official retail layer of the Integrated Telecommunication Services slice: 8,941 sellable product records straight off Nintendo of America's My Nintendo Store, maintained by Nintendo itself and covering everything the company chooses to sell in the Americas - first-party tentpoles, third-party partners, hardware tie-ins like the Game & Watch units, and titles still sitting on pre-order.

The split worth knowing before anything else: 7,319 of those records are Nintendo Switch, with 1,107 Nintendo 3DS and 878 Wii U behind them and nine apiece on Android and iOS. Each one carries the two numbers pricing analysts actually fight over - msrp and lowestPrice - in adjacent columns, so discount depth is arithmetic instead of a second collection pass. Genre facets put Action at 4,461 records, Adventure at 3,749, Arcade at 2,614 and Puzzle at 2,439; ESRB facets cover Everyone at 4,313, Teen at 2,173, Everyone 10+ at 2,004 and Mature at 778.

Get a sample of this dataset - name the platforms or fields you need, and real rows come back before you commit to a feed.

One title, read straight off its catalog record:

title      : The Legend of Zelda(TM): Skyward Sword HD
platform   : Nintendo Switch        msrp       : 59.99 USD
lowestPrice: 59.99 USD              esrbRating : Everyone 10+
releaseDate: 2021-07-16             availability: Available now

And one from the other end of the lifecycle - announced, credited, unrated:

title      : Bayonetta(TM) 3
platform   : Nintendo Switch        genres     : [Action]
esrbRating : Rating Pending         numOfPlayers: 1 player
publishers : [Nintendo]             developers : [PlatinumGames]

The pair makes the point better than either row alone. The Skyward Sword record shows a mature listing where list price and lowest price agree - no promotion running - while the Bayonetta record shows what the catalog holds before retail maturity: no price yet, rating pending, but full studio credits and a player count already attached. Both fill the same field structure as every other one of the 8,941 rows, which is why a single query can sweep launch-window pre-orders, decade-old back-catalog and hardware tie-ins without schema changes.

Ten fields carry each record in the standard delivery, every definition verified against live catalog pages rather than inferred from documentation. Six more exist inside the same records and fold under additional fields on request: the product slug, the eShop nsuid identifier, ESRB content descriptors, and the free-to-start flag and last-modified timestamp - each populates on a title-dependent subset of the catalog rather than every row.

The msrp/lowestPrice pairing deserves its own line. Most game-price sources publish one number and call it pricing; here list price and current lowest advertised price sit side by side, which turns promotional cadence into a derived column - how often a title discounts, how deep, and how quickly it returns to full price. Availability badges do similar work for the future-facing end: 'Available now' versus 'Pre-order now' is the difference between a shipping product and demand you can measure before release.

• Geography - the Americas storefronts: the US English index anchors the set, with Canada English/French, Mexico Spanish and Brazil Portuguese siblings behind it. Other regions run their own sites and are not folded in, so a Europe or Japan pricing question needs a different feed rather than a filter here.
• Temporal - the catalog reaches back to the Wii U and 3DS era around 2012 and runs through current Switch releases, open pre-orders included. At observed store cadence roughly 40-60 records arrive new or changed each week, which is enough motion to make weekly monitoring meaningful without overwhelming it.
• Granularity - one record per sellable product SKU. Hardware tie-ins get rows the same as software, facet counts roll up cleanly by platform, genre, franchise and rating, and nothing aggregates away the individual title you came looking for.

The honest caveat: some records carry stale attributes. Titles long past launch have shown lingering 'Rating Pending' labels, and whether delisted products remain indexed indefinitely is undocumented - so treat any long-run analysis of exits as something a sample should settle first.

API, files, or your warehouse. Daily, weekly, or hourly.

You pick the channel and the cadence; the field dictionary above travels unchanged through all three. Rows arrive flattened into one observation per SKU with the vocabulary already normalized, so an msrp column compares against an msrp column without anyone re-parsing storefront markup. Cadence changes are a settings conversation, not a re-integration project, and a sample cut to your platforms and fields comes first either way.

• Market researchers and consultants size the Americas Switch catalog - 7,319 Switch titles - by genre, publisher and ESRB rating, using the official storefront as the frame rather than a bestseller approximation.
• Competitive-intel teams watch MSRPs, lowest prices, release dates and pre-orders across the official storefront, catching first-party price moves and third-party promotions as they land.
• E-commerce operators benchmark game retail pricing against both price columns per SKU, flagging where their own shelf sits above or below the official floor.
• Investors and quant researchers track first-party MSRP discipline versus discount depth over time - the two-column price design exists precisely for this comparison.
• Sales and growth teams mine publishers and developers on the catalog as account lists for tooling outreach, segmented by genre and catalog presence.
• Journalists, academics and students verify official US and Canada pricing, ratings and player counts against the primary record instead of secondary aggregation.

Market researchers and consultants, competitive-intel and product teams and e-commerce operators all score this dataset at relevance 3 in Datadory's persona reviews - respectively, catalog sizing by official facets, launch-and-promotion watching, and retail price benchmarking. Investors and quant researchers hold it at relevance 2: the msrp-versus-lowestPrice series supports pricing-discipline work even though realized transaction volumes live elsewhere. Developers and builders also sit at relevance 2 - one normalized SKU record beats maintaining a parser for a storefront whose HTML is deliberately merchandised rather than tabular. Across all six, the constant is the same: the data describes what Nintendo itself sells and charges, which makes it ground truth for any question about the Americas storefront and merely a strong signal for anything beyond it.

Four things, all knowable upfront. First, the four folded fields - slug, nsuid, ESRB descriptors, free-to-start and last-modified - populate on a title-dependent subset, so if your use case leans on eShop identifiers or descriptor text, say so when requesting the sample and check population rates on your own scope. Second, prices are storefront list and advertised-floor values in local currency, not transactions; teams needing realized street prices typically pair this set with a retail price-history feed. Third, regional scope stops at the Americas - Mexico and Brazil indexes exist, Europe and Japan do not, which matters for global pricing work. Fourth, the catalog is Nintendo's commercial property, which is why Datadory delivers derived, normalized rows into your environment under our own terms rather than passing raw storefront pages through.