GET
/
transactions
/
{transactionId}
/
fragments
/
{fragmentIndex}
/
output
curl --request GET \
  --url https://core.us.stedi.com/2023-08-01/transactions/{transactionId}/fragments/{fragmentIndex}/output \
  --header 'Authorization: <api-key>'
{
  "documentDownloadUrl": "https://core.us.stedi.com/2023-08-01/transactions/7d0c6f84-4cec-4f4a..."
}

There are no size restrictions on documents when fetching from this endpoint. However, fragments are generally smaller and more consumable than entire transactions.

​
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 fragment data.

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.

​
Example

The following example shows a fragment from an 846 Inventory Inquiry/Advice transaction. It contains two iterations of the item_identification_LIN loop.

Authorizations

​
Authorization
string
header
required

A Stedi API Key for authentication.

Path Parameters

​
transactionId
string
required

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.

​
fragmentIndex
number
required

The identifier for a specific fragment within a processed transaction. This ID is included in the fragment processed event, or you can retrieve it manually from the transaction's details page within the Stedi app.

Response

302
application/json
GetTransactionFragmentOutputDocument 302 response

The response is of type object.