Skip to main content

Record from browser

Recording captures the APIs your web app fires while you browse. Enter a URL, start recording, walk through the product in real time, then review each request with its method and status. You do not build a collection first.

This is the fastest way to turn real user actions into API tests. For the full picture, including status codes, running on demand, and Execution History, start with REST API Testing.

1Enter URL
2Record & browse
3Review APIs
4Send or save

How to record live trafficHow to record live traffic

1
Start recording

Open REST API testing and hit record. QAlity asks for the application URL where the journey begins.

2
Enter your app URL

Type the URL and continue. Your actual product opens in a live browser, ready to explore.

3
Browse like a user

Click, type, add to cart, or check out. Whatever the journey is, every click, input, and interaction is captured in the background as API requests.

4
Watch traffic arrive

Requests appear as they fire, including duplicates, repeats, and noise. Each row shows method, path, and status code.

5
Stop recording

Stop the recorder when the journey is done. Every API from the session is listed in one dashboard.

6
Clean up with AI

Use AI suggestions to remove duplicates, ignore noise, or keep specific requests before you save or run the flow.

Real traffic can be messy

Analytics, polling, and retries often sit next to the calls you care about. Clean those up before you add assertions so the saved test stays focused.

What you see for each requestWhat you see for each request

Captured traffic is listed with method, URL, status, and time. Open a row to inspect the details:

Method
GET, POST, PUT, PATCH, DELETE, or HEAD.
URL / path
Full request URL and the path (for example /api/orders).
Status
The HTTP status returned while you browsed (200, 201, 204, 401, 500, and so on).
Request
Query parameters, headers, and body.
Response
Status, timing, headers, and body from the live call.
Send
Replay that one request immediately without rerunning the whole session.

After you stopAfter you stop

Review
Confirm the captured calls match the journey you just walked.
Clean
Drop duplicates and noise. Keep the requests that prove the backend path.
Edit
Change headers, body, or parameters, then add assertions. See Build a request.
Run
Send one call or run the full sequence. Results go to Execution History so you can rerun later. See REST API Testing.

Recording is one of five ways to add APIs. If you already have a cURL, JSON, or definition file, you do not need to browse first.

REST API Testing
What REST API testing is, status codes, and history.
Generate with AI
Create API requests from a prompt.
Build a request
Author a request from scratch.
Import cURL or JSON
Paste existing requests into QAlity.
Import from file
Bring in API definition files.
UI Recorder
Capture clicks and inputs instead of network calls.