Mastering API Automation with Apifox: From Parameter Passing to Batch Testing

Introduction

Compared with UI testing, API interfaces change less frequently after development, making automation cost‑effective for regression testing before each release. Manual API testing requires testers to fill data and parameters by hand, so the goal is to automate test cases while handling interface dependencies, token expiration, data coverage, and batch validation.

1. Interface Parameter Passing

A common scenario is that a query API needs an access_token obtained from an authentication API. The token must be extracted from the auth response and passed to the subsequent request. The solution is to extract the needed value, store it as a global variable, and reference it in the next interface.

Steps in Apifox:

In the interface tab, open the Post‑action section and select Extract Variable .

Enter the variable name, type, and a JSONPath expression (e.g., $.access_token) to capture the target field.

The extracted value appears in the environment variable list and can be referenced in subsequent requests.

2. External Data Sources

When an API requires multiple sets of POST data, manually editing parameters is inefficient. Apifox supports two approaches:

For a small number of data rows, create a test data set directly in the UI.

For large data volumes, import a CSV file and map columns to request parameters.

Test data can be loaded as global variables or via the Test Data switch in the test case editor.

Each row in the CSV represents one execution of the test case; the column names become parameter names, and values are injected sequentially.

3. Test Assertions

Automation requires programmatic validation of responses. Apifox provides an assertion panel (Interface → Run → Post‑action → Assertions) that can validate JSON, HTML, XML, headers, and cookies.

Typical assertion steps:

Select the response element using a JSONPath expression.

Define the expected value or range.

Optionally write a custom script for complex logic.

Results appear directly in the response tab for single‑interface tests or in the test result list for batch runs.

4. Environment Switching

After testing on a staging environment, the same test suite can be run against production by configuring a base URL (protocol and domain) in the environment settings. All interface paths remain unchanged.

Switch the active environment in the Run Environment dropdown before execution.

5. Batch Testing and Test Suite Organization

Apifox organizes tests as Test Cases → Test Case Groups → Test Suites . A test case can contain multiple steps, each representing an interface request. Cases can be dragged to reorder steps.

Running a suite executes all included cases, producing a consolidated report that can be exported as HTML.

Conclusion

The article demonstrates a practical workflow for API automation using Apifox, emphasizing parameter extraction, data‑driven testing, assertions, environment management, and scalable test suite organization, enabling testers—especially those less familiar with scripting—to quickly build reliable automated API tests.