Migrate from SteamWebAPI to WOK

SteamWebAPI's current inventory documentation checked October 25, 2026 describes its batch result as the first Steam page per requested ID, at most 2,000 assets. An inventory fitting one page may already be complete. For larger inventories, its documented single-inventory continuation follows the last_assetid response header with start_assetid until that header is absent. A short item array alone is not a completion signal.

WOK follows the pages returned by its public Steam source before publishing a successful inventory. A failed continuation returns an error rather than a partial success. Existing safety limits and source deadlines still apply. This is public_only coverage, not proof of every owned item: Steam may omit recently received items. See the inventory scope and response contract.

When you need all item rows, use top=0 on WOK's native inventory GET or top: 0 in JSON or streaming batch payloads. The default top: 10 is a display projection, not the source inventory size. Grouped rows use count, so row count is not always asset quantity. If you opt into single-inventory output pagination with limit, it overrides native top; follow WOK's returned signed cursor with the same options. That cursor reads an existing cached snapshot; it is not Steam's start_assetid. Changed or expired snapshots return HTTP 409. Read the output pagination, currency and export contract before adapting continuation code.

Check a saved page sequence

This explicitly fictional example is a local acceptance fixture, not a provider response, account scan or price quote. Two successful saved pages contain 2,300 observed assets. If the second page fails, the first 2,000 assets are not a complete valuation. No request or API key is needed to inspect it.

{
  "fictional": true,
  "pages": [
    {"saved_assets": 2000, "next_page": "saved-page-2"},
    {"saved_assets": 300, "next_page": null}
  ],
  "observed_assets": 2300
}

SteamWebAPI documents that private batch inventories may be an empty array or cached data. Validate those states against saved responses instead of treating every empty array as observed empty. WOK's single native route, compatibility route and native batches have different error envelopes; use the WOK OpenAPI contract and the existing offline response exercise. Streaming also needs its final verified complete record; see the stream completion and targeted retry rules.