Delivery and Retries
Meldoc delivers webhooks at-least-once over HTTPS with automatic retries. Your endpoint should respond quickly — treat heavy processing as a background task.
What counts as success
Any 2xx response code is treated as success. A non-2xx status, a network error, or a timeout triggers a retry.
Retry schedule
| Attempt | Delay after previous failure |
|---|---|
| 1 | Immediate |
| 2 | 1 minute |
| 3 | 10 minutes |
| 4 | 1 hour |
After four failed attempts the delivery is marked failed and no further retries are made.
URL restrictions
HTTPS required for any non-localhost URL. http:// is accepted only for localhost and 127.0.0.1 — useful for local development.
Private IPs blocked — RFC 1918 ranges (10.x, 172.16–31.x, 192.168.x) and link-local addresses (169.254.x, fe80::) are rejected even over HTTPS. This prevents server-side request forgery.
Delivery log
Open a webhook and select the Deliveries tab to view its delivery log. Each entry shows:
- Event — the event type that triggered the delivery.
- Status —
pending,retrying,success, orfailed. - Attempt — which delivery attempt this row represents.
- HTTP — the response code your endpoint returned.
- Duration — how long the attempt took, in milliseconds.
- Scheduled — when the attempt was scheduled.
Use the Status and Event type filters to narrow the log, and Load more to page through older deliveries.
Select Redeliver on any entry to enqueue a fresh delivery of that payload. Useful for replaying a missed event or testing your receiver.
Tip: The log retains up to 500 entries per webhook and clears entries older than 30 days automatically.
What’s next?
Verifying Webhook Signatures — Verify that deliveries come from Meldoc.
Webhook Events — Browse the full event catalog.