Using the Channel360 V1.1 API
Get started with using Channel360's V1.1 API
The Channel360 V1.1 API enables you to send notifications, manage templates, and receive feedback from user interactions.
When you send a notification, the API confirms that the request was received by returning a notification ID. Notification delivery results and user responses are provided separately through webhooks.
To track what happens after a notification is sent such as message delivery, failures, replies or read statuses webhooks must be configured. Webhooks allow Channel360 to send information about these events to your system.
Do not send notifications before configuring webhooks. Channel360 delivers message delivery results, failures, replies, and read statuses exclusively via webhooks. If webhooks are not configured, these events will be lost.
Getting Access to the API
Before using the Channel360 API, you must have access to an organisation in Channel360. This is managed through the Channel360 frontend.
To get started:
Sign up on the Channel360 frontend.
Wait for the Channel360 sales or support team to assign your account to an organisation.
Once assigned, sign in to Channel360.
Navigate to Settings navigation tab.
Under the Developer tab, select + Request Key to generate an API token.

Copy and securely store your API token.
Note: Most functionality in Channel360 can be completed directly through the frontend. The API is optional and is primarily intended for automation or building custom frontends.
In conclusion:
Templates define the structure of messages
Notifications trigger message delivery and return a notification ID
Webhooks provide delivery updates and user feedback
This guide walks you through the core concepts and API endpoints required to send notifications and receive feedback reliably using Channel360.
Last updated
Was this helpful?