# Stedi ## Docs - [Accounts and billing](https://stedi.com/docs/accounts-and-billing/index) - [Get Execution](https://stedi.com/docs/api-reference/edi-platform/core/get-executions): Retrieve the file execution details for a given executionId. - [Get Execution Input](https://stedi.com/docs/api-reference/edi-platform/core/get-executions-input): This endpoint retrieves an execution's input document before it passes through any translation and mappings. - [Get Execution Metadata](https://stedi.com/docs/api-reference/edi-platform/core/get-executions-metadata): This endpoint retrieves an execution's metadata document. - [Get Execution Output](https://stedi.com/docs/api-reference/edi-platform/core/get-executions-output): This endpoint retrieves an execution's output document. - [Get Execution Transactions](https://stedi.com/docs/api-reference/edi-platform/core/get-executions-transactions): Fetch a list of transactions for a given file execution, sorted by the date they were created from newest to oldest. Includes the full transaction details. - [List Executions](https://stedi.com/docs/api-reference/edi-platform/core/get-list-executions): Fetch a list of executions, sorted by the date they were created from newest to oldest. - [List Transactions](https://stedi.com/docs/api-reference/edi-platform/core/get-list-transactions): Fetch a list of transactions, sorted by the date they were created from newest to oldest. Generally this endpoint is used to display a list of transactions in a UI. If you are looking to regularly fetch and check for new transactions for programmatic usage, you should use the `ListPollingTransactions` operation instead. - [Poll Executions](https://stedi.com/docs/api-reference/edi-platform/core/get-pollingexecutions): This endpoint is used to regularly poll for new executions that have been processed by Stedi. You must define one of `startDateTime` or `pageToken` when making a request. You may optionally define a `pageSize`. The minimum `pageSize` is 1, and the maximum `pageSize` is 1000. The default is 100. `startDateTime` takes a string in ISO 8601 format. (ex: `2023-08-10T18:00:00Z`). `startDateTime` must be set to at least 1 minute in the past. The results will contain executions that occurred after this `startDateTime`. Starting from the oldest to newest executions ordered by the `processedAt` field. Note, this is _exclusive_ of the `startDateTime`, a execution occuring at exactly `2023-08-10T18:00:00Z` for instance, would not be included. In addition, there is a 15 second window where newly created executions will not be included to account for any network latency or clock drifts within the systems to ensure you do not miss any executions. Each request will _always_ return a `nextPageToken`, regardless of whether there are new executions or not. We DO NOT recommend trying to roll your own polling strategy leveraging `startDateTime` only. There are edge cases around two executions occuring at the _exact_ same time and being on the edge of a pagination which could cause you to miss one due to the exclusive nature of `startDateTime`. We recommend using `pageToken`'s instead. When making subsequent polling requests (not initiating with `startDateTime`), the `pageToken` can be used to continue iterating through pages of executions. Usage of the `pageToken` guaruntees you will not miss any executions on the stream. If at any point there are no more new executions in the `item` array, you will still receive a `nextPageToken`. Continue to use this token to poll for new executions. Once there are new executions, they will be returned in the `item` array. `pageToken`'s you have retrieved can serve as checkpoints. They do not expire, and you can always start from that point in the execution stream again if you need to catch a system up or recover from a failure. Storing `pageToken`'s as part of your polling process is encouraged. `pageToken`'s are unique per request, opaque, and should not be parsed or modified in any way. They are not guaranteed to be in any particular format, and may change in the future. - [Poll transactions](https://stedi.com/docs/api-reference/edi-platform/core/get-pollingtransactions): This endpoint is used to regularly poll for new transactions that have been processed in Core. You must define one of `startDateTime` or `pageToken` when making a request. You may optionally define a `pageSize`. The minimum `pageSize` is 1, and the maximum `pageSize` is 1000. The default is 100. `startDateTime` takes a string in ISO 8601 format. (ex: `2023-08-10T18:00:00Z`). `startDateTime` must be set to at least 1 minute in the past. The results will contain transactions that occurred after this `startDateTime`. Starting from the oldest to newest transactions ordered by the `processedAt` field. Note, this is _exclusive_ of the `startDateTime`, a transaction occuring at exactly `2023-08-10T18:00:00Z` for instance, would not be included. In addition, there is a 15 second window where newly created transactions will not be included to account for any network latency or clock drifts within the systems to ensure you do not miss any transactions. Each request will _always_ return a `nextPageToken`, regardless of whether there are new transactions or not. We DO NOT recommend trying to roll your own polling strategy leveraging `startDateTime` only. There are edge cases around two transactions occuring at the _exact_ same time and being on the edge of a pagination which could cause you to miss one due to the exclusive nature of `startDateTime`. We recommend using `pageToken`'s instead. When making subsequent polling requests (not initiating with `startDateTime`), the `pageToken` can be used to continue iterating through pages of transactions. Usage of the `pageToken` guaruntees you will not miss any transactions on the stream. If at any point there are no more new transactions in the `item` array, you will still receive a `nextPageToken`. Continue to use this token to poll for new transactions. Once there are new transactions, they will be returned in the `item` array. `pageToken`'s you have retrieved can serve as checkpoints. They do not expire, and you can always start from that point in the transaction stream again if you need to catch a system up or recover from a failure. Storing `pageToken`'s as part of your polling process is encouraged. `pageToken`'s are unique per request, opaque, and should not be parsed or modified in any way. They are not guaranteed to be in any particular format, and may change in the future. - [Get Fragment](https://stedi.com/docs/api-reference/edi-platform/core/get-transaction-fragment-detail): This endpoint fetches a fragment by its index for a given transaction. - [Get Fragment Output](https://stedi.com/docs/api-reference/edi-platform/core/get-transaction-fragment-output): This endpoint retrieves a transaction fragment's output document after it has been translated. - [Get Transaction](https://stedi.com/docs/api-reference/edi-platform/core/get-transactions): Fetch a single transaction by its ID. - [Get Transaction Input](https://stedi.com/docs/api-reference/edi-platform/core/get-transactions-input): This endpoint retrieves a transaction's input document before it passes through any translation and mappings. - [Get Transaction Output](https://stedi.com/docs/api-reference/edi-platform/core/get-transactions-output): This endpoint retrieves a transaction's output document after it has been translated. - [Stage fragment](https://stedi.com/docs/api-reference/edi-platform/core/post-fragments): This endpoint stages a fragment for outbound delivery. - [Stage transactions](https://stedi.com/docs/api-reference/edi-platform/core/stage-transactions): This endpoint stages a transaction for outbound delivery. - [Map Transaction Output](https://stedi.com/docs/api-reference/edi-platform/get-map-transaction-output): Retrieve a mapped transaction's output document - [Retry events](https://stedi.com/docs/api-reference/edi-platform/post-events-retry): This endpoint retriggers the specified processing event. - [Create Outbound Interchange](https://stedi.com/docs/api-reference/edi-platform/post-generate-edi): This endpoint generates and delivers fully-formed EDI files to your trading partners. - [Invoke Mapping](https://stedi.com/docs/api-reference/edi-platform/post-invoke-mapping): Maps the provided JSON to a different shape according to the specified mapping definition. - [Deliver Transaction Group](https://stedi.com/docs/api-reference/edi-platform/post-transaction-group): This endpoint generates and delivers a fully-formed EDI file containing the staged transactions in the specified transaction group. - [Create Outbound Transaction](https://stedi.com/docs/api-reference/edi-platform/post-transactions): This endpoint generates and delivers fully-formed EDI files containing a single transaction. It is the simplest way to generate EDI with Stedi. - [277CA Report](https://stedi.com/docs/api-reference/healthcare/get-healthcare-reports-277) - [835 ERA Report](https://stedi.com/docs/api-reference/healthcare/get-healthcare-reports-835) - [List Payers](https://stedi.com/docs/api-reference/healthcare/get-payers) - [CMS-1500 Claim Form PDF](https://stedi.com/docs/api-reference/healthcare/get-pdf-1500) - [Eligibility mock requests](https://stedi.com/docs/api-reference/healthcare/mock-requests-eligibility-checks) - [Real-Time Claim Status](https://stedi.com/docs/api-reference/healthcare/post-healthcare-claim-status) - [Real-Time Claim Status Raw X12](https://stedi.com/docs/api-reference/healthcare/post-healthcare-claim-status-raw-x12) - [Professional Claims](https://stedi.com/docs/api-reference/healthcare/post-healthcare-claims) - [Professional Claims Raw X12](https://stedi.com/docs/api-reference/healthcare/post-healthcare-claims-raw-x12) - [Real-Time Eligibility Check](https://stedi.com/docs/api-reference/healthcare/post-healthcare-eligibility) - [Real-Time Eligibility Check Raw X12](https://stedi.com/docs/api-reference/healthcare/post-healthcare-eligibility-raw-x12) - [Institutional Claims](https://stedi.com/docs/api-reference/healthcare/post-healthcare-institutional-claims) - [API Reference](https://stedi.com/docs/api-reference/index) - [Configure destinations](https://stedi.com/docs/edi-platform/configure/destinations/configure-destinations) - [Destinations error handling and limitations](https://stedi.com/docs/edi-platform/configure/destinations/error-handling-destinations) - [Destinations overview](https://stedi.com/docs/edi-platform/configure/destinations/index) - [EDI settings](https://stedi.com/docs/edi-platform/configure/global-settings) - [Configuration overview](https://stedi.com/docs/edi-platform/configure/index) - [Message Disposition Notifications (MDNs)](https://stedi.com/docs/edi-platform/configure/trading-partners/connections/as2/as2-mdn-response) - [AS2 Connections](https://stedi.com/docs/edi-platform/configure/trading-partners/connections/as2/as2-overview) - [AS2 requirements](https://stedi.com/docs/edi-platform/configure/trading-partners/connections/as2/as2-requirements) - [Configure AS2 connections](https://stedi.com/docs/edi-platform/configure/trading-partners/connections/as2/configure-as2) - [Bucket Connections](https://stedi.com/docs/edi-platform/configure/trading-partners/connections/buckets) - [Choosing a connection type](https://stedi.com/docs/edi-platform/configure/trading-partners/connections/choosing-the-right-connection-type) - [Connections overview](https://stedi.com/docs/edi-platform/configure/trading-partners/connections/index) - [Remote SFTP/FTPS Connections](https://stedi.com/docs/edi-platform/configure/trading-partners/connections/remote-ftp) - [Stedi SFTP/FTPS Connections](https://stedi.com/docs/edi-platform/configure/trading-partners/connections/stedi-ftp) - [Acknowledgments](https://stedi.com/docs/edi-platform/configure/trading-partners/functional-acknowledgments) - [Partnerships](https://stedi.com/docs/edi-platform/configure/trading-partners/profiles-and-partnerships) - [Transaction settings](https://stedi.com/docs/edi-platform/configure/trading-partners/transaction-settings) - [Configure webhooks](https://stedi.com/docs/edi-platform/configure/webhooks/configure-webhooks) - [Webhooks error handling and limitations](https://stedi.com/docs/edi-platform/configure/webhooks/error-handling-webhooks) - [Webhooks overview](https://stedi.com/docs/edi-platform/configure/webhooks/index) - [Glossary](https://stedi.com/docs/edi-platform/edi-essentials/glossary) - [What is EDI?](https://stedi.com/docs/edi-platform/edi-essentials/what-is-edi) - [Element data types in X12 EDI](https://stedi.com/docs/edi-platform/edi-essentials/x12/elements/element-data-types-in-x12-edi) - [Element Requirements in X12 EDI](https://stedi.com/docs/edi-platform/edi-essentials/x12/elements/element-requirements-in-x12-edi) - [Relational conditions in X12 EDI](https://stedi.com/docs/edi-platform/edi-essentials/x12/elements/relational-conditions-in-x12-edi) - [What is an element in X12 EDI?](https://stedi.com/docs/edi-platform/edi-essentials/x12/elements/what-is-an-element) - [X12 HIPAA](https://stedi.com/docs/edi-platform/edi-essentials/x12/hipaa/index) - [Segment repetition in X12 EDI"](https://stedi.com/docs/edi-platform/edi-essentials/x12/segments/segment-repetition-in-x12-edi) - [Segment requirements in X12 EDI](https://stedi.com/docs/edi-platform/edi-essentials/x12/segments/segment-requirements-in-x12-edi) - [What is a segment in X12 EDI?](https://stedi.com/docs/edi-platform/edi-essentials/x12/segments/what-is-a-segment) - [Split inbound EDI files with fragments](https://stedi.com/docs/edi-platform/fragments/inbound-fragments) - [Fragments: Split transactions into smaller chunks](https://stedi.com/docs/edi-platform/fragments/index) - [Generate outbound EDI files with fragments](https://stedi.com/docs/edi-platform/fragments/outbound-fragments) - [Integration steps](https://stedi.com/docs/edi-platform/getting-started/first-integration) - [Gather requirements](https://stedi.com/docs/edi-platform/getting-started/gather-requirements) - [EDI platform overview](https://stedi.com/docs/edi-platform/getting-started/index) - [Advanced: Build Stedi guides](https://stedi.com/docs/edi-platform/guides/customize-guides) - [Import Stedi Guides](https://stedi.com/docs/edi-platform/guides/import-guides) - [Guides overview](https://stedi.com/docs/edi-platform/guides/index) - [Public Guides](https://stedi.com/docs/edi-platform/guides/public-guides) - [What is an EDI guide?](https://stedi.com/docs/edi-platform/guides/what-is-a-stedi-guide) - [Mappings - Transform JSON](https://stedi.com/docs/edi-platform/mappings/index) - [Common Mapping Expressions](https://stedi.com/docs/edi-platform/mappings/jsonata/common-mapping-expressions) - [JSONata Cheatsheet](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-cheatsheet) - [Aggregation functions](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-functions/aggregation) - [Array functions](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-functions/array) - [Boolean functions](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-functions/boolean) - [Date/time functions](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-functions/date-time) - [Higher order functions](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-functions/higher-order) - [JSONata Functions](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-functions/index) - [Numeric functions](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-functions/numeric) - [Object functions](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-functions/object) - [Other functions](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-functions/other) - [String functions](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-functions/string) - [Boolean Operators](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-operators/boolean) - [Comparison Operators](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-operators/comparison) - [JSONata Operators](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-operators/index) - [Numeric Operators](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-operators/numeric) - [Other Operators](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-operators/other) - [Path Operators](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-operators/path) - [JSONata Playground](https://stedi.com/docs/edi-platform/mappings/jsonata/jsonata-playground) - [Mappings limits](https://stedi.com/docs/edi-platform/mappings/limits) - [Manage mapping definitions with the API](https://stedi.com/docs/edi-platform/mappings/manage-mappings/api-guide) - [Mapping Definition Overview](https://stedi.com/docs/edi-platform/mappings/manage-mappings/mapping-definition) - [Mappings UI Builder](https://stedi.com/docs/edi-platform/mappings/manage-mappings/ui-guide) - [Invoke mappings](https://stedi.com/docs/edi-platform/mappings/transform-json-documents) - [Events types and structure](https://stedi.com/docs/edi-platform/operate/event-types) - [Failures and retries](https://stedi.com/docs/edi-platform/operate/failures-and-retries) - [File processing overview](https://stedi.com/docs/edi-platform/operate/file-processing-overview) - [Customize the ISA and GS headers](https://stedi.com/docs/edi-platform/operate/generate-edi/envelope-overrides) - [Create outbound transaction](https://stedi.com/docs/edi-platform/operate/generate-edi/index) - [Generate test files in your browser](https://stedi.com/docs/edi-platform/operate/generate-test-files) - [Parse EDI](https://stedi.com/docs/edi-platform/operate/parse-edi) - [Monitor transactions](https://stedi.com/docs/edi-platform/operate/transaction-data) - [Guide JSON format](https://stedi.com/docs/edi-platform/operate/transform-json/guide-json) - [Choose a transformation approach](https://stedi.com/docs/edi-platform/operate/transform-json/transformation-approaches) - [Overview - Transform Guide JSON](https://stedi.com/docs/edi-platform/operate/transform-json/transforming-data) - [Payer benefit response](https://stedi.com/docs/healthcare/benefit-response) - [Check claim status](https://stedi.com/docs/healthcare/check-claim-status) - [Claims code lists](https://stedi.com/docs/healthcare/claims-code-lists) - [Configure webhooks for claim responses](https://stedi.com/docs/healthcare/configure-webhooks) - [Eligibility Manager](https://stedi.com/docs/healthcare/eligibility-manager) - [Eligibility troubleshooting](https://stedi.com/docs/healthcare/eligibility-troubleshooting) - [Enhanced claim validation](https://stedi.com/docs/healthcare/enhanced-claim-validation) - [Stedi Healthcare](https://stedi.com/docs/healthcare/index): Automate transactions with the only API-first clearinghouse - [Overview](https://stedi.com/docs/healthcare/intro-eligibility-checks) - [Overview](https://stedi.com/docs/healthcare/intro-to-claims-processing) - [Monthly refresh checks](https://stedi.com/docs/healthcare/monthly-refresh-eligibility-checks) - [Retrieve 277 and ERA responses](https://stedi.com/docs/healthcare/receive-claim-responses) - [Eligibility checks](https://stedi.com/docs/healthcare/send-eligibility-checks) - [Submit institutional claims](https://stedi.com/docs/healthcare/submit-institutional-claims) - [Submit professional claims](https://stedi.com/docs/healthcare/submit-professional-claims) - [Supported payers](https://stedi.com/docs/healthcare/supported-payers) - [Acceptable Use Policy](https://stedi.com/docs/legal/acceptable-use-policy) - [Cookie Notice](https://stedi.com/docs/legal/cookie-notice) - [Customer Agreement](https://stedi.com/docs/legal/customer-agreement) - [Privacy Notice](https://stedi.com/docs/legal/privacy-notice) - [Service Terms](https://stedi.com/docs/legal/service-terms) - [Site Terms](https://stedi.com/docs/legal/site-terms) - [Core Service Level Agreement](https://stedi.com/docs/legal/slas/core) - [Healthcare APIs](https://stedi.com/docs/legal/slas/healthcare) - [Data and privacy](https://stedi.com/docs/security-and-compliance/data-privacy) - [HIPAA compliance on Stedi](https://stedi.com/docs/security-and-compliance/hipaa) - [Support](https://stedi.com/docs/support/index) ## Optional - [Changelog](https://www.stedi.com/changelog)