Payload Format
Each delivery is an HTTP POST with Content-Type: application/json.
Headers
| Header | Value |
|---|---|
Content-Type | application/json |
X-DKP-Event | Event name e.g. lead.created |
X-DKP-Delivery | UUID identifying this specific delivery attempt |
X-DKP-Signature | sha256=<hex> — HMAC-SHA256 of the raw request body |
X-DKP-Attempt | 1-indexed retry counter |
Body structure
{
"event": "lead.created",
"delivery": "a1b2c3d4-e5f6-...",
"created_at": "2026-05-25T14:30:00Z",
"data": {
"id": 12345,
"name": "Jane Doe",
"phone": "555-0101",
"lead_status_id": 88,
"latitude": 37.7749,
"longitude": -122.4194,
"created_by": 47,
"created_at": "2026-05-25T14:30:00Z"
}
}
| Field | Type | Description |
|---|---|---|
event | string | The event type (e.g. lead.created) |
delivery | UUID | Unique ID for this delivery attempt — useful for deduplication |
created_at | ISO 8601 | When the event was dispatched |
data | object | Resource payload specific to the event type |
Use delivery for idempotent processing — the same delivery UUID is used across all retry attempts for the same event.