> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getrequest.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Share Request and Response Evidence with Your Team

> Generate a public link to any captured request and response so your team can view incident evidence instantly, no GetRequest account required.

When something breaks in production, debugging slows down because evidence is scattered — backend logs in one place, Slack threads in another, Jira comments somewhere else. GetRequest lets you link directly to the exact request and response that caused an issue. Anyone you share the link with can view it immediately, no account required.

<Note>
  Shareable links require the **Pro plan**.
</Note>

***

## Generate a shareable link

<Steps>
  <Step title="Open the log entry">
    Find the request in **Logs** and click the row to open the full detail view.
  </Step>

  <Step title="Click Share">
    Click the **Share** button. GetRequest generates a unique public URL instantly.
  </Step>

  <Step title="Copy and distribute">
    Copy the link and paste it anywhere — Slack, GitHub, Jira, Notion, Linear, or email.
  </Step>
</Steps>

Every shareable link follows this format:

```text theme={null}
https://getrequest.io/s/abc123xyz
```

***

## What the recipient sees

Anyone who opens the link gets a read-only view of the full captured exchange:

* **Request** — method, path, headers, query parameters, and body
* **Response** — status code, headers, and body
* **Timing** — how long the request took end-to-end
* **Shared at** — the timestamp when the link was created
* **Expires at** — the date the link will stop working

No account. No login. No permissions to configure. The link works for anyone who has it.

***

## Link expiry and revocation

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 original log entry and click **Revoke**. The link becomes invalid immediately — anyone who tries to open it will see a 404.

***

## When to use shareable links

<CardGroup cols={2}>
  <Card title="Bug reports" icon="bug">
    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.
  </Card>

  <Card title="Customer support" icon="headset">
    A customer reports an error. Share the link with your support team so they can see exactly what the customer sent and what your backend returned.
  </Card>

  <Card title="Cross-team debugging" icon="arrows-split-up-and-left">
    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 instead of competing narratives.
  </Card>

  <Card title="Postmortems" icon="file-lines">
    Attach the specific failing request to your incident report. The evidence is immutable, timestamped, and accessible to everyone reviewing the incident.
  </Card>

  <Card title="Code review" icon="code-pull-request">
    Paste the link in a PR comment to show the actual request and response that a change needs to handle correctly.
  </Card>
</CardGroup>

***

## Link limits

| Limit                      | Value     |
| -------------------------- | --------- |
| Links generated per minute | 30        |
| Link lifetime              | 30 days   |
| Account required to view   | No        |
| Account required to revoke | Yes (Pro) |