Mantiks POSTs this JSON body to setting.webhook.url when a search export finishes. The request uses Content-Type: application/json. Only HTTP 2xx acknowledges receipt; this does not confirm downstream processing. Redirects are not followed or treated as success. Real export deliveries include X-Mantiks-Delivery-ID (stable delivery ID), X-Mantiks-Attempt-ID (unique per attempt), X-Mantiks-Part (0 for a full payload, 1..N for split parts), and Idempotency-Key (stable per delivery and part). Deduplicate on Idempotency-Key; delivery is not exactly-once. A confirmed manual resend after acceptance creates a new delivery ID and idempotency keys; retries of uncertain receipt keep the original keys. These header names are reserved and cannot be used for custom authentication headers. Connection failures known to occur before sending (including connection timeouts), HTTP 429 and HTTP 5xx are retried up to five attempts per part, with waits of 1 minute, 5 minutes, 30 minutes and 2 hours; a valid Retry-After can extend the wait. A response timeout or interrupted attempt with uncertain receipt requires an explicit manual retry. Other HTTP 4xx responses stop automatic retries, except HTTP 413: Mantiks splits the payload into parts targeting 75 KiB, each containing the same envelope and a subset of leads. Parts with confirmed receipt are not resent when retrying a partial delivery. nb_leads and credits_cost retain the full export totals; use leads.length for the contacts in each POST. A single lead larger than the chunk target remains unsplit. Optional lead fields (reverse_company, icebreaker fields, CV score fields) appear only when enabled on the search. POST /searches/webhook/test sends a mocked payload immediately with the same JSON format, without delivery history, automatic retries, or the four delivery headers.
200Any HTTP 2xx acknowledges receipt. Non-2xx responses are treated as delivery failures.
