Skip to main content

Build a request

Build a request when you want full control from scratch, or when you are editing a captured, generated, or imported call. Set the method, URL, headers, body, parameters, and assertions, then send it or include it in a flow.

GETPOSTPUTPATCHDELETEHEAD

How to build from scratchHow to build from scratch

1
Choose Request

In REST API testing, choose the request path to build manually from scratch.

2
Set method and URL

Pick GET, POST, PUT, PATCH, DELETE, or HEAD, then enter the full URL or path.

3
Add headers and parameters

Set Content-Type, Authorization, Accept, and any query parameters the endpoint needs.

4
Add a body when needed

For POST, PUT, and PATCH, add the JSON (or other) body. GET, DELETE, and HEAD often have no body.

5
Add assertions and send

Expect a status such as 200, 201, or 204. Send the request, or add it to a flow and run the sequence whenever you need.

Request fieldsRequest fields

Method
The HTTP verb. Match what the backend implements.
URL
The endpoint to call, including host or environment base URL.
Query params
Key-value pairs appended to the URL (filters, ids, paging).
Headers
Auth, content type, accept, and any custom headers.
Body
Payload for create and update calls. Leave empty when the method does not use one.
Assertions
Expected status (and related checks) so pass/fail is explicit.

Assertions and statusAssertions and status

A request without an expected status only tells you what the server returned. An assertion tells QAlity whether that result is success for your test.

  • Expect 200 for a successful GET, PUT, PATCH, or HEAD.
  • Expect 201 when POST should create a resource.
  • Expect 204 when DELETE should succeed with an empty body.
  • Expect 400 or 401 on purpose when you are testing invalid input or missing auth.

If the actual status does not match, the request fails. That failure is stored in Execution History with the method, path, and status so you can rerun after a fix. See status codes.

Edit captured or generated requestsEdit captured or generated requests

The same editor applies after recording, AI generation, or import:

Change it
Update method, URL, headers, body, or parameters.
Test it
Send the request and inspect the live response.
Make it yours
Keep the edited request in the flow and run the sequence on demand.
Send vs run the flow

Use Send to isolate one call. Run the full flow when order matters, for example add to cart before you place the order.

REST API Testing
What REST API testing is, status codes, and history.
Record from browser
Capture live traffic instead of authoring by hand.
Generate with AI
Draft requests from a prompt, then edit here.
Import cURL or JSON
Paste an existing request, then edit.
Import from file
Bring in many endpoints from a definition file.