---
title: "GET /executions"
method: GET
path: "/executions"
---

# GET /executions

`GET /executions`

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

## 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 — An opaque token returned by a previous call to this operation in the `nextPageToken`. If not specified, Stedi returns the first page of results.
- `direction` 'INBOUND' | 'OUTBOUND' | 'UNKNOWN' — 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.
- `faultCode` 'DELIVERY_FAILURE' | 'FAILED_TO_EXTRACT_BUSINESS_IDENTIFIERS' | 'FAILED_TO_FIND_GUIDE' | 'FAILED_TO_FIND_LOCAL_PROFILE' | 'FAILED_TO_FIND_PARTNER_PROFILE' | 'FAILED_TO_FIND_PARTNERSHIP' | 'FAILED_TO_FIND_PROFILES' | 'FAILED_TO_FIND_RECEIVER_PROFILE' | 'FAILED_TO_FIND_SENDER_PROFILE' | 'FAILED_TO_FIND_CONNECTION' | 'FAILED_TO_GENERATE_CONTROL_NUMBERS' | 'FAILED_TO_PARSE' | 'FAILED_TO_PARSE_METADATA' | 'FAILED_TO_TRANSLATE' | 'FAILED_TO_ACK' | 'FAILED_TO_ACK_INTERCHANGE' | 'FILE_NOT_FOUND' | 'INVALID_EVENT' | 'INVALID_CONFIGURATION' | 'MISMATCHED_PARTNERSHIP_CONNECTION' | 'MISSING_FUNCTIONAL_GROUP_CONTROL_NUMBER' | 'MISSING_FUNCTIONAL_GROUP_RELEASE' | 'MISSING_INTERCHANGE_CONTROL_NUMBER' | 'MISSING_TRANSACTION_SET_CONTROL_NUMBER' | 'MISSING_RECEIVER_ID' | 'MISSING_RECEIVER_QUALIFIER' | 'MISSING_SENDER_ID' | 'MISSING_SENDER_QUALIFIER' | 'MULTIPLE_MATCHING_GUIDES' | 'MULTIPLE_MATCHING_TRANSACTION_SETTINGS' | 'MULTIPLE_PARTNERSHIPS' | 'NO_TRANSLATION_OUTPUT' | 'NO_TRANSACTION_SETS' | 'NOT_SUPPORTED' | 'NO_FUNCTIONAL_GROUPS' | 'NO_USAGE_INDICATOR_CODE' | 'PREVIOUSLY_RETRIED' | 'TRANSLATION_ERROR' | 'UNKNOWN_ERROR' — A code specifying the reason for the fault. This code appears in the `code` property of the HTTP error response.
- `partnershipId` string — The unique identifier for the partnership within the Stedi platform. 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.
- `status` 'COMPLETED' | 'PARTIALLY_COMPLETED' | 'FAILED' | 'IGNORED' | 'IN_PROGRESS' | 'RETRYING' | 'RETRIED' | 'STARTED' — The status of the execution. - You can only retry executions with a `FAILED` or `IGNORED` status. - An execution is `COMPLETED` when Stedi has finished processing the file with no errors. If the file is an outbound file, a `COMPLETED` status also means that Stedi successfully delivered it to the configured connection.
- `mode` 'test' | 'production' | 'other' | 'unknown' — Indicates whether the file execution 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).
- `from` string, date-time — The start of the time range to filter file executions. The results will include executions created at or after this timestamp.
- `to` string, date-time — The end of the time range to filter file executions. The results will include executions up to and including this timestamp.
- `displayName` string — Filter executions by the source of the file, including the directory and file name. Supports partial matching against the full path.

## Response `200`

ListExecutions 200 response

