Diff Metronome versions

GET/v1/metronomes/{metronomeId}/versions/{versionId}/diff

Compare a workflow version against another saved version and return added, removed, and changed node and edge IDs.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
metronomeIdpathstringYesMetronome workflow ID
versionIdpathstringYesMetronome workflow version ID
Query parameters
NameLocationTypeRequiredDescription
againstVersionIdquerystringYes

Body schema

This endpoint does not require a request body.

None.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Metronome version diffapplication/json
FieldTypeRequiredDescription
dataobjectNo
data.metronomeIdstringNo
data.baseVersionIdstringNo
data.baseVersionNumberintegerNo
data.targetVersionIdstringNo
data.targetVersionNumberintegerNo
data.nodesobjectNo
data.nodes.addedstring[]No
data.nodes.removedstring[]No
data.nodes.changedstring[]No
data.nodes.addedCountintegerNo
data.nodes.removedCountintegerNo
data.nodes.changedCountintegerNo
data.edgesobjectNo
data.edges.addedstring[]No
data.edges.removedstring[]No
data.edges.changedstring[]No
data.edges.addedCountintegerNo
data.edges.removedCountintegerNo
data.edges.changedCountintegerNo
data.summaryobjectNo
data.summary.addedintegerNo
data.summary.removedintegerNo
data.summary.changedintegerNo
data.summary.unchangedbooleanNo
404Metronome or version not found
None.
Diff Metronome versions
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow