Skip to main content
GET
Before you can execute a case, you must know what inputs the workflow expects. This endpoint returns the workflow object: its name, status, and the full node/edge graph. The workflow’s input definitions live on the input node: look up nodes[workflowInputNodeId].input_schema.schema to get the variable names and types you need for the Execute Case payload. By default, the response describes the latest version of the workflow. To inspect a specific historical version, pass one of the three version selectors as a query parameter. When more than one selector is supplied, they resolve in this order of priority:
  1. workflowVersionId — the version UUID
  2. version — the semantic version, <MAJOR>.<MINOR>
  3. workflowVersionNumber — the sequential version number

Path Parameters

string
required
The unique identifier of the workflow to retrieve details for

Query Parameters

string
Specific workflow version UUID. Highest priority — takes precedence over version and workflowVersionNumber when more than one is supplied.
string
Semantic workflow version as <MAJOR>.<MINOR>, for example 2.1. A leading v is accepted and stripped (v2.1 is the same as 2.1).Both components must be integers, and the value is sent as a string — 1.10 and 1.1 are different versions.
number
Sequential workflow version number to retrieve. Lowest priority. Omit all three selectors to use the latest version.

Headers

string
required
Your API authentication key

Response

string
required
The workflow ID
string
The workflow version ID this object represents
number
required
The workflow version number this object represents
number
The latest version number of the workflow
string
required
Workflow name
string
Workflow description
string
Validity status of the workflow
string
Active status of the workflow
string
ID of the workflow input node — its entry in nodes carries the input schema for Execute Case
string
ID of the workflow output node — its entry in nodes defines the output variables returned by Get Case Results
string[]
required
IDs of the starting nodes
string[]
required
IDs of the ending nodes
object
required
The workflow nodes keyed by node ID. Node objects use snake_case keys — the input node’s input_schema.schema maps variable names to their definitions (type, display_name, type_definition, …).
object
required
The workflow edges keyed by edge ID
object
The organisational layer: named boxes grouping steps, each with an owner, duration estimate and review status. Keyed by section ID.Open object — the workflow model owns this shape and new fields appear without an API version bump, so read defensively.
object
The annotation layer: canvas notes keyed by note ID. Open object.
string
Design lifecycle stage. One of interview, generating, rewire, or build.Workflows created before the design flow, and all non-Discovery creations, read as build.
object
The Discovery approver who owns the design flow, as {id, name, imgSrc}. null outside the design flow.
string
ISO timestamp of the workflow’s most recent execution. null if never run.

Errors

Bad Request
version is not in <MAJOR>.<MINOR> (or v<MAJOR>.<MINOR>) form, or a selector is otherwise malformed.
Unauthorized
Missing, invalid, or expired API key.
Not Found
The workflow does not exist, or it has no version matching the selector.

Supported Data Types

Variables in nodes[*].input_schema and nodes[*].output_schema use the Opus type system. For the full list of types, nested type_definition shapes and date formats, see Variable Schemas.