Loading documentation…
Loading documentation…
Continue large inventory reads without duplicate work.
Large inventories require multiple pages. Live Page and Current both use opaque cursors, but the cursors represent different workflows and are never interchangeable.
Maintaining an existing V1 client? Use Legacy V1 pagination instead. Its start_assetid and last_assetid values are not V2 cursors.
| Cursor | What it continues | Contacts Steam | Keep unchanged |
|---|---|---|---|
| Live Page cursor | One customer's upstream Steam traversal | Yes | Customer, inventory and language |
| Current cursor | One immutable committed revision | No | Inventory, language and page size |
A cursor is not authentication. Every page requires an active Credential with the operation's permission and is billed to the caller. Current cursors pin the revision and price version and have an expiry; they are not bound to one Credential. Do not combine independent Live Page traversals or use either cursor type with the other operation.
Deduplicate by stable asset identity, and cap the total pages your job may request.
Current is the normal choice for full application reads. Each page is billed separately, but every cursor stays on the same revision. If a refresh completes halfway through, finish the old cursor chain consistently; start again without a cursor to see the new revision.
Steam returns continuation cursors rather than trustworthy page numbers. A caller reaches its conceptual page 8 only by following the cursor from its own page 7. SteamCall does not lock or coalesce independent Live Page cursor chains.
Apply one deadline and page limit to the complete read. If any page fails or the limit is reached, mark the candidate snapshot incomplete and keep the previously published snapshot unchanged.
Do not sort, increment, decode, store as a permanent bookmark, or otherwise interpret a cursor. Record the request ID for each failed page so one workflow retains enough evidence without storing credentials or complete payloads.
If you need a complete inventory but do not want to own this loop, use Refresh inventory; SteamCall's workers traverse all pages and publish atomically.