Loading documentation…
Loading documentation…
Create a Credential and read a saved Steam inventory, with a refresh when needed.
Open the SteamCall Dashboard. Keep Default project for your first integration and create a Service Account for your application. Select the Current inventory (steam.inventory.current.page.v1) and Refresh inventory (steam.inventory.refresh.v1) permissions, then issue a Credential. Its secret value is your API key and is available only when issued; copy it and store it securely.
Export the key only in your local shell or secret manager. Never commit it or place it in a URL.
export STEAMCALL_API_KEY="your_application_key"Call Inventory capabilities without a key to see which game inventories support Current and Refresh. This guide uses Team Fortress 2: application 440, context 2. These game/context pairs are separate from your Service Account's permission scopes.
Replace the Steam ID with a public test inventory you are permitted to use. Current is the normal application read and never contacts Steam.
Run these examples on your server or development machine, not in browser code. For Python, install the dependency with python -m pip install requests. For TypeScript, use a server runtime with fetch and AbortSignal.timeout support.
Each returned Current page costs 1 credit. If you need a new scan, Refresh temporarily reserves up to 125 credits and charges for the completed inventory size. See Usage & credits before running paid requests. Status polling costs no credits but still counts toward your request limit.
curl --fail-with-body --max-time 15 --request GET \
'https://api.steamcall.com/v2/steam/users/76561198000000000/inventory/440/2/current' \
--header "X-API-Key: $STEAMCALL_API_KEY"404 inventory_revision_not_found means the inventory has not been committed yet; it is not an empty inventory. Follow Refresh inventory to submit an idempotent complete refresh, poll status, and retry Current after completion.
Treat the generated Current response schema as canonical. Retain X-Request-ID when contacting support, keep the key server-side, and read Build an inventory integration before adding retries or schedules.