What a recipient can do
When someone opens a share link, they get a full read-only view of the captured event.Inspect headers and body
View every captured header and the raw request body, formatted for readability. The same redaction rules apply —
authorization and cookie are shown as [REDACTED].Copy payload as JSON
Download or copy the entire event as a structured JSON object, ready to paste into a test fixture or a ticket.
Rebuild a cURL command
Generate a ready-to-run
curl command that reproduces the original request, including method, headers, and body.No account needed
Recipients do not need a Webhooktrap account to view a shared event. Opening the link is all it takes.
What a recipient cannot do
Share links are strictly read-only. A recipient cannot:- Replay the event to any destination URL
- Modify the inbox configuration or event data
- Delete events or the inbox itself
- Access any other event in the same inbox
How to generate a share link
- Dashboard
- API
Open the event
Navigate to your inbox in the Webhooktrap dashboard and click the event you want to share.
Use cases
- Collaborate on a bug — paste the share link into a GitHub issue or Slack message so a teammate can see the exact payload that caused the problem, without needing access to your inbox.
- Document an integration — attach a share link to a pull request to show reviewers the real payload your new handler will process.
- File a support ticket — send a share link to a provider’s support team as evidence of what their webhook actually contained.
A share link becomes inaccessible when the underlying event is deleted or when the inbox it belongs to expires. Anonymous inboxes expire after 48 hours, so share links from anonymous inboxes have the same effective lifetime. If you need a permanent share link, capture the event in a saved inbox first.
