Revoke and remove one person's access from a resource
DELETE
/v1/resource-invitations/resources/{resourceType}/{resourceId}/people/{personId}Requires resource access-management authority and the resource service write scope. Revokes accepted grants and pending offers immediately, retaining audit records. Other independent grants remain unchanged.
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 | skill | channel | resource_package | project | environment | agent | prompt | knowledge_library | database | server | security_repository | guardrail | evaluation | fine_tuning | test_plan | assurance_policy | metronome_workflow | batch_job | inference_endpoint | Yes | — |
| resourceId | path | string | Yes | — |
| personId | path | string | Yes | Personal access entry ID |
Query parameters
None.
Header parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| X-Computer-Agents-Organization | header | string | Yes | — |
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.
204Personal grant or offer revoked
None.
400Invalid resource type or organization header
None.
401Authentication required
None.
403Resource access-management permission required
None.
404Resource or personal entry unavailable in this organization
None.
409Project conversations inherit access from their parent project
None.
503PostgreSQL required
None.
Revoke and remove one person's access from a resource
Loading...
Response 204
Loading...