Create Channel

POST /channels

A provisioning failure yields a channel that exists and is inactive, with the reason on the response — never a silently non-functional one (annex 11 §5.6).

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Request body — ChannelCreate

Field	Type		Notes
type_name	string	required	min length 1 max length 60
agent_id	string (uuid)	required	—
persona_id	string (uuid) | null	optional	—
slug	string	required	—
config	object	optional	—
coalescing	object	optional	—
is_active	boolean	optional	Default true.

Responses

Status	Description	Body
201	Successful Response	ChannelView
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/channels \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "type_name": "string",
       "agent_id": "0190a2f4-0000-7000-8000-000000000000",
       "slug": "string"
     }'

Response — ChannelView

Field	Type		Notes
id	string (uuid)	required	—
workspace_id	string (uuid)	required	—
type_name	string	required	—
agent_id	string (uuid)	required	—
persona_id	string (uuid) | null	required, nullable	—
slug	string	required	—
config	object	required	—
coalescing	object	required	—
is_active	boolean	required	—
provision_error	string | null	optional	—
inbound_url	string | null	optional	—
created_at	string (date-time)	required	—
updated_at	string (date-time)	required	—