API testing in a Flow
Call GET, POST, PUT, PATCH, or DELETE in the same Flow as your browser steps. Store JSON as Values and assert what comes back.
API calls belong in the same Flow as your UI journey. Seed data, fetch a token, assert backend state, or clean up after checkout, without leaving DoesQA.
Use Integration steps such as GET and POST. Point them at a full URL or a Value that expands per environment. Store response fields as Values, then assert JSON in the next steps.
That keeps browser and API coverage in one place. Reviewers see one Flow. Schedules and CI run one pack. Failures show the API and UI context together.
Start from a login-token pattern or any endpoint your product already exposes. Expand from there the same way you expand any other path.