Skip to main content
POST
Execute Workflow
Records a run against a registered MAIP workflow. Supply trigger_agent_id, with optional input_payload and metadata. The current handler creates a run with status running and returns HTTP 201. This MAIP tracking route does not itself launch a Temporal workflow. Do not interpret the initial status as proof that workflow steps executed. Generated workflow receipts currently use system markers rather than cryptographic signatures. Use the generated parameter fields above for the request contract. Authenticate with a credential for the target workspace and environment; do not supply a tenant-selection header.

Authorizations

X-API-Key
string
header
required

API key for machine-to-machine authentication

Path Parameters

workflowId
string<uuid>
required

Workflow identifier

Body

application/json
trigger_agent_id
string
required
input_payload
any
metadata
any

Response

Workflow execution started

execution_id
string<uuid>
workflow_id
string<uuid>
status
enum<string>
Available options:
pending,
running,
completed,
failed
steps
object[]
created_at
string<date-time>