Skip to main content

Introduction

Webhooks are a way for Swervpay to provide real-time data to your application. They are HTTP callbacks that receive notification messages for events. When an event occurs, Swervpay sends an HTTP POST request to the webhook’s configured URL. Your endpoint should respond with a 2xx status code to indicate that the event has been successfully received.

Creating a Webhook

You can create a webhook from the dashboard.

Contactless activation subscriptions

Contactless activation codes are confidential and are not sent to a webhook by default. To receive them, explicitly subscribe one enabled HTTPS webhook to card.contactless.activation. Create a subscribed webhook:
Or update an existing webhook:
The endpoint must:
  • Use HTTPS.
  • Return a 2xx response.
  • Be the only enabled webhook subscribed to card.contactless.activation for the business.
When no unique eligible subscription can be resolved, or delivery fails, Swervpay sends the activation code using the standard Swervpay email instead.
Supplying events when editing replaces the webhook’s stored event list. Include every event that should remain explicitly registered. Omitting events preserves the existing list.

Authentication

All webhook requests include a X-SWERV-SECRET header for verification. It should match the secret generated when creating the webhook. The confidential card.contactless.activation event uses an HMAC signature instead of X-SWERV-SECRET. See the card webhook documentation for its headers and verification procedure.

Retry

If a webhook fails, you have two main options to retry the failed delivery: