Delivered
A request is delivered when your endpoint answers with a2xx status within 15 seconds, connection included.
- Redirects are not followed. A
3xxanswer counts as a failure: give TIKT the final address. - The first 1 KB of your answer is kept in the destination’s log (Recent deliveries), to help you debug. The rest is read and dropped.
- Answer fast, then do the work. If your processing takes long, accept the request first and handle it in the background.
Retries
Any answer other than2xx — or no answer — is tried again, up to 8 attempts over about 27 hours and 35 minutes:
The times are approximate: TIKT checks for due deliveries every few minutes. After the eighth failure, the delivery is given up (gave up in the log); you can still resend it.
When a
429 or 503 answer carries a Retry-After header, TIKT waits at least that long (10 hours at most) before the next attempt.
Every attempt carries the same webhook-id: use it to ignore an event you already handled.
A destination that keeps failing
TIKT turns a destination off when:- it has failed for 3 days in a row (no
2xxsince its first failure), or - it answers
410 Gone: TIKT takes it as “stop sending”.
webhook.endpoint_disabled. Nothing is lost: the events keep piling up for it. Fix your endpoint, then turn the destination back on in Settings › Integrations: the events since its first failure are sent.
You can also turn a destination off yourself: nothing is sent and nothing is lost; turned back on, it catches up.
Resend
Each row of Recent deliveries has a Resend button: TIKT sends the same message again — samewebhook-id — with the objects as they are now. A resend adds a row to the log.