Quickstart — Send Your First Request with GetRequest

GetRequest requires no SDK, no code changes, and no redeployment. You create an endpoint in the dashboard, point your callers at the URL it gives you, and every request is captured automatically. Follow the three steps below to see it working end to end.

Create an endpoint

Field	Example value	Notes
Name	`User login`	Human-readable label shown in the dashboard
Slug	`/auth/login`	Appended to your project URL to form the full path
Method	`POST`	Accepts GET, POST, PUT, PATCH, or DELETE
Action	`JSON`	Start with JSON to return a mock response immediately

Paste a sample JSON response body so GetRequest knows what to return:

{
  "token": "eyJhbGciOiJIUzI1NiJ9...",
  "user": { "id": 1, "email": "you@example.com" }
}

Click Create. Your endpoint goes live immediately — no deploy, no waiting.Your full endpoint URL will look like this:

https://e.getrequest.io/ddfkU760XMs2z7te/auth/login

The segment between e.getrequest.io/ and your slug (ddfkU760XMs2z7te above) is your project URI — unique to your project. Copy it from the project page in the dashboard.

Send your first request

Grab your API key from Settings → API Key. Every request to a GetRequest endpoint must include this key in the x-api-key header.Replace {project_uri} with your actual project URI and fire a request:

curl -X POST https://e.getrequest.io/{project_uri}/auth/login \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "you@example.com", "password": "secret"}'

const response = await fetch('https://e.getrequest.io/{project_uri}/auth/login', {
  method: 'POST',
  headers: {
    'x-api-key': 'YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ email: 'you@example.com', password: 'secret' }),
});

const data = await response.json();
console.log(data);

import requests

response = requests.post(
    'https://e.getrequest.io/{project_uri}/auth/login',
    headers={
        'x-api-key': 'YOUR_API_KEY',
        'Content-Type': 'application/json',
    },
    json={'email': 'you@example.com', 'password': 'secret'},
)

print(response.json())

$client = new \GuzzleHttp\Client();

$response = $client->post('https://e.getrequest.io/{project_uri}/auth/login', [
    'headers' => [
        'x-api-key' => 'YOUR_API_KEY',
        'Content-Type' => 'application/json',
    ],
    'json' => ['email' => 'you@example.com', 'password' => 'secret'],
]);

echo $response->getBody();

You’ll get back the JSON response body you configured in Step 1:

{
  "token": "eyJhbGciOiJIUzI1NiJ9...",
  "user": { "id": 1, "email": "you@example.com" }
}

Verify in Logs

Open your project in the dashboard and click Logs. You’ll see the request you just sent listed with its method, status code, path, and duration.Click any row to inspect the full detail:

Request — complete headers, query parameters, and body exactly as they arrived
Response — status code, headers, and the body that was returned
Timing — total end-to-end duration for the request

On Pro, click Share on any log entry to generate a public link to that request/response pair — useful for bug reports, postmortems, and team debugging sessions.

What’s next

Now that you have a working endpoint, explore what GetRequest can do when things go wrong in production.

Forward to your backend

Switch your endpoint from a JSON mock to a real upstream URL to proxy live traffic through GetRequest.

Capture webhooks

Point Stripe, GitHub, or any webhook provider at GetRequest so no event is ever silently dropped.

Recover from failures

Replay any captured request after a backend outage or failed deploy and confirm your system handled it correctly.

Share incident evidence

Generate a public link to any request/response pair and share it instantly in Slack or a Jira ticket.

Get Started

Core Concepts

Guides

Account

Quickstart — Send Your First Request with GetRequest

What’s next

Forward to your backend

Capture webhooks

Recover from failures

Share incident evidence

​What’s next

Forward to your backend

Capture webhooks

Recover from failures

Share incident evidence

What’s next