Current inventory

Use Current to read a saved, complete inventory without contacting Steam. The first page chooses the latest saved revision. Every following page uses that same revision, even if a newer refresh finishes while you are reading.

Request

Set STEAMCALL_API_KEY to your Credential secret in your server environment and replace the example Steam ID with the inventory you want to read. The response below uses synthetic data.

curl --fail-with-body --max-time 15 \
  'https://api.steamcall.com/v2/steam/users/76561198000000000/inventory/440/2/current?language=english&page_size=2000' \
  --header "X-API-Key: $STEAMCALL_API_KEY"

440/2 means the ordinary Team Fortress 2 backpack. language controls description text, not asset ownership. page_size is at most 2,000. When next_cursor is present, send it back unchanged and keep the same language and page-size choices.

This example shows prepaid credit funding. Subscription-funded requests use the applicable Inventory allowance; see Usage & credits for the distinction.

Full 200 response

{
  "success": true,
  "data": {
    "scope": {
      "steam_id": "76561198000000000",
      "app_id": 440,
      "context_id": 2
    },
    "revision_id": "invrev_01KEXAMPLE",
    "observation_id": "invobs_01KEXAMPLE",
    "verified_at": "2026-08-23T18:42:06Z",
    "age_seconds": 37,
    "scan_window": {
      "started_at": "2026-08-23T18:41:58Z",
      "completed_at": "2026-08-23T18:42:06Z"
    },
    "assets": [
      {
        "appid": 440,
        "contextid": "2",
        "assetid": "123456789",
        "classid": "101",
        "instanceid": "0",
        "amount": "1"
      }
    ],
    "descriptions": [
      {
        "appid": 440,
        "classid": "101",
        "instanceid": "0",
        "market_hash_name": "Mann Co. Supply Crate Key",
        "tradable": 1
      }
    ],
    "total_count": 1,
    "total_amount": 1,
    "pagination": {
      "has_more": false,
      "next_cursor": null
    }
  },
  "meta": {
    "request_id": "req_01KEXAMPLE",
    "product_code": "steam.inventory.current.page.v1",
    "price_version": 1,
    "credits_charged": 1,
    "credits_remaining": 999,
    "billing_disposition": "charged",
    "billing_reason": null,
    "rate_limit": {
      "limit_per_minute": 120,
      "remaining": 119,
      "reset_seconds": 30
    }
  }
}

The important fields are:

• revision_id: the immutable complete inventory version being paged;
• verified_at and age_seconds: how fresh SteamCall's evidence is;
• scan_window: when collection started and finished; items may have changed on Steam during that interval;
• assets: owned item instances; assetid identifies one instance;
• descriptions: localized reusable metadata joined by classid + instanceid;
• total_count: item-instance count, while total_amount also accounts for stacked amounts;
• next_cursor: an opaque, revision-pinned continuation.

Cold inventory

Current never starts hidden work. If SteamCall has no committed revision, it returns 404 inventory_revision_not_found and charges zero credits. Request a complete refresh, poll its status, and retry Current only after the refresh reports a completed outcome.

When to use Current

Use it for profile pages, bot decisions, stored application state, periodic polling, and downstream search/index updates. A common application cache key is scope + language + revision_id + cursor. You may cache immutable pages by revision, but always re-enter through the first Current page when deciding whether a newer revision exists.

Do not use Current when you explicitly need Steam at request time; use Live inventory page. Continue with Pagination and Item descriptions.

Receive refresh notifications

Where Events is enabled, use a signed webhook or authenticated Project stream to learn when a refresh reaches a terminal outcome. Correlate the notification's Refresh ID with the request you accepted, deduplicate by event ID, and inspect the outcome before reading Current. A terminal notification can describe a private or failed inventory; it does not contain the inventory or guarantee a successful refresh.

Keep bounded status polling as a fallback when Events is unavailable. After a disconnect or missed notification, follow Events recovery and reconcile refresh status before reading Current. Events is not generally available and does not provide Images preparation notifications.