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

# GetRequest: Capture, Inspect, and Replay HTTP Requests

> Everything you need to capture, replay, mock, and share HTTP traffic with GetRequest — the reliability layer that sits between callers and your backend.

GetRequest sits between your API callers and your backend, capturing every HTTP request that passes through it. Whether your backend is up, down, or mid-deploy, no traffic is ever silently dropped — you can inspect every request, replay anything that failed, and share exact request/response pairs with your team.

## Explore the docs

<CardGroup cols={2}>
  <Card title="Introduction" icon="book-open" href="/introduction">
    Learn what GetRequest does, how it works, and which plan fits your needs.
  </Card>

  <Card title="Quickstart" icon="bolt" href="/quickstart">
    Create your first endpoint and send a real request in under two minutes.
  </Card>

  <Card title="Core Concepts" icon="shapes" href="/concepts/endpoints">
    Understand endpoints, endpoint types, and how requests flow through GetRequest.
  </Card>

  <Card title="Guides" icon="map" href="/guides/api-mocking">
    Step-by-step walkthroughs for mocking APIs, capturing webhooks, and more.
  </Card>
</CardGroup>

## What you can do

<CardGroup cols={2}>
  <Card title="Capture Every Request" icon="database" href="/introduction">
    Every request that hits your GetRequest endpoint is logged in full — headers, body, status code, and timing. Nothing is dropped, even during an outage.
  </Card>

  <Card title="Replay After Failures" icon="rotate-right" href="/guides/recover-failures">
    After a failed deploy or backend outage, replay any captured request with a single click and confirm your system processed it correctly.
  </Card>

  <Card title="Mock API Responses" icon="code" href="/guides/api-mocking">
    Return a static JSON payload from any endpoint to unblock frontend teams, write integration tests, or prototype without a live backend.
  </Card>

  <Card title="Share Incident Evidence" icon="link" href="/guides/share-evidence">
    Generate a public, shareable link to any request/response pair and paste it straight into a Slack message or Jira ticket.
  </Card>
</CardGroup>