Shareable links require a paid plan — see the FAQ for which ones.
Generate a shareable link
1
Open the log entry
Find the request in Logs and click the row to open the detail view.
2
Click Share
Click the Share button. getrequest generates a unique public URL.
3
Copy and paste
Copy the link and paste it anywhere — Slack, GitHub, Jira, Notion, email.
What the recipient sees
Anyone who opens the link sees a read-only view of:- Request — method, path, headers, query parameters, body
- Response — status code, headers, body
- Timing — how long the request took
- Shared at — when the link was created
- Expires at — when the link will stop working
Link expiry
Shareable links expire automatically 30 days after creation. After expiry, the link returns a 404 and the shared content is no longer accessible. If you need to stop sharing a link before it expires, open the log entry and click Revoke. The link becomes invalid immediately.When to use shareable links
Bug reports — Attach the link to a GitHub issue or Jira ticket. The engineer picking it up sees the exact request shape without needing access to your dashboard. Customer support — A customer reports an error. Share the link with your support team so they can see what the customer actually sent and what your backend returned. Cross-team debugging — Your frontend team says the API is broken. Your backend team says it’s fine. Share the log entry — both teams see the same data, not competing narratives. Postmortems — Attach the specific failing request to your incident report. The evidence is immutable and timestamped. Code review — Paste the link in a PR comment to show the actual request/response that a change needs to handle.Link limits
The next time a bug report turns into a “can you send me the exact request?” thread, this is the one-click answer.