Getting Started

Here’s the fastest way to see what getrequest actually does: create an endpoint, send it a request, and watch that request make the round trip. This walkthrough uses a retail checkout call — a case where the caller needs your real response back — but every step here works identically for any endpoint you create.

Step 1: Create an endpoint

Sign in to app.getrequest.io and open your project.
Click New Endpoint.
Fill in the fields:

Field	Example	Notes
Name	`Order checkout`	Human-readable label — for your own reference, not part of the URL
Method	`POST`	Choose one or more: GET, POST, PUT, PATCH, DELETE
Action	`Sync API`	Proxies inline and returns your destination’s exact response
Destination URL	`https://postman-echo.com/post`	A public echo endpoint, so this walkthrough works without a backend of your own

Click Create. getrequest generates a unique, random ID for the endpoint and it’s live immediately.

Your endpoint URL will look like this:

https://e.getrequest.io/aB3dEf7gH9jK2mN4

That ID (aB3dEf7gH9jK2mN4 above) is auto-generated, unique to this endpoint, and permanent — there’s no separate project identifier or slug to configure. Copy the full URL from the endpoint page.

Step 2: Send your first request

Simulate a checkout request:

curl -X POST https://e.getrequest.io/aB3dEf7gH9jK2mN4 \
  -H "Content-Type: application/json" \
  -d '{
    "order_id": "ord_8841",
    "items": [{ "sku": "SKU-123", "qty": 2 }],
    "total": 59.98
  }'

const response = await fetch('https://e.getrequest.io/aB3dEf7gH9jK2mN4', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    order_id: 'ord_8841',
    items: [{ sku: 'SKU-123', qty: 2 }],
    total: 59.98,
  }),
});

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

import requests

response = requests.post(
    'https://e.getrequest.io/aB3dEf7gH9jK2mN4',
    headers={
        'Content-Type': 'application/json',
    },
    json={
        'order_id': 'ord_8841',
        'items': [{'sku': 'SKU-123', 'qty': 2}],
        'total': 59.98,
    },
)

print(response.json())

$client = new \GuzzleHttp\Client();

$response = $client->post('https://e.getrequest.io/aB3dEf7gH9jK2mN4', [
    'headers' => [
        'Content-Type' => 'application/json',
    ],
    'json' => [
        'order_id' => 'ord_8841',
        'items' => [['sku' => 'SKU-123', 'qty' => 2]],
        'total' => 59.98,
    ],
]);

echo $response->getBody();

Because this is a Sync API endpoint, you get back the destination’s exact response — not something getrequest invents. postman-echo.com echoes whatever it received, so the response looks like this:

{
  "args": {},
  "data": "",
  "json": {
    "order_id": "ord_8841",
    "items": [{ "sku": "SKU-123", "qty": 2 }],
    "total": 59.98
  },
  "headers": { "...": "..." },
  "url": "https://postman-echo.com/post"
}

That json field is your original payload, sent back unchanged — proof that getrequest proxied it through untouched. Point the Destination URL at your own backend instead, and this same response would be whatever your backend returns. getrequest didn’t just relay that request, though — it also kept a copy. That’s what the next step shows you.

Step 3: Verify the request arrived

Open your project in the dashboard and click Logs. You’ll see the request you just sent — method, status, path, and duration. Click the row to inspect:

Request — full headers, query params, and body
Response — status code, headers, and body
Timing — how long it took end to end

This is exactly what getrequest captures for every request it receives. Nothing is dropped, even before your backend ever sees it.

On paid plans, you can click Share on any log entry to generate a public link — useful for bug reports and team debugging. See the FAQ for which plans.

You just sent a real request through getrequest, got your destination’s exact response back, and watched the whole exchange land in Logs — no code, no config file, no redeploy. The next step is pointing this at your real backend instead of a public echo endpoint, and deciding how you want getrequest to behave when it gets there: wait for the response like you just did, hand it off in the background, or skip the backend entirely with a mock.

What’s next

Sync vs. Async endpoints

Choose an immediate response or a queued, retried background delivery.

Authenticate endpoints and destinations

Require credentials on incoming requests and attach them to outgoing calls.

Launch APIs without a backend

Use Static API to mock a response before your backend exists.

Recover from failures

Replay any captured request after an outage.

Bulk retry many requests

Retry a manual selection or an entire filtered set in one action.

Share incident evidence

Generate a public link to any request/response pair.

Limits, timeouts & error responses

Every status code, timeout, and size cap getrequest applies, in one place.

Get Started

Guides

More

Step 1: Create an endpoint

Step 2: Send your first request

Step 3: Verify the request arrived

What’s next

Sync vs. Async endpoints

Authenticate endpoints and destinations

Launch APIs without a backend

Recover from failures

Bulk retry many requests

Share incident evidence

Limits, timeouts & error responses

​Step 1: Create an endpoint

​Step 2: Send your first request

​Step 3: Verify the request arrived

​What’s next

Sync vs. Async endpoints

Authenticate endpoints and destinations

Launch APIs without a backend

Recover from failures

Bulk retry many requests

Share incident evidence

Limits, timeouts & error responses

Step 1: Create an endpoint

Step 2: Send your first request

Step 3: Verify the request arrived

What’s next