HTTP probe
The HTTP probe lets you send a fully configured HTTP request to any target and inspect the response. It supports all standard methods, custom headers, query parameters, cookies, and a request body.
[SCREENSHOT: HTTP probe editor — full view with URL bar, method, headers/params/body tabs, and Send button]
Configuration
Section titled “Configuration”| Field | Description |
|---|---|
| URL | Full target URL including scheme (http:// or https://) |
| Method | HTTP method: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS |
| Headers | Key-value pairs sent as request headers |
| Query parameters | Key-value pairs appended to the URL |
| Body | Request body (for POST/PUT/PATCH) |
| Cookies | Key-value pairs sent as Cookie header |
Variable substitution
Section titled “Variable substitution”All fields support {{variable}} placeholders resolved from the active environment:
URL: https://{{host}}/api/usersHeader: Authorization: Bearer {{token}}Body: {"email": "{{email}}"}Response
Section titled “Response”[SCREENSHOT: HTTP probe response panel — status code badge, headers tab, body tab with syntax-highlighted JSON]
The response panel shows:
- Status code with colour-coded badge
- Response time
- Response headers
- Response body with syntax highlighting (JSON, HTML, plain text)
- Copy to clipboard button for the response body
Assertions
Section titled “Assertions”Set an expected status code on the probe. If the actual response code differs, the history entry is marked as failed and highlighted with a warning indicator.
[SCREENSHOT: HTTP probe with failed assertion — red badge on history entry]
History
Section titled “History”[SCREENSHOT: HTTP probe history panel expanded — list of past sends with timestamps and status codes]
Each send is recorded. The history panel shows status codes and timestamps for quick scanning.