How to use HTTP Request Inspector
- Create a capture URL.
- Send a request from the client you are debugging (or open the URL in a browser tab).
- Select the request; the raw view shows the full message, other tabs break it down.
- Compare with what your code intended to send.
HTTP Request Inspector features
- See requests exactly as the server receives them: method, path, query, headers, body, client IP
- Raw HTTP message view opens by default; JSON and form bodies decoded on demand
- Works with any client — mobile SDKs, scripts, proxies, browsers, IoT devices
- Open the URL in a new tab to see what your browser sends
- Copy headers, payload or a cURL reproduction
HTTP Request Inspector example
Mobile SDK request
Input:
App → PUT https://www.mutqansoft.sa/api/v1/webhooks/in/…/v1/devices/42?locale=arOutput:
PUT /v1/devices/42?locale=ar HTTP/1.1
user-agent: MyApp/3.2.1 (Android 14)
content-type: application/json
x-app-token: ••••
{"pushToken":"…","timezone":"Asia/Riyadh"}Frequently asked questions about HTTP Request Inspector
What is this for?
Point any HTTP client (mobile SDK, script, proxy, IoT device) at the URL and see exactly what arrives at a server: method, path, query, headers, body, IP — the raw HTTP view shows it as one message.
Can I open the URL in a browser?
Yes, "Open in new tab" performs a GET from your browser so you can see what a browser sends by default.
Is anything stored permanently?
Captured requests live only until the endpoint expires (24 h) or you delete it, and are never shared with anyone else.
Which HTTP methods and body sizes does the capture URL accept?
Any method — GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS — on the URL or any sub-path, with CORS enabled so browser fetch() works. Bodies are kept up to 256 KB (larger ones are truncated and flagged), each endpoint retains its latest 200 requests at up to 60 per minute, and every call receives a 200 JSON acknowledgement.