List Transactions

Fetch a list of transactions, sorted by the date they were created from newest to oldest.

GET/transactions

This endpoint fetches a list of all the transactions Stedi has processed in your account. It's useful for displaying a list of transactions in a UI. If you want to programmatically fetch and check for new transactions, you should use the Poll Transactions endpoint instead.

Authorizationstringrequiredheader

A Stedi API Key for authentication.

Query Parameters

pageSizenumber

The maximum number of elements to return in a page. You can set this to a maximum of 500 elements. If not specified, the default is 100.

  • Range: ≥ 1 and ≤ 500
pageTokenstring

A token returned by a previous call to this operation in the nextPageToken. If not specified, Stedi returns the first page of results.

  • Required string length: 1 - 1024

List only transactions containing a business identifier with the given value.

Any valid 3-digit X12 Transaction Set Identifier Code, as defined in the X12 standard. See: https://www.stedi.com/edi/x12/element/143.

Possible values
100
101
102
103
104
senderstring

List only transactions sent by the given profile. This is the profile ID of the sender.

receiverstring

List only transactions sent to the given profile. This is the profile ID of the receiver.

directionstring

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
modestring

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
statusstring

A status indicating whether Stedi was able to successfully process the transaction.

Possible values
failed
succeeded
fromstring
  • Format: date-time
tostring
  • Format: date-time
elementIdstring

List only transactions containing a business identifier with the given element ID. This is the X12 element ID, such as "127" for Reference Identification. May only be supplied if businessIdentifier is also supplied. See Stedi's EDI references pages to find element IDs.

List only transactions that were sent or received on the given partnership. This is the partnership ID, such as "local_clearinghouse-test".

Response

application/json

ListTransactions 200 response

Token for pagination to retrieve the next page of results; null if there are no more results

  • Required string length: 1 - 1024
itemsarray<object>required

The processed transactions that match the request criteria. The items array is empty if there are no matching transactions.

Array item
items[].transactionIdstringrequired

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

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

items[].statusstringrequired

A status indicating whether Stedi was able to successfully process the transaction.

Possible values
failed
succeeded
items[].directionstringrequired

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
items[].modestringrequired

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
items[].processedAtstringrequired

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

  • Format: date-time
items[].artifactsarray<object>required

A list of artifacts related to the transaction.

Array item

The format of the artifact.

Possible values
text/csv
application/edifact
application/filepart
application/json
application/pdf

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

The size of the artifact in bytes.

A URL to download the artifact.

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
items[].partnershipobjectrequired

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.

Show attributes

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.

  • Pattern: ^([a-zA-Z0-9._-]+)$
  • Required string length: 1 - 81

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

Possible values
x12
edifact

The entity that initiated the transaction.

Show attributes

A unique identifier for the profile within the Stedi platform.

  • Pattern: ^([a-zA-Z0-9._-]+)$
  • Required string length: 1 - 40

The entity that is receiving the transaction.

Show attributes

A unique identifier for the profile within the Stedi platform.

  • Pattern: ^([a-zA-Z0-9._-]+)$
  • Required string length: 1 - 40

Details about the X12 EDI transaction.

Show attributes
items[].x12.metadataobjectrequired

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

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

Show attributes

The value of ISA14 in the Interchange Control Header, which indicates whether the sender is requesting an interchange acknowledgment.

The control number in the Interchange Control Header.

  • Range: ≥ 0 and ≤ 999999999

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

Show attributes

The Group Control Number (GS06).

  • Range: ≥ 0 and ≤ 999999999

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

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

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

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

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

Show attributes

The Transaction Set Control Number (ST02).

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

The Application Code and ISA ID for the profile.

Show attributes

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

The Interchange ID and qualifier.

Show attributes

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

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

The Application Code and ISA ID for the profile.

Show attributes

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

The Interchange ID and qualifier.

Show attributes

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

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

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

Show attributes

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.

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.

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

Show attributes

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.

The total number of fragments in the transaction.

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

Details about errors that prevented Stedi from processing the transaction.

Array item
Show attributes

The name of the JSON property where the error occurred.

The location in the document where the problem occurred. May be a single index or a range.

Show attributes
Show attributes

The line number in the document where the problem occurred.

The column number in the document where the problem occurred.

Show attributes

The line number in the document where the problem occurred.

The column number in the document where the problem occurred.

A message describing the error that occurred during translation.

Any business identifiers extracted from the transaction.

Array item

The identifier of the element containing the business identifier in the EDI specification.

The element where the business identifier was found. For example, BEG-03.

The friendly name of the business identifier. For example, Purchase Order Number.

The value of the business identifier.