Public Store Page Access Notes

Public Store pages are not the same as official Steam Web API endpoints.

They may be useful, but they should be treated as browser-like public web traffic, not stable typed API traffic.

Starting with v1.1.0, steam-go exposes a small read-only client.Web.* layer for a few high-value Storefront, Community, and Market JSON endpoints. These methods are stable Go APIs, but their upstream payloads should still be treated as unofficial or volatile web surfaces.

Recent client.Web.* helpers also include handler-based paginators and small batch helpers for common read-only workflows:

• client.Web.Storefront.ListAppReviews
• client.Web.Community.ListInventory
• client.Web.Storefront.GetAppDetailsBatch
• client.Web.Market.GetPriceOverviewBatch

These helpers reuse the same request controls as the underlying single-item methods and keep the same read-only boundary.

Official API vs Public Store Page

Official Web API	Public Store Page
JSON-oriented	HTML-oriented
API key may be required	Browser-like request may be needed
Better suited for typed SDK methods	Better suited for best-effort extraction
More stable request shape	Page structure may change
Usually backend API style	Public website behavior

Recommended SDK Features

For Store-page-like or adjacent web access, consider:

• TrafficClassPublicStorePage
• TrafficClassCommunityWeb
• TrafficClassMarketWeb
• HeaderProfile
• RefererSelector
• TrafficCachePolicy
• TrafficBlockPolicy
• HostControl
• SessionControl
• route-specific proxy policy

Header Profile

profile := steam.DefaultPublicStoreHeaderProfileEN()

or:

profile := steam.DefaultPublicStoreHeaderProfileZH()

Referer

referer, err := steam.NewStaticRefererSelector(
    "https://store.steampowered.com/search/",
)

Short Cache

Cache: &steam.TrafficCachePolicy{
    TTL: time.Minute,
}

Block Detection

BlockPolicy: &steam.TrafficBlockPolicy{
    HTMLSniffBytes: 4096,
}

Practical Advice

• Prefer built-in client.Web.Storefront.*, client.Web.Community.*, and client.Web.Market.* methods when the SDK already exposes the JSON endpoint you need.
• Prefer paginator or batch helpers for common reviews, inventory, app details, and market price overview loops instead of hand-rolling repeated request code.
• Do not treat HTML pages as stable APIs.
• Keep parsing code isolated from the core Web API client.
• Use cache for repeated reads.
• Use low concurrency.
• Watch for 403, 429, and HTML challenge pages.
• Prefer official Web API methods when available.