Retrieve Fragment

Retrieve metadata for a fragment.

GET/transactions/{transactionId}/fragments/{fragmentIndex}

This endpoint retrieves metadata about a specific fragment within a transaction. To retrieve the fragment itself, use the Retrieve Fragment Output endpoint.

Fragments allow you to split large transactions into smaller chunks for easier processing. You can enable fragments for one repeated EDI segment in each transaction set and then split the transaction into chunks based on that segment.

Authorization
RequiredHeader

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. You can also retrieve it manually from the transaction's details page within the Stedi portal.

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 portal.

Response

application/json

GetTransactionFragment 200 response

transactionId
StringRequired

A unique identifier for the processed transaction containing this fragment. This ID is included in the transaction processed event. You can also retrieve it manually from the transaction's details page within the Stedi portal.

fileExecutionId
StringRequired

A unique identifier for the processed file containing this fragment. This ID is included in the file processed event. You can also retrieve it manually from the file's details page in the Stedi portal.

direction
StringRequired

The direction of the transaction. Inbound transactions are those you receive from a payer, provider, or other trading partner. Outbound transactions are those you send to a payer, provider, or other trading partner.

Possible values
INBOUND
OUTBOUND
UNKNOWN
mode
StringRequired

Indicates whether the transaction contains test or production data. Stedi determines this from the value in ISA15 Usage Indicator Code.

Possible values
test
production
other
processedAt
StringRequiredFormat: date-time

The date and time when Stedi processed the transaction containing the fragment, in ISO 8601 format. For example, 2023-08-28T00:00:00Z.

fragmentIndex
NumberRequired

The identifier for the fragment within a processed transaction.

fragments
ObjectRequired

Details about fragments included in the transaction, if applicable. Fragments break large transactions into smaller parts for easier processing and management.

Show attributes
keyName
fragments.keyName
StringRequired

The JSON schema key name for the segment in the Stedi guide used to split the transaction into fragments. For example, in an 834 Health Care Benefit Enrollment and Maintenance, this would be member_level_detail_INS_loop.

fragmentCount
fragments.fragmentCount
NumberRequired

The total number of fragments in the transaction.

batchSize
fragments.batchSize
NumberRequired

The maximum size of each fragment in kilobytes (KB). Stedi uses this to automatically split large inbound transactions into fragments.

transactionUrl
StringRequired

The URL to review the transaction within the Stedi portal.

artifacts
Array of ObjectsRequired

A list of artifacts related to the transaction containing the fragment.

Array item
artifactType
artifacts[].artifactType
StringRequired

The format of the artifact.

Possible values
text/csv
application/edifact
application/filepart
application/json
application/pdf
usage
artifacts[].usage
StringRequired

The type of data the artifact contains. For example, an input artifact represents the original data Stedi received before processing, while an output artifact represents the processed data.

For example, for an inbound 835 ERA from a payer, the input artifact would be the original X12 EDI, and the output artifact would be the JSON representation of the ERA.

Possible values
attachment
input
metadata
output
sizeBytes
artifacts[].sizeBytes
NumberRequired

The size of the artifact in bytes.

url
artifacts[].url
StringRequired

A URL to download the artifact.

model
artifacts[].model
StringRequired

The model of the artifact, which indicates the type of process or operation it represents. For example, an execution artifact represents a file that was processed, a fragment artifact represents a part of a larger transaction, and a fault artifact represents an error that occurred during processing.

Possible values
execution
fragment
transaction
fault
partnership
ObjectRequired

Information about the associated partnership.

A partnership describes all aspects of the EDI relationship between two profiles in your Stedi account, such as which transaction sets they will exchange and other important information for processing EDI files. If you're sending or receiving transactions through the Stedi clearinghouse, Stedi configures the necessary partnership for you automatically when you set up your account.

Show attributes
partnershipId
partnership.partnershipId
StringRequiredRegex pattern: ^([a-zA-Z0-9._-]+)$Length: 1 - 81

The unique identifier for the partnership within the Stedi platform.

A partnership describes all aspects of the EDI relationship between two profiles in your Stedi account, such as which transaction sets they will exchange and other important information for processing EDI files. If you're sending or receiving transactions through the Stedi clearinghouse, Stedi configures the necessary partnerships for you automatically when you set up your account.

partnershipType
partnership.partnershipType
StringRequired

The type of partnership, which determines the EDI standard used for exchanging transactions.

Possible values
x12
edifact
sender
partnership.sender
ObjectRequired

The entity that initiated the transaction.

Show attributes
profileId
partnership.sender.profileId
StringRequiredRegex pattern: ^([a-zA-Z0-9._-]+)$Length: 1 - 40

A unique identifier for the profile within the Stedi platform.

