List eligible Metronome owners
GET
/v1/metronomes/{metronomeId}/owner-candidatesLists active members of the Metronome workflow organization that may become the workflow owner.
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 |
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.
200Eligible Metronome owner listapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| object | list | No | — |
| data | object[] | No | — |
| data[].userId | string | Yes | User ID. |
| data[].name | string | Yes | Human-readable name. |
| data[].email | string | Yes | — |
| data[].avatarUrl | string | Yes | — |
| total_count | integer | No | — |
| has_more | boolean | No | — |
403Only the current workflow owner may list transfer candidates
None.
404Metronome not found
None.