Bearer authentication of the form Bearer <token>, where token is your auth token.
The ID of the WorkflowRun. This ID will start with “workflow_run”. This ID can be found in the API response when creating a Workflow Run, or in the “history” tab of a workflow on the Extend platform.
Example: "workflow_run_8k9m-xyzAB_Pqrst-Nvw4"
API version to use for the request. If you do not specify a version, you will either receive a 400 Bad Request or be set to a previous legacy version. See API Versioning for more details.
The workspace ID to target. Required when using an organization-scoped API key; optional for workspace-scoped keys (the key is already tied to a workspace). See Authentication for details on API key scopes.
A metadata object that can be assigned to a specific WorkflowRun. If metadata already exists on this WorkflowRun, the newly incoming metadata will be merged with the existing metadata, with the incoming metadata taking field precedence.
You can include any arbitrary key : value pairs in this object.
To categorize workflow runs for billing and usage tracking, include extend:usage_tags with an array of string values (e.g., {"extend:usage_tags": ["production", "team-eng", "customer-123"]}). Tags must contain only alphanumeric characters, hyphens, and underscores; any special characters will be automatically removed.