List account Metronome audit events
GET
/v1/metronomes/audit-eventsInspect publish, version, run, attachment, and lifecycle events across Metronome workflows.
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
None.
Query parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| limit | query | integer | No | — |
| metronomeId | query | string | No | — |
| action | query | string | No | — |
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 audit event listapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| object | string | No | — |
| data | object[] | No | — |
| data[].id | string | No | Unique identifier. |
| data[].metronomeId | string | No | — |
| data[].userId | string | No | User ID. |
| data[].actorUserId | string | No | — |
| data[].runId | string | No | — |
| data[].versionId | string | No | — |
| data[].action | string | No | — |
| data[].payload | object | No | — |
| data[].createdAt | string | No | ISO 8601 timestamp. |
List account Metronome audit events
Loading...
Response 200
Loading...