Skip to main content

Webhook API Reference

Merdeka Webhooks deliver real-time event notifications to your endpoint whenever leads or projects change. Instead of polling, your system receives a POST request the moment something happens.

What You Can Do​

  • Create & manage webhooks — register your endpoint, choose which events to subscribe to, and filter which data fields are included in the payload.
  • Monitor delivery health — view delivery logs, check success/failure rates, and inspect the exact payload that was sent.
  • Control granularity — subscribe only to the events you care about (lead.created, project.updated, etc.) and filter payloads down to specific fields.

Base URL​

https://externals.merdeka.app/api/v1/bridge-subscription

Available Events​

EventDescription
lead.createdA new lead has been created
lead.updatedAn existing lead has been updated
project.createdA new project has been created
project.updatedAn existing project has been updated

Payload Example​

When an event fires, your endpoint receives:

{
"eventSlug": "project.updated",
"entityType": "project",
"entityId": "4a51e919-9d74-4b8e-94e7-0c99ac879c53",
"occurredAt": "2026-07-30T09:17:48.872Z",
"data": {
"project": {
"name": "Alexandre Fry",
"epc": { "name": "Tynergy" },
"salesRep": { "firstName": "Greta", "lastName": "Knowles" }
}
}
}

Security​

Merdeka authenticates each delivery by including a static secret in a custom HTTP header you define during webhook setup (e.g., X-Enzy-Auth: your-secret). Your endpoint should verify this header before processing.

See Receiving Webhooks for verification code examples in Node.js, PHP, and Python.

Delivery & Retries​

SettingValue
Max attempts3 (1 initial + 2 retries)
BackoffExponential (1s → 2s)
Timeout15 seconds per request

Failed deliveries (non-2xx, timeout, network error) are retried automatically. After all attempts fail, the delivery is marked as failed in the delivery logs.

Getting Started​

  1. Follow the Webhook Guide for step-by-step setup from the Backoffice UI.
  2. Read Receiving Webhooks for verification, retry behavior, and per-event sample payloads.
  3. Or use the API endpoints below to manage webhooks programmatically.