# Event destinations now support file processing events

> You can now subscribe to file processing events using event destinations, including events for successful files, failed files, and processed transactions.

Published Sep 11, 2026

Product: Accounts

You can now subscribe to [file processing events](https://www.stedi.com/docs/healthcare/event-destinations-event-types#file-processing-events) using [event destinations](https://www.stedi.com/docs/healthcare/event-destinations-configure):

- [`file.processed`](https://www.stedi.com/docs/healthcare/event-destinations-event-types#fileprocessed) – Stedi generates this event when it successfully processes a file, such as a [277CA claim acknowledgment](https://www.stedi.com/docs/healthcare/claim-responses-overview#277ca-claim-acknowledgment) from a payer.

- [`file.failed`](https://www.stedi.com/docs/healthcare/event-destinations-event-types#filefailed) – Stedi generates this event when it fails to process a file, such as an SFTP claim submission it can't parse.

- [`transaction.processed`](https://www.stedi.com/docs/healthcare/event-destinations-event-types#transactionprocessed) – Stedi generates this event when it translates a transaction, such as a payer's [Electronic Remittance Advice](https://www.stedi.com/docs/healthcare/claim-responses-overview#835-electronic-remittance-advice-era) (ERA) into JSON.

You can subscribe on the Stedi portal's [Event Destinations page](https://portal.stedi.com/app/settings/developer/event-destinations), with the [Event Destination APIs](https://www.stedi.com/docs/healthcare/event-destinations-configure#api), or with the [Stedi SDKs](https://www.stedi.com/docs/healthcare/sdks#event-destinations).

Selecting file processing events for an event destination in the Stedi portal

An installed [OAuth app](https://www.stedi.com/docs/healthcare/oauth-apps) can also subscribe to these events in its provider's account.

## Event payloads

Stedi events use a thin event schema. A thin event notifies you that a resource changed, but it doesn't include the resource's data.

A single file with multiple transactions produces one `file.processed` event and one `transaction.processed` event per transaction. The `relatedResources` array identifies the transaction type.

```json
{
  ...
  "resource": {
    "id": "019bb508-dc63-73a1-8ddc-9d4720299072",
    "type": "transaction"
  },
  "relatedResources": [
    {
      "id": "019bb508-dc63-73a1-8ddc-9d4720299072",
      "type": "transaction.x12.835" // ERA
    }
  ],
  "type": "transaction.processed"
}
```

Once you receive an event, retrieve the details using Stedi's APIs or the Stedi portal:

- `transaction.processed` – Pass the transaction ID in `relatedResources` to the [Get 835 ERA Report](https://www.stedi.com/docs/healthcare/api-reference/get-healthcare-reports-835) or [Get 277CA Report](https://www.stedi.com/docs/healthcare/api-reference/get-healthcare-reports-277) endpoint.

- `file.processed` and `file.failed` – Pass the execution ID in `resource.id` to the [Retrieve File Execution Input](https://www.stedi.com/docs/healthcare/api-reference/get-execution-input) endpoint.

For event schemas, see our [event types](https://www.stedi.com/docs/healthcare/event-destinations-event-types) reference.