API products

Inventory

Read live pages, refresh complete inventories, and serve committed current state.

Open API Reference

COMMON TASKS

Start with the task in front of you.

Read current inventoryServe fast, complete, revision-pinned inventory pages without contacting Steam.Refresh an inventoryCollect every Steam page asynchronously and publish a complete revision.Load one live pageCall Steam inline when you deliberately need only one upstream page.Handle paginationUnderstand Live Page and Current cursors without mixing them.Understand item descriptionsJoin reusable item metadata correctly.Handle inventory errorsInterpret privacy, validation, and upstream failures.

GUIDES

Build beyond one request.

Build an inventory integrationChoose a workflow and manage refresh, status, and Current reads.Handle private inventoriesRespond safely when visibility prevents retrieval.Synchronize inventory dataChoose freshness rules while SteamCall owns complete collection and single-flight work.

One Inventory product, three workflows

The table shows prepaid prices. Subscription-funded requests use fresh inventory units or stored page reads instead; see Usage & credits for pooled allowances and optional prepaid fallback.

Workflow	Operation	Contacts Steam	Result	Billing
Read saved inventory	`GET .../current`	No	A page from the latest complete revision	1 credit per returned page
Collect a complete inventory	`POST .../refresh`, then poll status	In a worker	Publishes after all pages succeed	1 credit per started 2,000 observed assets; 1–125 credits
Read one live page	Live Page request	Yes	One upstream page	Live Page price per requested page

For most applications, use Refresh → Status → Current. Refresh collects a complete inventory. Status tells you when it is ready. Current reads the saved result without contacting Steam.

Use Live Page when you need one page directly from Steam or are maintaining an existing integration. If your client uses a V1 URL, follow Legacy V1 pagination.

Simultaneous refresh requests for the same inventory may share collection work. Each customer still receives their own refresh status and billing result; you do not need to coordinate with other SteamCall customers.

Games and contexts

Game	`app_id`	Usual player `context_id`	Support level
Team Fortress 2	`440`	`2`	Current and Refresh supported

Context 2 is TF2's ordinary player backpack. It is not a universal Steam context number. Current and Refresh reject every scope not returned by Inventory capabilities. Live Page accepts other positive app and context IDs as a best-effort passthrough, which is not a tested support commitment.

Integration model

Start with Current inventory and Refresh inventory. Each page contains complete request and response examples before linking to the generated contract. Then review pagination, item descriptions, and the beginner-to-advanced integration guide.

Troubleshooting and support

Start with Troubleshooting. If escalation is still required, follow Support guidance and include the request ID, operation, UTC time, and HTTP status—never a credential.