Get Transaction Output
Stedi Core-compatible Retrieve Transaction Output — the translated JSON document Cair produced (Guide JSON).
An authenticated call returns a 302 Found whose Location header and documentDownloadUrl body point at a short-lived, presigned download URL. Follow that URL (with or without the Authorization header) to stream the artifact; the presigned URL is valid for 60 minutes and is bound to your organization, the transaction, and the output usage.
Overview
Downloads the transaction’s output document — the translated JSON (Guide JSON) Cair produced from the input. This is a 1:1 drop-in for Stedi’s Retrieve Transaction Output operation and the Stedi SDK’sgetTransactionOutput.
For 835 remits the output is the parsed claim payment JSON; for 837 claims it is the parsed claim JSON. The Content-Type of the downloaded artifact is application/json.
Authentication
The initial request is authenticated with your JWT Bearer token fromPOST /api/token, with the api-access feature.
The download request that follows the redirect is authenticated by the presigned token in the URL and does not require the Authorization header.
Path parameters
transactionId whose output artifact you want to download.Two-step download flow
Identical to the input endpoint:- Authenticated request. Call the endpoint with your Bearer token. Cair responds
302 Foundwith aLocationheader and a{ "documentDownloadUrl": "..." }body. - Follow the redirect. Fetch the presigned URL — with or without the
Authorizationheader — and Cair streams the JSON output artifact.
output usage.
302 automatically, so getTransactionOutput typically returns the artifact bytes in a single call.Example
Response
302 Found — body:
200 OK (after following the redirect) — the translated JSON artifact:
Errors
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Unique identifier of the processed transaction (the transactionId returned by the list/poll endpoints).
Response
Raw output artifact bytes, returned when the presigned URL is followed. Content-Type matches the artifact (typically application/json).
The response is of type object.

