Skip to content
Latch

Webhooks

Webhooks let you forward Latch events to your own backend — to sync customers into your CRM, kick off onboarding emails, or audit subscription changes. Each webhook is a URL plus the list of events it cares about.

Webhooks list

Section titled “Webhooks list”

Each row shows the destination URL, subscribed events, and recent delivery status. Expand a row to see the latest delivery attempts, response codes, and bodies — useful for debugging without leaving the dashboard.

Creating a webhook

Section titled “Creating a webhook”

Click Create Webhook and provide:

  • URL — your HTTPS endpoint
  • Events — pick from the grouped list:
    • Forms — newsletter.subscribe, data.submit
    • Subscription — subscription.created, .updated, .cancelled, .trial_ended
    • Invoice — invoice.paid, .payment_failed, .upcoming
    • Customer — customer.created, .updated, .deleted
    • Paywall + Experiment — paywall.shown, .dismissed, .converted, experiment.assigned, .converted

On creation, Latch shows the signing secret once — copy it now and store it somewhere safe; it cannot be retrieved later.

Verifying signatures

Section titled “Verifying signatures”

Every delivery is signed with HMAC-SHA256 using the webhook’s secret, in the X-Latch-Signature header. See Webhooks (REST API) for the verification recipe in your language of choice.

Common actions

Section titled “Common actions”
  • Edit — change the URL or event list (the secret is preserved).
  • Delete — stop deliveries and remove the webhook.
  • Inspect deliveries — expand a row to see the most recent attempts and retries.

API reference

Section titled “API reference”
  • GET /api/v1/admin/webhooks
  • POST /api/v1/admin/webhooks
  • PATCH /api/v1/admin/webhooks/:id
  • DELETE /api/v1/admin/webhooks/:id

The full event payload schemas live under REST API · Webhooks.