The complete stack for API reliability.
Launch endpoints, observe every request, recover from failures — without managing infrastructure.
Instant endpoints.
Launch a production-ready API endpoint in under 60 seconds. No gateway config, no server to provision, no deployment pipeline. Define your method, slug, and action — getrequest handles the rest.
Return static JSON for mock APIs, or forward to any upstream. Switch between actions without downtime. The infrastructure layer ships with your first request.
- Live in under 60 seconds, zero config
- Mock JSON or proxy any upstream
- No servers, no gateways, no ops overhead
- Edit or delete endpoints at any time
# Define once. Live immediately. method: POST slug: /api/auth/login action: mock_json response: 200 OK { "status": "success", "token": "eyJhbGc..." } # Switch to forwarding with one edit: action: forward destination: api.example.com/auth/login
Live request inspector.
Total observability into every request — headers, body, status code, latency — the moment it lands. No log aggregation pipeline. No custom instrumentation. No Datadog bill. Observability is built into the infrastructure layer.
Whether you're validating a webhook, auditing third-party traffic, or monitoring a live integration, you have a complete picture without writing a single line of logging code.
- 100% request capture, nothing dropped
- Full headers, body, and response
- Real-time stream, no refresh
- Searchable log history up to 30 days
// Captured 2s ago POST /api/auth/login · 200 OK · 43ms content-type: application/json authorization: Bearer eyJhbGc... x-request-id: req_8xm2k9p // Request body { "user": "alice", "action": "login" } // Response body { "status": "success", "token": "eyJhbGc..." }
Request replay.
Recover from failures with certainty. Re-fire any captured request with one click — exact headers, body, and method preserved. Confirm a fix works before it ships. Reproduce production failures locally without reconstructing the context.
Reliability isn't just about preventing failures — it's about recovering fast when they happen. Replay closes the gap between “we got an error report” and “we confirmed the fix.”
- Exact original payload, headers, and method
- Fresh response captured for comparison
- Confirm fixes before merging
- Reproduce production failures locally
// Original — captured 2 hrs ago PUT /api/settings · 500 · 203ms // Replaying with original headers + body status: replaying... // Result PUT /api/settings · 500 · 198ms // Bug confirmed. Response diff available. "error": "Cannot read property 'id' of null" // Fix deployed. Replaying again... PUT /api/settings · 200 OK · 31ms
Shareable debug links.
Turn any captured request into a permanent, shareable URL. Paste it in a Slack message, a Jira ticket, or a PR comment. Anyone with the link sees the full request and response — no account required. Cross-team incident response, without the overhead.
Incident resolution slows down when context lives in one engineer's terminal. Shareable links make every failure a shared artifact — visible, referenceable, and linkable across your entire org.
- Permanent link to exact request snapshot
- Full headers, body, and response visible
- No account required to view
- Works across environments and teams
# Shared request snapshot # Anyone with this link can inspect it POST /api/webhooks/stripe Host: api.example.com stripe-signature: t=1714000000,... content-type: application/json { "type": "payment_intent.succeeded", "data": { "object": { "amount": 4200 } } } --- Response: 500 Internal Server Error Body: { "error": "unhandled event type" }
Smart forwarding.
A transparent proxy layer for any upstream — no SDK, no agent, no code changes required. getrequest routes traffic to your destination, captures the full exchange, and logs everything without modifying a single byte in transit. The routing layer you'd otherwise have to build yourself.
Route to staging, production, or third-party APIs. Validate what your system sends against what the upstream receives. The proxy ships with the infrastructure — there's nothing extra to configure.
- Works with any upstream, any HTTP client
- Zero byte modification in transit
- Full request + response logged
- HTTP and HTTPS supported
# Forward to your real API action: forward destination: api.stripe.com # Every request is proxied and logged: POST /v1/charges → api.stripe.com/v1/charges status: 200 OK latency: 143ms logged: yes GET /v1/customers → api.stripe.com/v1/customers status: 200 OK latency: 67ms logged: yes
Usage metering.
Build a reliability baseline from real traffic data. Track request volume per project, spot usage trends before they become capacity problems, and maintain a full audit trail. Get notified before you hit limits — not after traffic drops.
Reliability starts with measurement. getrequest makes traffic data visible by default — no separate metrics pipeline, no custom dashboards to maintain.
- Real-time usage dashboard, per project
- Pre-limit alerts before incidents happen
- Full audit trail with timestamps
- Capacity planning from real traffic trends
Project Requests Limit Used ───────────────────────────────────────── proj_api 48,231 100,000 48.2% proj_webhooks 12,048 100,000 12.0% proj_staging 7,831 100,000 7.8% ───────────────────────────────────────── Total 68,110 100,000 68.1% ⚠ proj_api on track to exceed limit Upgrade to Pro for 1M requests/mo
The full stack. Available from day one.
No gateway to configure. No observability stack to manage. No ops team required.
Start for free →