Skip to main content

Import from file

Import from file when you already have API definitions and want those endpoints in QAlity as runnable tests. This is the File path in REST API testing: bring in the contract, then inspect, assert, and run, without browsing the app first.

For a single copied command, use Import cURL or JSON instead.

Pro and Business only

API import from definition files is available on Pro and Business. It is not included on Discover. See Pro plan and Business plan.

How to import a definition fileHow to import a definition file

1
Choose File

In REST API testing, choose the file path to import API definitions.

2
Select the definition file

Upload the file that lists your endpoints. QAlity reads the operations into requests in the workspace.

3
Review imported endpoints

Check methods and paths. Keep the calls you will test; ignore ones that are not part of this flow.

4
Fill in runtime details

Add environment URLs, auth headers, and realistic bodies. Definitions often omit the values a live test needs.

5
Assert and run

Set expected status codes, then send a request or run the flow whenever you need. Each run is stored in Execution History.

After importAfter import

Imported definitions describe what the API can do. Tests still need expected results.

Select
Keep the endpoints that match the journey (checkout, login, profile). Drop unused operations.
Edit
Set URL, headers, query, and body. See Build a request.
Status
Assert 200, 201, 204, or an expected error code. See status codes.
History
Run on demand. Compare the latest status with earlier runs in Execution History.
Pair file import with recording

A definition file lists every endpoint. Recording shows which of those endpoints the product actually calls. Use both when you want contract coverage plus real traffic.