Skip to main content

Endpoints, events, and deliveries

Use this page after you understand the Webhooks overview. It explains the day-to-day workflow for endpoints, events, deliveries, and replay.

Switera webhooks service tabs for endpoints, deliveries, event catalog, and test send
The Webhooks service is organized by endpoint setup, delivery history, event catalog, and test send.

Create an endpoint​

Switera add webhook endpoint form with sample endpoint URL
Use a stable HTTPS URL from a system that can validate signatures and return quickly.
  1. Open Endpoints.
  2. Select Add Webhook.
  3. Enter the endpoint URL.
  4. Add a readable endpoint name if the form asks for one.
  5. Choose event subscriptions.
  6. Save.
  7. Store the endpoint secret in the receiver environment.

Choose event subscriptions​

Start small. Subscribe to one event family first, then add more after the receiver is proven.

For each event, ask:

  • does the receiver need this event?
  • what action will happen when the event arrives?
  • is the action idempotent?
  • what data should be stored for troubleshooting?
  • who owns the receiver if delivery fails?

Send a test event​

Use Test Send before enabling real traffic.

Check:

  • the receiver receives the request
  • signature verification passes
  • the receiver returns a success status quickly
  • the event payload is parsed correctly
  • duplicate delivery does not create duplicate business records
  • logs contain the delivery ID

Review deliveries​

Use Deliveries when something fails or when you need proof of delivery.

Review:

  • delivery status
  • event type
  • endpoint name
  • attempt count
  • response status
  • response body or error summary
  • last attempt time

Retry and replay​

Retry only after fixing the receiver. Replaying failed deliveries before the receiver is corrected usually creates repeated failures.

Safe retry pattern:

  1. Inspect the failed delivery.
  2. Fix the receiver or subscription.
  3. Send a test event.
  4. Retry one failed delivery.
  5. Confirm success.
  6. Retry the remaining affected deliveries.

Receiver implementation checklist​

  • accepts HTTPS
  • verifies signatures
  • returns 2xx quickly after validation
  • stores event ID or delivery ID
  • handles duplicates
  • logs enough context for diagnosis
  • keeps secrets out of logs

Related pages: