A channel represents a delivery medium through which notifications reach end users. Every notification flows through at least one channel, and templates are linked to channels to define per-channel content.
What channel types are available?
The platform supports two channel types:
| Type | Description | Limit per app |
|---|
in_app | In-app notifications via CometChat | Unlimited |
push | Mobile push notifications | 1 |
The push channel type is limited to one channel per app. Attempting to create a second push channel returns an error.
How do channel limits work?
Each app (identified by appId) has limits on how many channels of each type can be created. The in_app type is unlimited, while push is capped at one. Other types require contacting sales for provisioning.
Use the channel availability endpoint to check current limits and usage for your app.
What is the enabled flag?
Channels have an enabled boolean property. When a channel is disabled:
- It still exists and retains its configuration
- Templates linked to it remain intact
- Notifications skip the disabled channel during delivery
This lets you temporarily pause a delivery medium without deleting the channel or unlinking templates.
What are templateType and config?
- templateType — Either
ui or data. Determines whether the channel delivers rich UI templates or raw data payloads.
- config — A flexible JSON object for channel-specific settings (e.g., push credentials, SMTP configuration).
The key field is auto-generated from the channel name and is immutable after creation. Use it as a stable identifier in integrations.
How do channels relate to templates?
Templates are linked to one or more channels at creation time. Each link creates a template-channel record where you define the per-channel content (subject lines for email, body text for SMS, etc.).
See the Templates and Template Channels documentation for details. 
