How long does a webhook inbox last?

Thirty minutes from the last request or page refresh. Inboxes live in memory on the server and are gone after a restart - this is a throwaway tool, not storage.

Can I send production webhooks to it?

No. Anyone with the URL can read what arrives, and a real conversation delivery contains a customer name, number and transcript. Use it to learn the payload shape, then point the webhook at your own endpoint.

bitpull.io

Free tool

Webhook tester

A throwaway URL that captures whatever is sent to it and shows you the headers and body exactly as they arrived. No account, nothing stored longer than half an hour.

Create an inbox, paste its URL into the agent's outbound webhook field, and press Test in the bitpull dashboard. Whatever arrives appears below.

How to use it with a bitpull agent

Create an inbox above and copy the URL.
In the bitpull dashboard, open your agent → Actions → outbound webhook, paste the URL and make sure the active toggle is on. If the Actions tab is not there, the account capability is not enabled yet - that is what to ask support for.
Press Test. The delivery appears here within a second or two.
Read it. Field names, nesting, which values are actually populated - this is the contract your consumer has to be written against, and it is not published anywhere.
Then have a real conversation with the agent and let it end. A test delivery and a real one are not always identical, and the difference is worth seeing before you deploy anything.

Do not send anything real through this

The inbox lives in memory on this server for half an hour and is readable by anyone who has the URL. That is fine for a test delivery and wrong for a production conversation containing a customer's name, number and transcript. Use it to learn the shape, then point the webhook at your own endpoint.

Testing your own endpoint instead

The other direction is just as useful: before you configure anything in the dashboard, check that your endpoint answers a webhook the way it should.

terminal

# Does your endpoint answer fast enough, and with a 200?
curl -sS -o /dev/null -w 'status %{http_code}  total %{time_total}s\n' \
  -X POST https://your-endpoint.example.com/bitpull \
  -H 'Content-Type: application/json' \
  -d '{"sessionId":"test","summary":{"outcome":"UNRESOLVED"}}'

A correct consumer returns 200 in single-digit milliseconds and does the real work afterwards. If that curl takes two seconds, your integration will drop deliveries under load - the webhooks page covers the shape that survives.