- ListExecutionsResponseContent — 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` ExecutionSummary[], required
    - `createdAt` string, date-time, required — The date and time when the resource was created, in ISO 8601 format. For example, `2023-08-28T00:00:00Z`.
    - `updatedAt` string, date-time, required — The date and time when the resource was last updated, in ISO 8601 format. For example, `2023-08-28T00:00:00Z`.
    - `executionId` 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` 'COMPLETED' | 'PARTIALLY_COMPLETED' | 'FAILED' | 'IGNORED' | 'IN_PROGRESS' | 'RETRYING' | 'RETRIED' | 'STARTED', required — The status of the execution. - You can only retry executions with a `FAILED` or `IGNORED` status. - An execution is `COMPLETED` when Stedi has finished processing the file with no errors. If the file is an outbound file, a `COMPLETED` status also means that Stedi successfully delivered it to the configured connection.
    - `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.
    - `transactionCount` number — The number of individual transactions included in the file.
    - `faultCount` number — The number of errors that occurred during processing. If the file was successfully processed completely, this value is `0`.
    - `faultCode` 'DELIVERY_FAILURE' | 'FAILED_TO_EXTRACT_BUSINESS_IDENTIFIERS' | 'FAILED_TO_FIND_GUIDE' | 'FAILED_TO_FIND_LOCAL_PROFILE' | 'FAILED_TO_FIND_PARTNER_PROFILE' | 'FAILED_TO_FIND_PARTNERSHIP' | 'FAILED_TO_FIND_PROFILES' | 'FAILED_TO_FIND_RECEIVER_PROFILE' | 'FAILED_TO_FIND_SENDER_PROFILE' | 'FAILED_TO_FIND_CONNECTION' | 'FAILED_TO_GENERATE_CONTROL_NUMBERS' | 'FAILED_TO_PARSE' | 'FAILED_TO_PARSE_METADATA' | 'FAILED_TO_TRANSLATE' | 'FAILED_TO_ACK' | 'FAILED_TO_ACK_INTERCHANGE' | 'FILE_NOT_FOUND' | 'INVALID_EVENT' | 'INVALID_CONFIGURATION' | 'MISMATCHED_PARTNERSHIP_CONNECTION' | 'MISSING_FUNCTIONAL_GROUP_CONTROL_NUMBER' | 'MISSING_FUNCTIONAL_GROUP_RELEASE' | 'MISSING_INTERCHANGE_CONTROL_NUMBER' | 'MISSING_TRANSACTION_SET_CONTROL_NUMBER' | 'MISSING_RECEIVER_ID' | 'MISSING_RECEIVER_QUALIFIER' | 'MISSING_SENDER_ID' | 'MISSING_SENDER_QUALIFIER' | 'MULTIPLE_MATCHING_GUIDES' | 'MULTIPLE_MATCHING_TRANSACTION_SETTINGS' | 'MULTIPLE_PARTNERSHIPS' | 'NO_TRANSLATION_OUTPUT' | 'NO_TRANSACTION_SETS' | 'NOT_SUPPORTED' | 'NO_FUNCTIONAL_GROUPS' | 'NO_USAGE_INDICATOR_CODE' | 'PREVIOUSLY_RETRIED' | 'TRANSLATION_ERROR' | 'UNKNOWN_ERROR' — A code specifying the reason for the fault. This code appears in the `code` property of the HTTP error response.
    - `faultMessage` string — A message providing more information about the fault. Note that if there are multiple faults, Stedi sets the first fault as the code and corresponding message.
    - `fileType` 'CSV' | 'EDI/EDIFACT' | 'FILEPART' | 'JSON' | 'PSV' | 'JSON/STEDI-GUIDE' | 'TSV' | 'UNKNOWN' | 'EDI/X12' | 'XML' | 'ZIP' — The file format. For example, `EDI/EDIFACT` for an EDIFACT file or `EDI/X12` for an X12 EDI file.
    - `retryable` boolean — If `true`, you can retry the file in the Stedi portal.
    - `parentExecutionId` string — The ID of this execution's parent execution, if it is part of a retry chain. When you retry a file, Stedi creates a child execution with a new ID and links it to the original (parent) execution.
    - `childExecutionId` string — The ID of this execution's child execution, if it is part of a retry chain. When you retry a file, Stedi creates a child execution with a new ID and links it to the original (parent) execution.
    - `partnershipId` string — 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.
    - `connectionType` 'BUCKET' | 'AS2' | 'STEDI_FTP' | 'REMOTE_FTP' | 'STEDI_ACCOUNT_FTP' — The type of connection used for file delivery.
    - `connectionId` string — An autogenerated identifier for the connection within the Stedi platform.
    - `source` ExecutionSource — The source of the file, including the directory where Stedi received it and the file name.
      - `dirname` string, required — The directory where Stedi received the file for processing.
      - `name` string, required — The name of the file.
    - `mode` 'test' | 'production' | 'other' | 'unknown', required — Indicates whether the file execution 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).

## 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/revisions/172bd33e0d66/schema)