Idempotently remove a personal favourite
DELETE
/v1/account/favorites/{resourceType}/{resourceId}Requires resources:write. Never deletes or mutates the target resource. Missing bookmarks also succeed, allowing removal after a resource is deleted or access is revoked.
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 |
|---|---|---|---|---|
| resourceType | path | string | Yes | — |
| resourceId | path | string | Yes | — |
Query parameters
None.
Header parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| X-Computer-Agents-Organization | header | 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.
200Favourite absentapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| removed | boolean | Yes | — |
400Invalid resource identity
None.
401Authentication required
None.
403Insufficient scope or inactive organization membership
None.
500Favourites storage failed
None.
Idempotently remove a personal favourite
Loading...
Response 200
Loading...