Loading documentation…
Loading documentation…
Handle validation, authentication, privacy, rate-limit, and upstream outcomes.
Use the documented status and error code together. The generated Inventory responses are canonical for the public error schema.
Do not retry validation, authentication, or privacy outcomes unchanged. Retry only documented transient failures with bounded exponential backoff and jitter.
Retain X-Request-ID with your safe application logs. Support can use it to investigate a request; never send an API key or Steam credential to support.
An inventory privacy outcome is not an empty successful inventory. A transient upstream outcome is not proof of privacy. Keep the structured outcome alongside any last successful snapshot and let product behavior decide whether labelled stale data may be shown.
Centralize this classification so background refreshes and interactive requests behave consistently. Continue with Handle private inventories and Errors.