Team Fortress 2 inventories through one stable endpoint.

Stable behavior across TF2 inventory pages

A request returns exactly one Steam inventory page. Cache headers report freshness and source, while stable errors let your application distinguish invalid input, limits, upstream failures, and temporary unavailability.

• One normalized JSON response model across supported Steam economies.
• Durable public page snapshots with observable HIT, MISS, STALE, and BYPASS behavior.
• Cursor pagination that preserves Steam's real page boundaries.
• Bearer API-key authentication, explicit timeouts, and stable error codes.
• Optional authorized access for inventories that need a Steam session.

Credentials stay outside public browser code

Call ItemData from your backend and send the API key as a Bearer token. If an authorized Steam session is required, keep it in request memory and never expose it to client-side analytics.