Request Body Inspector

Server assisted API Testing

Send POST/PUT requests to a capture URL and see the raw body, detected content type, parsed JSON/form fields and byte size — great for verifying what your app really transmits.

Privacy: This tool sends the request through the Mutqan backend relay to reach the target. Only the target URL, headers and body you enter are transmitted, and nothing is stored.

How to use Request Body Inspector

  1. Create a capture URL.
  2. Send the request from your application or with cURL.
  3. Select it — the Body tab shows the parsed and raw body side by side.

Request Body Inspector features

  • Captures POST/PUT/PATCH bodies exactly as sent: raw bytes, size and Content-Type
  • JSON pretty-printed and as a tree; form-urlencoded decoded to fields; XML shown as text
  • Body tab opens by default; truncation is flagged
  • Important fields and timestamps extracted from JSON bodies
  • Copy payload or cURL reproduction

Request Body Inspector example

Form submission

Input:

POST … Content-Type: application/x-www-form-urlencoded
name=Layla&plan=pro&agree=on

Output:

Form fields
{
  "name": "Layla",
  "plan": "pro",
  "agree": "on"
}
32 B · application/x-www-form-urlencoded

Frequently asked questions about Request Body Inspector

Which body types are decoded?

JSON is pretty-printed and shown as a tree, application/x-www-form-urlencoded is decoded into fields, XML is shown as text; everything is also available raw.

How large can the body be?

The relay stores bodies up to its limit (about 1 MB) and marks larger bodies as truncated.

Can I verify what my app really sends?

Yes — that is the point: compare the raw bytes, Content-Type and size with what your code intended to send.