Use Request Inspector

Create a temporary HTTP endpoint, send requests to it, and inspect exactly what arrived in real time. No receiver application or server setup is required.

Create a public endpoint

How it works

Three simple steps from endpoint creation to payload inspection.

  1. Step 1

    Create an endpoint

    Choose a name and password. Request Inspector generates a unique URL for receiving test requests.

  2. Step 2

    Send HTTP requests

    Use the generated URL as a webhook destination or as the target of your HTTP client, script, or application.

  3. Step 3

    Inspect the result

    Open the endpoint display to see new requests immediately and compare their contents with what your integration should send.

What you can inspect

Each captured request provides the details needed to troubleshoot an HTTP integration:

  • HTTP method, requested path, and query parameters
  • Request headers and content type
  • Request body and submitted payload
  • Arrival time and recent request history

Common uses

Common workflows where real-time inspection accelerates troubleshooting:

  • Configure and verify webhook deliveries
  • Debug malformed payloads or missing headers
  • Test HTTP clients, scripts, and automation
  • Compare expected and received request data

Service limits

Limits keep the shared service responsive. Registered-user endpoints provide longer history and retention than public endpoints.

Limit Public endpoint Registered-user endpoint
Request rate 20 req/sec 20 req/sec
Maximum request body 64 KB 64 KB
Requests shown in history 100 250
Request retention 2 days 10 days

The request-rate limit corresponds to 100 requests in 5 seconds. Keep test traffic and request bodies within these values.

Security and data lifetime

Best practices and automated retention policies.

Protect access

New public endpoints require a password to open the captured-request display. Use a strong, unique password and share the display URL only with people who need access.

Avoid sensitive production data

Captured requests can contain credentials, personal data, or private payloads. Prefer test data and remove secrets before sending a request.

Endpoints expire automatically after 180 days without access. Request history is removed according to the retention limits shown above.