Loading documentation…
Loading documentation…
Correlate client failures with SteamCall support evidence.
Capture the X-Request-ID response header with operation, timestamp, status, and duration. Include that identifier in support requests.
Request IDs are diagnostic metadata. They do not replace authentication and should not contain customer-provided secrets.
Clients may send X-Request-ID for correlation, and SteamCall returns the effective ID. Generate opaque values that carry no email address, Steam ID, API key, or other user data.
A useful diagnostic record contains the request ID, API operation, UTC timestamp, HTTP status, duration, attempt number, and safe application release identifier. Avoid full headers and bodies by default.
For a retry sequence, keep the evidence for each HTTP attempt and a separate workflow identifier in your own system. Do not assume a request ID proves that a timed-out operation had no effect.
Send the smallest relevant evidence when contacting Support. Never include credentials, Steam login material, or unnecessary inventory data.