> ## 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.

# Frequently Asked Questions about GetRequest

> Answers to common questions about how GetRequest handles request storage, latency, quotas, binary payloads, API key rotation, Replay, and team access.

If you're just getting started or running into something unexpected, this page covers the questions that come up most often. Browse by topic or use your browser's search to find what you need.

<AccordionGroup>
  <Accordion title="How long are requests stored?">
    Log retention depends on your plan:

    | Plan | Retention |
    | ---- | --------- |
    | Free | 7 days    |
    | Dev  | 30 days   |
    | Pro  | 30 days   |

    Logs older than your retention window are automatically deleted. If you need to keep a specific log entry, upgrade your plan before the window closes — retention applies going forward from the moment you upgrade.
  </Accordion>

  <Accordion title="Does GetRequest add latency to my API?">
    For **Forward** endpoints, GetRequest adds less than 5ms of overhead per request. That overhead covers edge interception, logging, and proxying to your upstream — it's designed to be invisible in practice.

    For **JSON** endpoints, there is no upstream call at all. The response is returned directly from GetRequest's edge infrastructure with sub-millisecond overhead.
  </Accordion>

  <Accordion title="What happens if my backend is slow or unresponsive?">
    Forward endpoints wait up to **3 seconds** for your upstream to respond. If your backend exceeds that timeout, GetRequest returns `504 Gateway Timeout` to the caller. The request is still captured and logged — with the timeout noted — so you can replay it once your backend recovers.
  </Accordion>

  <Accordion title="Can I send binary payloads (images, files)?">
    Yes. GetRequest forwards any request body, including binary data such as images and file uploads. Binary payloads are base64-encoded in storage so they can be safely logged and inspected. The maximum body size is **1 MiB** per request.
  </Accordion>

  <Accordion title="Is my API key the same as my project URI?">
    No — these are two different things and serve different purposes.

    * **API key** — authenticates you to GetRequest's API Gateway. Include it as the `x-api-key` header in every request. Find it at **Settings → API Key**.
    * **Project URI** — the routing token embedded in your endpoint URL (e.g., `ddfkU760XMs2z7te`). It tells GetRequest which project a request belongs to. Find it on your project page.

    Your API key is a credential; your project URI is an address. Never substitute one for the other.
  </Accordion>

  <Accordion title="What happens when I exceed my monthly quota?">
    Requests that exceed your monthly quota are rejected at the API Gateway with `HTTP 429 Too Many Requests`. They do not reach your backend and are not logged. Upgrade your plan to restore access immediately — mid-period upgrades are prorated, so you only pay for the remaining time in the billing cycle.
  </Accordion>

  <Accordion title="Can I replay requests on the Free or Dev plan?">
    No. Request Replay is a **Pro-only** feature. On Free and Dev plans you can view and inspect every captured log in full detail, but you cannot re-fire requests from the dashboard. Upgrade to Pro to unlock Replay.
  </Accordion>

  <Accordion title="Do shareable links require the recipient to have an account?">
    No. Anyone with the link can view the full request and response — headers, body, status, and timing — with no login, no account, and no permissions required. Links expire after **30 days** or when you revoke them, whichever comes first. Shareable links are a Pro feature.
  </Accordion>

  <Accordion title="Can I use GetRequest with multiple environments (dev, staging, prod)?">
    Yes. Create a separate **project** for each environment. Each project gets its own URI and its own set of endpoints, keeping traffic cleanly isolated. Your API key is shared across all projects on your account — you don't need a separate key per environment.
  </Accordion>

  <Accordion title="Can multiple team members access the same project?">
    Team access is coming soon. Currently each account has its own projects and endpoints with single-user access. In the meantime, you can share individual log entries with teammates using **shareable links** (Pro) — they can view the full request and response without needing access to your account.
  </Accordion>

  <Accordion title="How do I rotate my API key?">
    Go to **Settings → API Key** and click **Regenerate**. Your old key is invalidated immediately — update any clients, services, or environment variables using the old key before you click Regenerate.

    <Warning>
      There is no grace period after regeneration. The old key stops working the instant the new one is issued. Make sure all your integrations are ready before you proceed.
    </Warning>

    You can regenerate up to **6 times per hour**. If you reach that limit, wait for the hour to reset before generating again.
  </Accordion>

  <Accordion title="Is GetRequest suitable for production traffic?">
    Yes. Forward endpoints are used in production by teams that need full request visibility, capture-and-replay capability, and a safety net during deploys and outages. GetRequest is designed for high availability and low latency, adding less than 5ms of overhead per request.
  </Accordion>
</AccordionGroup>