// DOCUMENTATION
Request Builder
Build requests from scratch or from documented operations and choose the right execution runner.
Build a request
Enter the HTTP method and URL, then add query parameters, headers, authentication and a body. Starting from documentation carries operation context into the editor.
- Keep secrets out of shareable examples.
- Use structured parameter rows for query and headers.
- Select the correct content type for the body.
Choose a runner
Cloud Runner executes through the REST Test backend and avoids browser CORS enforcement. Browser Runner executes from the current browser and is subject to the target API's CORS policy.
- Use Browser Runner when browser behavior matters.
- Use Cloud Runner for server-side reachability.
- Browser Runner does not bypass CORS.
Inspect the response
Review status, duration, size, headers and body together. A non-2xx response is still a valid HTTP result and should be inspected rather than treated as a transport failure.
HTTP/1.1 422 Unprocessable Content
content-type: application/json
{ "error": "amount must be positive" }