API requests, environments and Postman import (1.5.2)

Since 1.5.2 the API Testing tab has two inner tabs: Requests (saved requests, Postman-style) and Spec Tests (the scenarios generated from an OpenAPI spec). Both save into the same API suite.

BUILD A REQUEST
1. Mode > API Testing, open or create an API project and suite, then the Requests tab.
2. + New Request (or From Endpoint... to start from a discovered endpoint): method, URL, params, headers, auth (none, bearer, basic, API key, OAuth 2.0 client credentials) and body.
3. Checks: status equals or is 2xx; JSON path equals / contains / matches regex / exists; header equals or contains; body contains; response time under N ms; OpenAPI contract.
4. Capture: save a JSON path, a header or the status into a variable, and use it as ${name} in later requests. The usual chain is log in -> capture the token -> place an order with it -> capture the order id -> track it.
5. Send shows status, time and size with the Body, Headers and Checks views; Copy as cURL gives the same call for a terminal (secrets masked); History keeps the last 50 sends of the session.

ENVIRONMENTS AND SECRETS
- The selector in the API tab header picks the environment; Manage Environments... edits them. Each environment (dev, qe, uat, prod...) is a map of variables such as baseUrl, token or userId.
- Tick Secret on a value and it is stored encrypted for your Windows user and shown as ******** in logs, reports and cURL.
- The file is api-projects/<project>/environments.yaml, so it lives in your repo with the suite.

RUN AND SAVE
- Run Requests runs the suite's requests in order with a live row per request; Rerun failed repeats only the failures. Results appear in API Run History.
- Save Suite writes the suite as YAML (existing .json suites keep working).
- Command line: wsq api-suite-run --suite <file> [--env qe] [--json] runs the requests and the spec scenarios; an unknown environment exits 2 before anything is sent.

IMPORT FROM POSTMAN
- Import Postman Collection... (v2.1 JSON) brings requests, folders, headers, query, raw/JSON/urlencoded bodies, bearer/basic/apikey auth and collection variables; {{var}} becomes ${var}.
- Import Postman Environment... creates an environment. Pre-request and test scripts are listed as not imported.

Practice on the public API Lab (api.wsqdemo.com): log in, place an order with the captured bearer token, and track it on the public endpoint, exactly as in our API Tester video.

The public guide stays intentionally high level. Open the Intelligent Assistant for click-by-click instructions, learning order, and practice ideas.