Community Market errors
Handle market validation, rate-limit, and upstream outcomes safely.
On this page
The generated Market responses own the exact error schema and status codes. Use documented codes for program logic and preserve X-Request-ID for safe investigation.
Retry selectively
Correct invalid application, item-name, or currency inputs before retrying. Apply bounded backoff only to documented transient outcomes and honor Retry-After when present.
Keep missing observations, rate limiting, product availability, and transient Steam failures separate in your application. Preserve a prior cached observation according to a declared stale policy instead of rewriting it as a fresh zero value.
Record the operation, currency, UTC timestamp, status, and request ID for diagnosis. Do not record the API key or full request headers. See Errors for the shared classification model.