Configure and test event destinations

You can configure event destinations that automatically send Stedi events to your endpoint. Events indicate changes to Stedi resources, such as transaction enrollment requests.

In each event message, Stedi includes a signature you can use to verify its authenticity. Stedi also automatically manages retries for event deliveries and sends you notification emails when there are repeated failures.

Currently, you can configure event destinations for Stedi transaction enrollment events. More event types, including transaction processing events, will be available in future releases.

Create event destinations

You can create up to 16 event destinations per Stedi account. To create event destinations:

1. Go to the Event destinations page in your Developer settings.

2. Click All event destinations.

3. Click + New destination.

4. Enter the following information into the Create an event destination form:

   1. Name: Choose a descriptive, human-readable name for the event destination. Stedi displays this name in the portal for identification.
   2. URL: Enter the webhook URL where you want Stedi to send events.
   3. Description: Optionally, describe the intended use for the destination in more detail. This description will be displayed in the Stedi portal.
   4. Events: Select the event types you want to send to the designated webhook URL.

5. Click Create destination. Stedi displays a modal containing the signing secret for this webhook. Save it to a secure location. You'll need it to verify that the events you receive are from Stedi.

You can now begin testing the event destination.

Trigger test events

You can manually trigger event.ping events for any configured event destination. To trigger test events:

1. Go to the Event destinations page in your Developer settings.
2. Click the event destination you want to test.
3. Click the Event deliveries tab.
4. Click the Ping button.

Stedi attempts to deliver an event.ping to the designated webhook URL. You can review its status and details on the Event deliveries tab.

Secrets

Stedi generates a secret for each event destination. You can use the secret to verify the authenticity of the event messages you receive from Stedi.

Manage secrets

You can review, copy, and rotate an event destination's secret at any time from its Overview tab.

Rotate secret

You can rotate the secret in accordance with your organization's security policies. To rotate the secret for an event destination:

1. Go to the Event destinations page in your Developer settings.
2. Click the event destination you want to edit to go to its Overview tab.
3. Under Signing secret, click the Rotate secret icon.
4. Select an Expiry period. This is the number of hours the previous secret should remain valid after rotation. Available options are:
   • 0 hours (previous secret expires immediately)
   • 24 hours
   • 720 hours (30 days)
5. Click Rotate.

If you specified an expiry period, the event message will contain two signatures until that period has concluded: one matching the previous secret and one matching the new secret. You'll need to run any verification steps with both until the expiry period ends.

Each event destination can have only two active secrets at a time. If you set an expiry period for the rotated secret, you must wait until that expiry period has passed before attempting to rotate the secret again.

Edit event destinations

You can review a list of all configured event destinations from the Event destinations page in your Developer settings.

Click the ellipses (...) to the right of any destination to view, edit, disable, re-enable, or delete it.

Disable vs. delete

Disabling an event destination causes Stedi to stop sending new events to the webhook. Stedi also attempts to complete any in-progress retry attempts, and then pauses additional retries until the event destination is re-enabled. Once you re-enable the event destination, Stedi resumes retrying undelivered events until the retry limit is reached.

Deleting an event destination stops all event deliveries, including in-progress retry attempts immediately.