receiver
partnership.receiver
ObjectRequired

The entity that is receiving the transaction.

Show attributes
profileId
partnership.receiver.profileId
StringRequiredRegex pattern: ^([a-zA-Z0-9._-]+)$Length: 1 - 40

A unique identifier for the profile within the Stedi platform.

x12
Object

Details about the X12 EDI transaction.

Show attributes
metadata
x12.metadata
ObjectRequired

Metadata about the X12 EDI transaction, including information from the interchange, functional group, and transaction headers as well as the sender and receiver IDs.

Show attributes
interchange
x12.metadata.interchange
ObjectRequired

Data from the Interchange Control Header of the X12 EDI file.

Show attributes
acknowledgmentRequestedCode
x12.metadata.interchange.acknowledgmentRequestedCode
StringRequired

The value of ISA14 in the Interchange Control Header, which indicates whether the sender is requesting a TA1 Interchange Acknowledgment.

controlNumber
x12.metadata.interchange.controlNumber
NumberRequiredRange: ≥ 0 and ≤ 999999999

The control number in the Interchange Control Header.

functionalGroup
x12.metadata.functionalGroup
ObjectRequired

Data from the Functional Group Header of the X12 EDI file.

Show attributes
controlNumber
x12.metadata.functionalGroup.controlNumber
NumberRequiredRange: ≥ 0 and ≤ 999999999

The Group Control Number (GS06).

date
x12.metadata.functionalGroup.date
StringRequired

The date in the Functional Group Header (GS04), formatted as YYYY-MM-DD. For example, 2023-08-28.

functionalIdentifierCode
x12.metadata.functionalGroup.functionalIdentifierCode
StringRequired

The Functional Identifier Code (GS01), which indicates the type of transaction. For example, HC for an 837 Healthcare Claim.

time
x12.metadata.functionalGroup.time
StringRequired

The Time (GS05), formatted as HH:MM:SS. For example, 21:29:57.

release
x12.metadata.functionalGroup.release
StringRequired

The Version/Release/Industry Identifier Code (GS08), which indicates the version of the X12 standard used. For example, 005010X222A1.

transaction
x12.metadata.transaction
ObjectRequired

Data from the Transaction Set Header of the X12 EDI file.

Show attributes
controlNumber
x12.metadata.transaction.controlNumber
StringRequired

The Transaction Set Control Number (ST02).

transactionSetIdentifier
x12.metadata.transaction.transactionSetIdentifier
StringRequired

The Transaction Set Identifier Code (ST01), which indicates the type of transaction. For example, 837 for an 837 Healthcare Claim.

sender
x12.metadata.sender
ObjectRequired

The Application Code and ISA ID for the profile.

Show attributes
applicationCode
x12.metadata.sender.applicationCode
StringRequired

The Application Code for the profile, which is used to identify the entity in the GS header of an EDI file.

isa
x12.metadata.sender.isa
ObjectRequired

The Interchange ID and qualifier.

Show attributes
qualifier
x12.metadata.sender.isa.qualifier
StringRequired

The Interchange Sender ID Qualifier, which indicates the type of identifier. For example, ZZ for a mutually defined identifier.

id
x12.metadata.sender.isa.id
StringRequired

The Interchange ID, which is the unique identifier for the entity in the EDI file.

receiver
x12.metadata.receiver
ObjectRequired

The Application Code and ISA ID for the profile.

Show attributes
applicationCode
x12.metadata.receiver.applicationCode
StringRequired

The Application Code for the profile, which is used to identify the entity in the GS header of an EDI file.

isa
x12.metadata.receiver.isa
ObjectRequired

The Interchange ID and qualifier.

Show attributes
qualifier
x12.metadata.receiver.isa.qualifier
StringRequired

The Interchange Sender ID Qualifier, which indicates the type of identifier. For example, ZZ for a mutually defined identifier.

id
x12.metadata.receiver.isa.id
StringRequired

The Interchange ID, which is the unique identifier for the entity in the EDI file.

transactionSetting
x12.transactionSetting
Object

The IDs for the guide and transaction setting Stedi used to process the transaction.

Show attributes
guideId
x12.transactionSetting.guideId
String

The unique identifier for the Stedi guide used to process the transaction.

Stedi guides are machine-readable specifications for X12 EDI transactions. They describe how to structure and validate EDI files for each transaction type.

transactionSettingId
x12.transactionSetting.transactionSettingId
String

The unique identifier for the transaction setting Stedi used to process the transaction.

Transaction settings configure how Stedi processes specific transaction types, such as which Stedi guide to use and other processing options. If you're using the Stedi clearinghouse, Stedi automatically configures the required transaction settings for you when you set up your account.