Skip to content
DevelopersBuild with YallaBuy
Merchant guide
HTTPS · Signed events

Operational limits and retention

Every number in one place — the limits governing registration, delivery, replay and retention.

Start building
Reviewed against implementation
YOUR INTEGRATION, AT A GLANCE
Webhook delivery · Headers
POST /your-webhook-endpoint
Content-Type: application/json
webhook-event-type: order.created
webhook-id: <endpoint_id>
webhook-event-id: <event_id>
webhook-delivery-id: <delivery_id>
webhook-timestamp: <unix_seconds>
webhook-signature: v1=<hmac_sha256_hex>
See the implementation
On this page

01The full table

LimitValue
Endpoints per store10 maximum
Types per endpoint1–25 (from the 16 subscribable types)
Endpoint name1–100 chars — unique within the store
Endpoint URLHTTPS only, port 443 or 8443, max 2048 chars
Payload size64 KB maximum (items and variants capped at 100, free text at 500)
Per-attempt deadline10 seconds
Redirect hops3 maximum — every hop re-validated
Signature verification window±300 seconds from webhook-timestamp
Attempts per delivery5 by default (exponential backoff from 60 s up to a 2 h cap)
Delivery cadenceInstant — a kick fires the worker the moment an event lands; the worker also sweeps every minute as a safety net (up to 25 deliveries claimed per pass)
Event retention14 days
Delivery & attempt retention30 days
Replay window14 days from event creation
Replay budget1000 replays/hour/store (events + DEAD retries)
Test-event budget10 presses/hour/store — does not consume the replay budget
Dashboard list pagesUp to 50 rows per request

02What retention means in practice

Keep exploring

The delivery lifecycle and retriesping — the test event (not subscribable)Troubleshooting

COMPLETE YOUR INTEGRATION