Reference

Supported HTTP Methods & Payloads

Check supported capture methods, raw payload formats and HTTP status meanings. Understand HEAD, framework OPTIONS, rejected TRACE and binary body handling.

On this page

HTTP methods

The following methods are verified against the application. A deployment proxy or sender may impose additional restrictions.

Method	Behavior
`GET`	Captured.
`HEAD`	Captured; wire response body is empty.
`POST`	Captured.
`PUT`	Captured.
`PATCH`	Captured.
`DELETE`	Captured.
`OPTIONS`	Framework response: HTTP 200 with Allow; not captured.
`TRACE`	Rejected with HTTP 405; not captured.

CONNECT and custom methods are not established capture workflows. Browser preflight is different from server-to-server delivery.

Payload formats

In a Bash-compatible shell with cURL installed, set WEBHOOK_URL to the receiving URL copied from your endpoint. Replace <YOUR_RECEIVING_URL> including the angle brackets, without a trailing slash; keep the single quotes. Reuse that variable for the examples on this page.

Use the Quickstart variable setup and JSON POST. Invalid JSON is also accepted within the body limit; there is no schema validation.

After setting WEBHOOK_URL, send any of these synthetic payloads. The inspector preserves raw bytes; it does not validate JSON schemas or verify webhook signatures.

Plain text

Bash / cURL

curl --include "${WEBHOOK_URL}/notes" \
  --header 'Content-Type: text/plain' \
  --data 'Synthetic delivery test'

URL-encoded form

Bash / cURL

curl --include "${WEBHOOK_URL}/forms" \
  --data-urlencode 'event=order.created' \
  --data-urlencode 'note=synthetic test'

Multipart form

Bash / cURL

curl --include "${WEBHOOK_URL}/uploads" \
  --form 'note=synthetic test'

Multipart content is captured as raw bytes, including boundaries. File-part extraction is not provided.

Binary and raw bytes

Create a local synthetic file named sample.bin before running this example; it sends the file’s exact bytes. Keep it below the current body limit.

Bash / cURL

curl --include "${WEBHOOK_URL}/binary" \
  --header 'Content-Type: application/octet-stream' \
  --data-binary @sample.bin

Non-UTF-8 bodies display as base64 when decoding fails. Original bytes are available as bodyBase64 in request data and downloads, including for text captures. Multipart is raw content, not an extracted attachment collection. No automatic signature validation is performed.

HTTP responses

Status	Interpretation
200	Default successful capture; empty response body.
404	Unknown or removed endpoint.
410	Expired or disabled endpoint.
413	Ingestion body too large; not captured.
429	Temporary restriction when admission controls apply.
5xx	Service failure; inspect history before retrying.

A configured response can intentionally return these same codes. Check configuration and history before interpreting a status as ingestion failure. Follow Retry-After only when supplied. HEAD and 204/304 omit response bodies.

A saved custom 4xx or 5xx response can accompany a successful capture. If a sender reports a timeout or service error, check history before resending: persistence may already have succeeded and a resend can create a duplicate.