Get Metronome run
GET
/v1/metronomes/{metronomeId}/runs/{runId}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
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| metronomeId | path | string | Yes | Metronome workflow ID |
| runId | path | string | Yes | — |
Query parameters
None.
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 run detailsapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| data | object | No | — |
| data.id | string | No | Unique identifier. |
| data.metronomeId | string | No | — |
| data.userId | string | No | User ID. |
| data.triggerType | string | No | — |
| data.status | queued | running | waiting_approval | completed | failed | cancelled | No | Current lifecycle status. |
| data.input | object | No | — |
| data.output | object | No | — |
| data.error | string | No | — |
| data.startedAt | string | No | ISO 8601 timestamp. |
| data.completedAt | string | No | ISO 8601 timestamp. |
| data.createdAt | string | No | ISO 8601 timestamp. |
| data.updatedAt | string | No | ISO 8601 timestamp. |