> For the complete documentation index, see [llms.txt](https://docs.channel360.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.channel360.co.za/api-usage/using-the-channel360-v1.1-api.md).

# Using the Channel360 V1.1 API 

Get started with using Channel360's V1.1 API

{% hint style="info" %}
Here is a link to our official [Postman Collection](https://www.postman.com/satellite-geoscientist-80349849-7234340/c360-workspace)
{% endhint %}

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.

{% hint style="warning" %}
**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.
{% endhint %}

### Getting Access to the API

{% hint style="info" %}
Before using the Channel360 API, you must have access to an organisation in Channel360.\
This is managed through the **Channel360 frontend**.
{% endhint %}

To get started:

1. Sign up on the **Channel360 frontend**.
2. Wait for the Channel360 sales or support team to assign your account to an organisation.
3. Once assigned, sign in to Channel360.
4. Navigate to **Settings** navigation tab.
5. Under the **Developer** tab, select **+ Request Key** to generate an API token.

<figure><img src="https://685637647-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP4Um8QSERfruL8OrCzQm%2Fuploads%2FiW8i68BolYPpSXlLRhj8%2Fimage.png?alt=media&amp;token=e8976239-6cce-4680-8841-b0d0e01e861e" alt=""><figcaption></figcaption></figure>

6. Copy and securely store your API token.

{% hint style="warning" %}
**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.
{% endhint %}

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.