Create or send data via API during your automated test
API interactions are an important part of many modern applications. Sometimes your automated tests need to send data to a backend service, create a resource, or trigger a process that cannot (or should not) be handled purely through the UI. The Integration API POST step allows your test to perform an HTTP POST request to a given API endpoint, submitting data and integrating backend behaviour directly into your automation flow.
Using this step makes your automation capable of not only validating frontend behaviour but also interacting with backend systems, setting up test state, and verifying outcomes that depend on server-side logic.
Why POST requests matter in tests
POST requests are used to create resources or trigger actions on a server. Typical use cases include:
Creating a user
Submitting form data
Uploading data or triggers
Initiating processes
Starting workflows that backend services manage
Rather than navigating through multiple UI screens to create this state, your test can call an API directly with precise data. This results in faster, cleaner, and more reliable automation.
How the step works
With Integration API POST, your automated test:
Defines the full endpoint or relative API path
Includes required headers (for example authentication or content type)
Provides a JSON body or payload of data
Sends the POST request to the target service
Optionally asserts on the response to confirm success
Continues the test based on the response
Because POST is idempotent only in how it creates new data, using it inside your flow allows you to set up fresh test scenarios without manual external setup.
Typical scenarios where POST is useful
The Integration API POST step is often used for:
Creating test users
Submitting simulated orders
Kicking off backend processes
Posting messages to chained services
Triggering event pipelines
Defining test state for the next steps
For example, you might POST an order object to your backend, then run UI checks to ensure that order is reflected correctly in the application interface.
Combine with data and stored values
DoesQA’s value store makes API POST requests even more powerful. You can:
Use dynamic values generated earlier in your flow (like timestamps, tokens, or identifiers)
Pull values from previous requests
Store response fields and reuse them later
Drive downstream steps based on returned data
For example:
After creating an order via POST, store the order ID
Use the stored ID to navigate to a detail page
Assert that the order appears correctly
Continue with additional validations
This integration makes your automation context aware and stateful.
Verify backend impact and UI outcome
After performing a POST request, you can:
Assert on the backend response (status, fields, values)
Navigate the UI to the resource you just created
Check that UI elements reflect the new state
Validate that workflows behave consistently
This gives you full confidence that server APIs and frontend behaviour are aligned.
Improve reliability and maintainability
Relying solely on UI to create test data can be brittle, flaky, and slow. Using API POST requests inside your test:
Speeds up setup
Reduces flaky navigation
Makes tests more readable
Avoids repetitive UI interaction
Provides backend validation
This results in smoother automation that covers real world behaviour both at the front and back end.
Embedding POST requests into your flows ensures your automation can handle real use cases requiring remote creation logic, giving you deeper and more reliable coverage.