Factuarea APIDevelopers

Dry-run an automation rule

Simulate what a rule would do against a sample event: condition match and what each action would resolve to.

Executes nothing. - No email, change, quota use or run record; it takes the read scope. - For document rules pass event_aggregate_id of a real document, or no step would run. - An unevaluable condition returns 200 with condition_error.

POST
/companies/{company}/automations/rules/{rule}/dry-run

Authorization

AuthorizationBearer <token>

Your API key as a bearer token: fact_live_… in production, fact_test_… in sandbox. See the authentication guide.

In: header

Path Parameters

company*string

Public identifier (UUID v7) of the company. Get it from GET /v1/me (data.scope[].id).

Formatuuid
rule*string

Public identifier (UUID v7) of the automation rule.

Formatuuid

Headers

Factuarea-Version?string

Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.

Formatdate

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json