Skip to main content
GetRequest sits between your API callers and your backend. Every request that passes through it is captured, inspected, and available to replay — whether your backend was up at the time or not. You point callers at a GetRequest endpoint URL instead of directly at your service, and GetRequest handles the rest transparently.

​
The problem it solves

When your backend goes down, requests vanish. There is no record of what came in, no way to recover what was lost, and your users have already moved on. Webhook providers retry a handful of times and then give up. Misconfigured handlers silently swallow events. A bad deploy flips your API from green to red in seconds with no forensic trail. GetRequest fixes this at the infrastructure level — before a request ever reaches your code.

​
Core capabilities

Relay

Every request is intercepted at the edge and forwarded to your backend transparently. Your callers see no difference.

Retain

Every request and response is logged — headers, body, status code, and timing. Nothing is dropped, even during downtime.

Recover

Replay any captured request with one click after a failed deploy or outage. Confirm your system processed it before closing the incident.

Share

Generate a public link to any request/response pair and drop it in Slack or a Jira ticket for instant, reproducible evidence.

​
How it works

You create an endpoint in GetRequest — no code, no deploy. GetRequest gives you a URL in this format:
Point your callers at that URL instead of your real backend. GetRequest either returns a mock JSON response or forwards the request upstream to your service. Either way, every request is captured and logged in your dashboard. Your project_uri is unique to your project and is shown on the project page inside getrequest.io. Your slug is the path you define when you create an endpoint — for example /auth/login or /webhooks/stripe.

​
Two endpoint types

GetRequest endpoints come in two flavours. You can switch between them at any time with zero downtime and no redeployment.
Switching an endpoint from JSON to Forward — or back — takes effect immediately. All historical logs are preserved regardless of the type change.

​
Authentication

Every request to a GetRequest endpoint must include your API key in the x-api-key header:
Find your API key at Settings → API Key inside the dashboard. Keep it private — it authenticates all traffic routed through your project.

​
Plans

Replay and Share are Pro-only features. If you need to recover traffic after outages or share request evidence with your team, upgrade to Pro from the dashboard.

Create your first endpoint in 2 minutes

Follow the quickstart guide to set up an endpoint, send a real request, and verify it landed in your logs.