Delete a channel

DELETE/v1/channels/{channelId}

Project conversations cannot be deleted independently of their project (400). Requires active organization membership, threads:write and channel_manage. Soft-deletes the canonical channel conversation and revokes pending ownership offers. Conversation and associated agent history become inaccessible; queued mentions cannot start. Existing agent execution is not forcibly interrupted.

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
channelId	path	string	Yes	—

Query parameters

Name	Location	Type	Required	Description
revision	query	integer	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.

200Channel removedapplication/json

Field	Type	Required	Description
deleted	boolean	Yes	—
channelId	string	Yes	—

400Invalid input (400), unauthenticated (401), denied (403), unavailable resource (404), stale revision/idempotency conflict/archived channel (409), unavailable PostgreSQL backend (503), or failed operation (500).application/json

Field	Type	Required	Description
error	string	Yes	—
code	string	No	—
message	string	Yes	Message text.

401Invalid input (400), unauthenticated (401), denied (403), unavailable resource (404), stale revision/idempotency conflict/archived channel (409), unavailable PostgreSQL backend (503), or failed operation (500).application/json

Field	Type	Required	Description
error	string	Yes	—
code	string	No	—
message	string	Yes	Message text.

403Invalid input (400), unauthenticated (401), denied (403), unavailable resource (404), stale revision/idempotency conflict/archived channel (409), unavailable PostgreSQL backend (503), or failed operation (500).application/json

Field	Type	Required	Description
error	string	Yes	—
code	string	No	—
message	string	Yes	Message text.

404Invalid input (400), unauthenticated (401), denied (403), unavailable resource (404), stale revision/idempotency conflict/archived channel (409), unavailable PostgreSQL backend (503), or failed operation (500).application/json

Field	Type	Required	Description
error	string	Yes	—
code	string	No	—
message	string	Yes	Message text.

409Invalid input (400), unauthenticated (401), denied (403), unavailable resource (404), stale revision/idempotency conflict/archived channel (409), unavailable PostgreSQL backend (503), or failed operation (500).application/json

Field	Type	Required	Description
error	string	Yes	—
code	string	No	—
message	string	Yes	Message text.

500Invalid input (400), unauthenticated (401), denied (403), unavailable resource (404), stale revision/idempotency conflict/archived channel (409), unavailable PostgreSQL backend (503), or failed operation (500).application/json

Field	Type	Required	Description
error	string	Yes	—
code	string	No	—
message	string	Yes	Message text.

503Invalid input (400), unauthenticated (401), denied (403), unavailable resource (404), stale revision/idempotency conflict/archived channel (409), unavailable PostgreSQL backend (503), or failed operation (500).application/json

Field	Type	Required	Description
error	string	Yes	—
code	string	No	—
message	string	Yes	Message text.

Delete a channel

Response 200

See the ACP quickstart and SDK flow