WEBHOOKS
Event model
Understand the common event envelope used across Mediloop webhook notifications.
Real-time
Event driven
As events happen
Reliable delivery
Automatic retries
Exponential backoff
Signatures
HMAC SHA-256
Verify every payload
Endpoint limit
100 endpoints
Per tenant
Payload
JSON
Versioned envelope
Event envelope
Event payload
{
"id":"evt_01J...",
"type":"prescription.signed",
"api_version":"2026-08-01",
"created_at":"2026-08-19T10:15:30Z",
"tenant_id":"tenant_123",
"data":{"object":{...}}
}Core fields
| Field | Purpose |
|---|---|
| id | Globally unique event ID |
| type | Event name |
| api_version | Payload contract version |
| created_at | Creation timestamp |
| tenant_id | Originating tenant context |
| data.object | Event object snapshot or reference |
Object snapshots
Payloads contain the fields required for the event contract. Retrieve the authoritative resource from the API when you need current state.
Event IDs
Store processed event IDs and make handlers idempotent. The same event can be delivered more than once.
Ordering
Do not assume global ordering. Where ordering matters, compare resource versions/timestamps and process per object.
Versioning
Webhook contract versions are explicit so integrations can safely migrate payload changes.