Skip to main content

Captured Requests

Every HTTP request sent to your debug endpoint is captured and stored for inspection.

Viewing requests in the dashboard​

The dashboard shows captured requests in real time. Each request entry displays:

  • HTTP method (GET, POST, PUT, etc.)
  • Request path (including sub-paths)
  • Remote IP address
  • Timestamp
  • Content preview

Click a request to see its full details.

Request details​

Each captured request includes:

Info​

  • Method — HTTP method used
  • URL — full request URL including query string
  • Remote address — sender's IP address
  • Timestamp — when the request was received
  • Content length — body size in bytes
  • Request ID — unique identifier

Headers​

All HTTP headers sent with the request, displayed as key-value pairs.

Query parameters​

URL query parameters parsed and displayed separately for easy reading.

Body​

The raw request body. JSON bodies are syntax-highlighted and formatted for readability.

Filtering and searching​

Use the search functionality to filter requests by:

  • HTTP method (GET, POST, PUT, etc.)
  • Request path or URL
  • Body content
  • Remote address

Viewing requests via the CLI​

# List recent requests for an endpoint
hooklistener endpoint requests <endpoint-id> --page 1 --page-size 50

# View a specific request
hooklistener endpoint request <endpoint-id> <request-id>

Viewing requests via the API​

# List requests
curl https://app.hooklistener.com/api/v1/endpoints/<endpoint-id>/requests?page=1&page_size=20 \
  -H "Authorization: Bearer hklst_your_api_key"

# Get a specific request
curl https://app.hooklistener.com/api/v1/endpoints/<endpoint-id>/requests/<request-id> \
  -H "Authorization: Bearer hklst_your_api_key"

Deleting requests​

You can delete individual requests from the dashboard, CLI, or API:

# CLI
hooklistener endpoint delete-request <endpoint-id> <request-id>

# API
curl -X DELETE https://app.hooklistener.com/api/v1/endpoints/<endpoint-id>/requests/<request-id> \
  -H "Authorization: Bearer hklst_your_api_key"

Saving replay cases​

When a request should become a repeatable regression test, save it as a replay case. Cases keep the captured payload, can include response assertions, and can be replayed individually or as suites.

Retention​

Captured requests are kept for your plan's request history period (1 day on Free, 14 to 90 days on paid plans) and then deleted automatically. On the Free plan an endpoint stores at most 50 requests; while it is full, new requests are rejected with HTTP 403 until older ones expire or you delete them. See Plans & Billing for details.