Webhooks

Test, retry and redeliver

Every request Jodie sends is recorded against its endpoint, so you can see exactly what was sent, what came back and how long it took.

Retries

A delivery succeeds when your endpoint replies with any 2xx status within 3 seconds. Anything else counts as a failure: a 4xx or 5xx status, a redirect, a timeout, or a connection or TLS error.

After a failure, Jodie tries again, up to 3 attempts in total:

AttemptWhen
1As soon as the activity finishes
2About 10 seconds later
3About 2 minutes after that

While retries are pending, the delivery shows as Retrying. If the third attempt fails too, it's marked Failed and isn't retried again automatically. You can still redeliver it.

Because a retry can follow a request your endpoint actually processed (for example, when it replied after the 3-second timeout), the same delivery can reach you more than once. Every attempt of one delivery has the same Delivery-Id header, so store the IDs you've handled and skip repeats.

The delivery log

Open an endpoint from Integrations › Webhooks to see its Deliveries card. It shows:

  • totals for the last 7 days: deliveries, failures and the last delivery
  • a table of every request, with its status, activity, response code, time taken and when it was sent
  • filters for status (Pending, Retrying, Delivered, Failed) and activity type

Test events and redeliveries are labelled Test and Redelivery in the table. Deliveries are kept for 7 days, then deleted.

On a phone, the table hides the Response and Time taken columns. Open a delivery to see them.

Delivery details

Click any delivery to open its details. Each delivery has its own link, so you can share it with a teammate.

The Delivery details panel for a failed website chat delivery, showing a Redeliver button, the delivery and activity IDs, the destination, timing, attempts, the error, the 422 response body and the request headers
Delivery details show the error, the response and the exact request.

The details show:

  • Delivery ID (the Delivery-Id header) and Activity ID (the call_id or conversation_id in the body)
  • where it was sent to, when it was sent and finished, the number of attempts and the time taken
  • What went wrong, for failures
  • the Response: status code and body (the first 8,000 characters are stored)
  • the Request: every header, including Signature, and the exact JSON body

Send a test event

Use Send test event on the Webhooks list or on an endpoint's page, then pick a kind of activity: call, WhatsApp, email or website chat.

Test events:

  • use sample data (a call or conversation with "Sam Taylor" asking for a boiler quote), with IDs such as call_sample0000000000000000
  • carry a Test-Event: true header, so your receiver can skip saving them
  • are signed with the endpoint's real secret
  • are sent once, straight away, with no retries, and open the result as soon as it's back

Redeliver a request

Click Redeliver in a delivery's details to send the same payload again to the endpoint's current URL. This is useful after you fix a bug in your receiver or change the endpoint's URL.

A redelivery:

  • sends the original body unchanged, freshly signed with the endpoint's secret
  • is a new delivery with its own Delivery-Id, linked to the original in the log
  • is sent once, straight away, with no retries

Because a redelivery has a new Delivery-Id, use the call_id or conversation_id in the body if you need to recognise the same activity across redeliveries.

Sending test events and redeliveries is limited to 20 a minute.

Need a hand?

Our team can help you connect Jodie to your systems.

Email [email protected]