API test data
Keep the remaining fields valid so a failed request can be traced to the rule under test.
Generate request data →- No account or installation
- Copy or download results
- Documents processed in your browser
File sizes and generation counts have limits. Check the limits shown in each tool.
Example specification
A registration request has an email field and an age field. Both are required. Neither accepts null. Age is an integer from 18 to 65 inclusive. We will use synthetic values only.
{"email":"qa@example.test","age":25}Follow these steps
- Open the tools and choose API test data.
- Use email = qa@example.test and age = 25 as baselines. Set the age range to 18–65 and the step to 1.
- Select Change one field at a time and generate requests.
- Filter Negative and open a result. A missing email must leave age unchanged.
- Review the expected outcome and export selected rows.
Read the results
| Request | What it tests |
|---|---|
{"age":25} | Missing required email |
{"email":null,"age":25} | Present email with a null value |
{"email":"qa@example.test","age":"25"} | String instead of a numeric age |
Missing and null are not interchangeable. Whether "25" is converted to a number depends on the API specification. Do not assume a specific error code or message unless documented.
Common mistake
Changing every field to an invalid value at once obscures the cause of failure. Start with isolated errors; then use combinations if error precedence is itself a test requirement. JSON export contains request bodies only. CSV and Excel include expected outcomes.