Idempotency

Many webhook providers retry after a timeout or non-success response. Hooklane uses a 24-hour idempotency cache to avoid running the same event twice.

Send an Idempotency-Key

Generate a unique identifier for each event and send it with the request:

Idempotency-Key: evt_01HTM2APX7M4D2Q8XF8C3J8AXY

For the next 24 hours, Hooklane treats a request with the same key for the same endpoint as a duplicate. It does not start another Flow execution.

Recommendations

• Reuse the source event ID when your provider supplies one.
• Generate a random UUID or ULID if your sender does not have an event ID.
• Keep the key stable across retries for that event and use a new key for every new event.

The cache is endpoint-scoped, so the same key can safely be used on different Hooklane endpoints.