Delivery and retries
Timeouts, duplicates, errors and subscription disabling.
On this page
Respond within 10 secondsDuplicates and arrival orderDisablingAllowed destinationsDiagnose a problemRespond within 10 seconds
Your receiver must return an HTTP 2xx status within 10 seconds. Other statuses, timeouts and network errors count as failed attempts and trigger retries. Your response body is not interpreted.
Duplicates and arrival order
Deliveries are asynchronous and may arrive out of order. Retries keep the same id: use it as a deduplication key. Use reservationId, customerId, vehicleId or callRecordId as the stable business identifier for the event. repair.status_changed uses reservationId. Do not assume createdAt represents the order of business changes.
Disabling
A 410 Gone response permanently disables the subscription without retrying. Create a new subscription to resume. Ten consecutive failures also cause disabling and a dashboard notification. One successful delivery resets the failure counter.
Allowed destinations
Only public HTTPS URLs are allowed. Loopback, private, link-local and bare-hostname destinations are rejected both at registration and on every delivery attempt. A forbidden destination disables the subscription without retries.
Diagnose a problem
Read status, consecutiveFailures, lastDeliveredAt and lastError through GET /webhooks. Check your receiver’s HTTPS availability, response time and signing secret. Do not log keys or secrets.