---
title: "GET /executions/{executionId}/transactions"
method: GET
path: "/executions/{executionId}/transactions"
---

# GET /executions/{executionId}/transactions

`GET /executions/{executionId}/transactions`

Fetch a list of transactions for a file execution, including the full transaction details.

## Path parameters

- `executionId` string, required — A unique identifier for the file execution within Stedi. This ID is included in the file processed event, or you can retrieve it manually from the file's details page within the Stedi portal.

## Query parameters

- `pageSize` number — 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.
- `pageToken` string — A token returned by a previous call to this operation in the `nextPageToken`. If not specified, Stedi returns the first page of results.

## Response `200`

ListExecutionTransactions 200 response

- ListExecutionTransactionsResponseContent — Common output structure for list operations with pagination support.
  - `nextPageToken` string — Token that you can supply in subsequent requests to retrieve the next page of results. If not returned, there are no more results.
  - `items` TransactionSummary[], required
    - `transactionId` string, required — 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.
    - `fileExecutionId` string, required — 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.
    - `status` 'failed' | 'succeeded', required — A status indicating whether Stedi was able to successfully process the transaction.
    - `direction` 'INBOUND' | 'OUTBOUND' | 'UNKNOWN', required — 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.
    - `mode` 'test' | 'production' | 'other', required — Indicates whether the transaction contains test or production data. Stedi determines this from the value in [`ISA15` Usage Indicator Code](https://www.stedi.com/edi/x12/segment/ISA#ISA-15).
    - `processedAt` string, date-time, required — The date and time when Stedi processed the transaction, in ISO 8601 format. For example, `2023-08-28T00:00:00Z`.
    - `artifacts` Artifact[], required — A list of artifacts related to the transaction.
      - `artifactType` 'text/csv' | 'application/edifact' | 'application/filepart' | 'application/json' | 'application/pdf' | 'text/psv' | 'text/tsv' | 'application/edi-x12' | 'application/xml' | 'application/zip' | 'image/jpeg' | 'image/png' | 'image/tiff' | 'text/plain' | 'unknown', required — The format of the artifact.
      - `usage` 'attachment' | 'input' | 'metadata' | 'output', required — 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.
      - `sizeBytes` number, required — The size of the artifact in bytes.
      - `url` string, required — A URL to download the artifact.
      - `model` 'execution' | 'fragment' | 'transaction' | 'fault', required — 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.
    - `partnership` Partnership, required — 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.
      - `partnershipId` string, required — 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` 'x12' | 'edifact', required — The type of partnership, which determines the EDI standard used for exchanging transactions.
      - `sender` PartnershipSender, required — The entity that initiated the transaction.
        - `profileId` string, required — A unique identifier for the profile within the Stedi platform.
      - `receiver` PartnershipReceiver, required — The entity that is receiving the transaction.
        - `profileId` string, required — A unique identifier for the profile within the Stedi platform.
    - `x12` X12TransactionSummary — Details about the X12 EDI transaction.
      - `metadata` X12TransactionMetadata, required — Metadata about the X12 EDI transaction, including information from the interchange, functional group, and transaction headers as well as the sender and receiver IDs.
        - `interchange` X12TransactionMetadataInterchange, required — Data from the Interchange Control Header of the X12 EDI file.
          - `acknowledgmentRequestedCode` string, required — The value of [`ISA14`](https://www.stedi.com/edi/x12/segment/ISA#ISA-14) in the Interchange Control Header, which indicates whether the sender is requesting a [`TA1` Interchange Acknowledgment](https://www.stedi.com/edi/x12/segment/TA1).
          - `controlNumber` number, required — The control number in the Interchange Control Header.
        - `functionalGroup` X12TransactionMetadataFunctionalGroup, required — Data from the Functional Group Header of the X12 EDI file.
          - `controlNumber` number, required — The Group Control Number ([`GS06`](https://www.stedi.com/edi/x12/segment/GS#GS-06)).
          - `date` string, required — The date in the Functional Group Header ([`GS04`](https://www.stedi.com/edi/x12/segment/GS#GS-04)), formatted as `YYYY-MM-DD`. For example, `2023-08-28`.
          - `functionalIdentifierCode` string, required — The Functional Identifier Code ([`GS01`](https://www.stedi.com/edi/x12/segment/GS#GS-01)), which indicates the type of transaction. For example, `HC` for an 837 Healthcare Claim.
          - `time` string, required — The Time ([`GS05`](https://www.stedi.com/edi/x12/segment/GS#GS-05)), formatted as `HH:MM:SS`. For example, `21:29:57`.
          - `release` string, required — The Version/Release/Industry Identifier Code ([`GS08`](https://www.stedi.com/edi/x12/segment/GS#GS-08)), which indicates the version of the X12 standard used. For example, `005010X222A1`.
        - `transaction` X12TransactionMetadataTransaction, required — Data from the Transaction Set Header of the X12 EDI file.
          - `controlNumber` string, required — The Transaction Set Control Number ([`ST02`](https://www.stedi.com/edi/x12/segment/ST#ST-02)).
          - `transactionSetIdentifier` string, required — The Transaction Set Identifier Code ([`ST01`](https://www.stedi.com/edi/x12/segment/ST#ST-01)), which indicates the type of transaction. For example, `837` for an 837 Healthcare Claim.
        - `sender` X12TransactionMetadataProfile, required — The Application Code and ISA ID for the profile.
          - `applicationCode` string, required — The Application Code for the profile, which is used to identify the entity in the `GS` header of an EDI file.
          - `isa` X12TransactionMetadataProfileISA, required — The Interchange ID and qualifier.
            - `qualifier` string, required — The Interchange Sender ID Qualifier, which indicates the type of identifier. For example, `ZZ` for a mutually defined identifier.
            - `id` string, required — The Interchange ID, which is the unique identifier for the entity in the EDI file.
        - `receiver` X12TransactionMetadataProfile, required — The Application Code and ISA ID for the profile.
          - `applicationCode` string, required — The Application Code for the profile, which is used to identify the entity in the `GS` header of an EDI file.
          - `isa` X12TransactionMetadataProfileISA, required — The Interchange ID and qualifier.
            - `qualifier` string, required — The Interchange Sender ID Qualifier, which indicates the type of identifier. For example, `ZZ` for a mutually defined identifier.
            - `id` string, required — The Interchange ID, which is the unique identifier for the entity in the EDI file.
      - `transactionSetting` X12TransactionSetting — The IDs for the guide and transaction setting Stedi used to process the transaction.
        - `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` 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.
    - `fragments` TransactionFragmentsSummary — Details about fragments included in the transaction, if applicable. Fragments break large transactions into smaller parts for easier processing and management.
      - `keyName` string, required — 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` number, required — The total number of fragments in the transaction.
      - `batchSize` number, required — The maximum size of each fragment in kilobytes (KB). Stedi uses this to automatically split large inbound transactions into fragments.
    - `translationErrors` TranslationError[] — Details about errors that prevented Stedi from processing the transaction.
      - `context` TranslationErrorContext
        - `code` string — The error code.
        - `schemaPath` string — The name of the JSON property where the error occurred.
      - `mark` Mark — The location in the document where the problem occurred. May be a single index or a range.
        - `start` Index, required
          - `line` number, required — The line number in the document where the problem occurred.
          - `column` number, required — The column number in the document where the problem occurred.
        - `end` Index
          - `line` number, required — The line number in the document where the problem occurred.
          - `column` number, required — The column number in the document where the problem occurred.
      - `message` string, required — A message describing the error that occurred during translation.
    - `businessIdentifiers` BusinessIdentifier[] — Any business identifiers extracted from the transaction.
      - `elementId` string, required — The identifier of the element containing the business identifier in the EDI specification.
      - `element` string, required — The element where the business identifier was found. For example, `BHT03` for 837 claims.
      - `name` string, required — The friendly name of the business identifier. For example, `Originator Application Transaction Identifier`.
      - `value` string, required — The value of the business identifier.

## Other responses

- `400` — BadRequestException 400 response
- `401` — UnauthorizedException 401 response
- `403` — AccessDeniedException 403 response
- `404` — ResourceNotFoundException 404 response
- `409` — ResourceUnderChangeException 409 response
- `422` — UnprocessableEntityException 422 response
- `429` — ThrottlingException 429 response
- `500` — ServiceException 500 response
- `503` — ServiceUnavailableException 503 response
- `504` — GatewayTimeoutException 504 response

---

[API](https://skmtc.net/stedi/apis/core.md) · [All operations](https://skmtc.net/stedi/apis/core/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/stedi/core/versions/172bd33e0d66/schema)