Steam on any website.

The Steam Web API exposes dozens of distinct content endpoints across several interfaces, and each maps to a different job. The owned library is fetched through IPlayerService/GetOwnedGames with the include_appinfo and include_played_free_games flags, returns up to 2,000 owned titles per profile with playtime in minutes, last-played timestamp, and the appid that powers every other call. This is the right endpoint for a personal homepage, a developer portfolio that lists shipped games alongside personal favourites, or any place where the breadth of a library matters. The wishlist is fetched through the public IWishlistService/GetWishlist endpoint, returns priority order, current sale state, and the per-region price for every wishlisted title, and is the right endpoint for a creator gift page, a Patreon-backed wishlist reveal, or a personal homepage where conversion to store clicks matters more than back catalogue depth. Achievements come from ISteamUserStats/GetPlayerAchievements paired with GetSchemaForGame for the icons and display names, and ranked against GetGlobalAchievementPercentagesForApp for global rarity. This is the right endpoint for proving expertise: a 100 percent completion in a notoriously hard game, a sub-1-percent ultra-rare unlock, or a curated Hall of Fame of the rarest moments across a library. Now-playing and recent activity come from IPlayerService/GetRecentlyPlayedGames combined with the player summary in ISteamUser/GetPlayerSummaries, which returns the gameextrainfo field whenever a profile is currently launched into a game. This is the right endpoint for streamers who want a live in-game indicator next to a Twitch embed, or for review-site authors who want to show what they are currently grinding. There is a fifth surface worth knowing: Steam community reviews, surfaced through the public store reviews endpoint with cursor-based pagination. Mirroring your authored Steam reviews onto your own blog turns Valve-owned content into domain-owned content for SEO. Picking the right combination of endpoints at the start saves you a re-embed cycle later, and Poper supports every major surface from the same widget config so you can switch primitives without rewriting your site code.

Every Steam widget on the market is gated by the same thing: the Steam Web API, which Valve has documented at partner.steamgames.com and developer.valvesoftware.com since 2010 and which has remained remarkably stable across more than fifteen years. Authentication is a single API key issued at steamcommunity.com/dev/apikey, tied to the Steam account requesting it, and required for every endpoint outside the read-only public surface. The key is server-side only and must never ship to the browser, because anyone with the key can exhaust the daily 100,000-call quota in minutes by hitting any expensive endpoint in a loop. Most third-party Steam widgets fail in one of two ways. The first failure mode is to skip the API entirely and scrape steamcommunity.com pages, which is brittle (Valve tweaks the markup roughly twice a year and every scraper breaks), slow (full-page HTML loads versus 4KB JSON payloads), and rate-limited at the IP level rather than the key level so a popular widget gets throttled the moment it goes viral. The second failure mode is to ship the API key to the browser as a query parameter, which leaks the key on first page-load, lets anyone copy it, and either gets the key revoked by Valve or burned by abuse within hours. Poper handles every Steam Web API call server-side. We resolve vanity URLs to 64-bit SteamIDs once at connect time via ISteamUser/ResolveVanityURL, cache the mapping in our edge layer for the lifetime of the widget, then poll the appropriate endpoints on a tier-dependent schedule. Owned library refreshes every 6 hours on Free and every 30 minutes on Pro. Wishlist refreshes on the same cadence. Now-playing refreshes every 5 minutes on Business. Achievement payloads cache for 24 hours since unlock states change rarely and the schema changes even less often. The result is roughly 50 to 100 times more headroom than a browser-based widget, comfortable safety margin against the 100,000-call daily quota, and complete isolation between visitors hitting your site and Valve's API rate limits.

Steam has the most granular privacy model of any major gaming platform, and any widget that ignores it either breaks for half its users or surfaces hidden data and gets the user banned. The Steam profile privacy field has four states: public, friends-only, private, and the deprecated friends-of-friends. The owned game list has its own three-state field: public, friends-only, private. The total playtime field is independent again, as are the wishlist, the achievement showcase, the inventory, and the comments wall. A user can publish a fully public profile with private game details, or a private profile with a public showcase. The Web API respects every privacy setting at the endpoint level: GetOwnedGames returns an empty games array for any profile where game details are not public, GetPlayerSummaries returns only the public profile fields when the profile itself is private, and any attempt to read achievement data on a non-public profile returns a 403. Most third-party widgets handle this badly, either showing a confusing error message that tells visitors the profile is broken, or guessing the profile is empty and rendering a blank embed with no explanation. Poper detects every privacy state on connection and renders a helpful, branded fallback card that explains exactly what is private and how the profile owner can adjust it. For private library cases, we offer a one-click guided flow that links the owner to steamcommunity.com/my/edit/settings with the right tab pre-selected. For friends-only library cases, we surface only the public summary fields and offer a Steam Group join CTA instead of a games list. The same logic applies to wishlist privacy, which is independent again: a user can have a fully public profile and a private wishlist (default for new accounts) or vice versa. Surfacing this clearly in the widget builder saves dozens of support tickets and protects every user from the embarrassment of a broken-looking embed.

