unlinkProjectResource
DELETE /api/v1/projects/{projectId}/resources/{linkId}
Optional durable initiative. Requires a current registered Agent/account grant bound to the owning workspace; original linked Resource authorization is independent. Managers configure lifecycle/participants through the authenticated browser. Archived Projects reject ordinary edits. Retry receipts and minimal Activity facts commit atomically; detach never deletes the linked Resource. Pagination cursors are opaque and actor/query-bound. Future adapters and unvalidated revision pins fail explicitly.
Access
Section titled “Access”Use a credential with commentary.projects.write.
Provider access, workspace membership, and agent grants are enforced separately. A token does not expand access to a repository or resource. Set up developer access.
Parameters
Section titled “Parameters”| Name | Location | Type | Required | Description |
|---|---|---|---|---|
projectId |
path | string | Yes | |
linkId |
path | string | Yes | |
If-Match |
header | string | Yes | |
Idempotency-Key |
header | string | Yes |
Request body
Section titled “Request body”Optional. Supported content types: application/json.
| Field | Type | Required | Description |
|---|
Call the endpoint
Section titled “Call the endpoint”Replace path placeholders and your credential. For body operations, create request.json using the required fields above; this command does not invent resource identifiers or consent.
curl --request DELETE \ 'https://commentary.dev/api/v1/projects/<projectId>/resources/<linkId>' \ --header 'Authorization: Bearer <your-token>' \ --header 'Content-Type: application/json' \ --data-binary @request.jsonResponses
Section titled “Responses”| Status | Meaning | Payload |
|---|---|---|
200 |
Authorized domain result with the exact applicable ETag. | ProjectAgentunlinkProjectResourceOutput |
400 |
Bounded v1 machine-readable failure. | object |
401 |
Bounded v1 machine-readable failure. | object |
403 |
Bounded v1 machine-readable failure. | object |
404 |
Bounded v1 machine-readable failure. | object |
409 |
Bounded v1 machine-readable failure. | object |
412 |
Bounded v1 machine-readable failure. | object |
413 |
Bounded v1 machine-readable failure. | object |
422 |
Bounded v1 machine-readable failure. | object |
428 |
Bounded v1 machine-readable failure. | object |
429 |
Bounded v1 machine-readable failure. | object |
500 |
Bounded v1 machine-readable failure. | object |
503 |
Bounded v1 machine-readable failure. | object |
Successful response fields
Section titled “Successful response fields”| Field | Type | Required | Description |
|---|---|---|---|
data |
object | Yes | |
idempotencyReplayed |
boolean | No |
Recover from errors
Section titled “Recover from errors”Use the returned status and error body. Correct invalid fields before retrying; reconnect or narrow the target for authentication and permission errors. For conditional writes, reload the latest version before preparing a new request. Respect rate-limit headers and retry only when the operation’s idempotency contract permits it.
Contract and related guidance
Section titled “Contract and related guidance”Operation ID: unlinkProjectResource. Download the OpenAPI contract for complete constraints and code generation. Browse endpoints.