Loading documentation…
Loading documentation…
Diagnose authentication, validation, inventory, and upstream failures.
Start with the symptom visible to your application. Capture the operation, UTC timestamp, HTTP status, structured error code, and X-Request-ID before changing retry behavior.
Confirm that the request runs on your server, targets https://api.steamcall.com, and sends one active Service Account Credential in X-API-Key. In the Dashboard, check the Credential lifecycle and the Service Account's Project, permissions, and rate policy. Do not retry the same rejected Credential in a loop.
Confirm the API host, method, path parameters, query parameters, and X-API-Key header. A validation error must be corrected rather than retried.
Compare the request with the API Reference, including exact parameter names and types. Avoid branching on message text; use the documented code and field details.
For Current reads, inventory_revision_not_found means SteamCall has no complete
stored revision for that inventory yet. It does not mean the inventory is empty
or private. Request a Refresh, check its status, and
retry Current after it completes successfully.
Check Steam privacy and identity inputs. Do not convert a private or upstream-unavailable state into an empty inventory.
Preserve the last successful snapshot separately. If the documented privacy outcome is present, guide the user to review Steam settings and retry on demand instead of polling aggressively.
Stop immediate retries, use the documented reset metadata, and coordinate all callers sharing the Service Account's rate budget. Reduce duplicate work through caching and request coalescing before increasing concurrency.
Check the public Status Page, apply documented retry policy, and retain X-Request-ID.
Apply one workflow deadline and a capped attempt count. The Status Page supplies context but does not decide whether your particular request is safe to retry.
Provide request ID, UTC timestamp, operation, and HTTP status. Remove credentials, request bodies, and personal data.
If possible, include your safe application release identifier, attempt count, and whether the behavior is reproducible with synthetic input. Read Support before sending evidence.