Steam in 2026 is no longer just a desktop game store, and any modern Steam widget needs to reflect the platform-level features Valve has shipped since the Deck launched in February 2022. The Steam Deck verified rating is a four-tier system: Verified (works perfectly out of the box), Playable (works with manual config), Unsupported (does not work on Deck), and Unknown (Valve has not tested yet). The rating is exposed on every store page and surfaced through the appdetails endpoint, which Poper calls once per game per week and caches at the edge. For creators and reviewers who emphasise handheld play, surfacing the Verified badge directly on the library grid is a major credibility signal. The Proton compatibility tier (Platinum, Gold, Silver, Bronze, Borked) comes from the community-maintained ProtonDB project rather than Valve directly and is opt-in in the Poper widget builder. Steam Workshop subscriptions are exposed through the IPublishedFileService interface and matter for indie creators who ship Workshop content alongside their main games. Steam Family Sharing membership and Steam Cloud sync state are both surfaced where the API allows. Achievements deserve their own treatment: the rarity field comes from GetGlobalAchievementPercentagesForApp and represents the percentage of global owners who have unlocked each achievement. Anything under 10 percent is rare, anything under 1 percent is ultra-rare, and the truly hardest achievements (the Cookie Clicker Hardcore unlock, the Dark Souls Lord of Cinder solo no-death run) sit at fractions of a percent globally. Surfacing rarity on the achievement card with a colour-coded badge turns a wall of icons into a credibility-led showcase. Indie game developers building a portfolio site benefit doubly: their own shipped games can be highlighted with a developer badge alongside their personal library, and their own ultra-rare achievements (often unlocked only by their own QA team) become a conversation starter for sponsorship and partnership pitches. Poper auto-detects developer ownership through the appdetails publishers field and offers a one-click Mark as my game toggle in the widget builder.

A naive Steam embed is one of the heavier integrations you can put on a content page, and the size scales linearly with library breadth. A 500-game library at full capsule art resolution (header capsules are 460 by 215 pixels, hero capsules are 1840 by 860) can pull more than 8MB of imagery on first load, blow Largest Contentful Paint past 4 seconds, and regress Cumulative Layout Shift if the cards lazy-load without reserved dimensions. Embed multiple profiles in a team roster and you can lose 30 Lighthouse points before any other code runs. The fix is the lite-mode pattern, which renders only the small library capsule (231 by 87 pixels, roughly 4KB in WebP) and a thin metadata strip on initial load, then swaps in the full hero capsule, screenshot reel, and trailer only when the visitor clicks into a specific game. The same pattern works for wishlist cards and achievement showcases. Poper ships lite mode as the default, so all the Steam content you embed costs you no more LCP than the same number of static thumbnails. Visitors who click see the full Steam-store-style detail card with screenshots, trailer, system requirements, review distribution, and Steam Deck status. Visitors who scroll past pay nothing. The performance difference between lite mode and a naive full-capsule embed is the difference between a 92 Lighthouse score and a 60. Three additional optimisations Poper applies on top of lite mode. First, capsule art is served from steamcdn-a.akamaihd.net (Valve's official CDN) and converted to WebP on the fly through our edge layer, which typically halves capsule weight versus the default JPEG. Second, the click-to-expand uses CSS containment and content-visibility: auto so off-screen library cards never paint. Third, when a visitor does open a game detail card, we lazy-fetch screenshots and trailer URLs from the Steam appdetails endpoint at click time rather than at page-load, which keeps the initial HTML payload tiny. The combined result is that a page with a 500-game Steam library in lite mode often outperforms a page with a single naive full-capsule embed on every Core Web Vitals metric. If page speed matters to your SEO, this is the single biggest reason to choose carefully which Steam widget you embed.