Update task activity subscription
PUT
/v1/tasks/{taskId}/activity-subscriptionIdempotently subscribe or unsubscribe the authenticated user from activity notifications for the task.
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 |
|---|---|---|---|---|
| taskId | path | string | Yes | Task ID |
Query parameters
None.
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| subscribed | boolean | Yes | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Task activity subscription updatedapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| taskId | string | Yes | — |
| subscribed | boolean | Yes | — |
| subscription | object | No | — |
| subscription.taskId | string | No | — |
| subscription.userId | string | No | User ID. |
| subscription.organizationId | string | No | — |
| subscription.subscribed | boolean | No | — |
| subscription.createdAt | string | No | ISO 8601 timestamp. |
| subscription.updatedAt | string | No | ISO 8601 timestamp. |
400Invalid subscription state
None.
404Task not found
None.
Update task activity subscription
Loading...
Response 200
Loading...