Get Transaction Input
This endpoint retrieves a transaction’s input document before it passes through any translation and mappings.
This endpoint retrieves a transaction’s input document before it passes through any translation or mappings.
The input document can be in either X12 EDI or JSON format, depending on the direction of the transaction. For example:
- If you send an 834 Benefit Enrollment to a payer, the input document will be in the JSON format you submitted to Stedi’s API.
- If a payer sends you an 835 ERA, the input document will be in the original X12 EDI format.
There are no size restrictions on documents when fetching from this endpoint.
Response
This endpoint returns a 302
Temporary redirect to the document download URL. Many HTTP clients will automatically follow this redirect, or have a simple follow redirects configuration to set. For example, using the -L
or --location
flag in cURL will automatically follow the redirect. In this case, the response will contain the full transaction input document.
In the event you cannot, or chose not to automatically follow the redirect, the body of the response contains a JSON object with a single key documentDownloadUrl
which contains a temporary URL to download the document. This URL is available for 60 minutes.
Authorizations
A Stedi API Key for authentication.
Path Parameters
A unique identifier for the processed transaction within Stedi. This ID is included in the transaction processed event, or you can retrieve it manually from the transaction's details page within the Stedi app.
Response
A URL to download the document. This URL is available for 60 minutes.