List hierarchical activity groups
GET
/v1/threads/{threadId}/activity-groupsHow 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 |
|---|---|---|---|---|
| threadId | path | string | Yes | Thread ID |
Query parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| runId | query | string | No | — |
| status | query | pending | active | completed | failed | superseded | No | — |
| after | query | integer | No | Return groups whose start sequence is greater than this cursor. |
| before | query | integer | No | Return the newest groups whose start sequence is lower than this history cursor. |
| cursor | query | integer | No | Backward-compatible alias for `before`. |
| limit | query | integer | 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.
200Observer-maintained activity groupsapplication/json
None.
List hierarchical activity groups
Loading...
Response 200
Loading...