Skip to main content
The Automation Dry Run Results API retrieves and manages the per-profile results produced when an automation is triggered in dry run mode. See Reactions for a conceptual overview of automations and how they execute.

​
What is a dry run

When you trigger an automation with dry_run: true, Omneo simulates the automation’s actions for the requested date range without creating production records or firing events. For each profile the query matches, Omneo stores a dry run result recording what the automation would have done. Use dry runs to verify automation logic before enabling it in production, or to understand what a past automation run would have produced.

​
Triggering a dry run

Send POST /v3/automations/{automation}/trigger with dry_run: true in the request body. Optionally include start_date and end_date to simulate over a range of days. The endpoint returns 202 Accepted. Results are written asynchronously. Query this API to retrieve them once processing is complete.

​
Dry run result attributes

​
Filtering results

The index endpoint accepts the following filters:

​
Cleaning up

Delete results individually once reviewed. The delete-reactions scope is required. There is no bulk delete endpoint.

​
Required scopes