Notifications
Notifications use pre-approved templates to send one-way messages to users.
Before sending a notification, make sure that:
Webhooks are configured to receive delivery events.
The template you are using has been approved.
You have a valid orgId and API token.
If webhooks are not configured, delivery results and user events will not be captured.
Send Notification
Use this endpoint to send a WhatsApp template message to a single recipient.
POST https://www.channel360.co.za/v1.1/org/{{orgId}}/notification
Headers
Content-type
applications/json
Authorization
Bearer <token>
Body
orgId
stringrequired
Organization ID (path parameter)
destination
stringrequired
Recipient phone number
message
objectrequired
Message payload (template-based)
message.type
stringrequired
Must be set to template
message.template
objectrequired
Template message definition
message.template.name
stringrequired
The name of the template.
message.template.language
objectrequired
An object specifying the language for the template with the following properties:
message.template.language.policy
stringrequired
Set to "deterministic" to define the language policy.
message.template.language.code
stringrequired
Language code (e.g. en_US)
message.template.components
array
An array of message components. You can define message components within this array.
Examples of templates and notifications
Example 1: Notification sent using a basic text template.
Example 2: Notification sent using a template with header tag, body tag, footer text, and button tag.
Example 3: Notification sent using an Afrikaans template.
What happens after sending?
When you send a notification, the API responds with a notificationId.
Receiving a notificationId only confirms that the request was sent.
It does not mean the message was delivered to the user.
Authentication Templates
For authentication message templates, the components array contains dynamic placeholders that must be populated with a unique {{AUTH_CODE}} at runtime. These placeholders ensure secure and personalised message delivery.
The {{AUTH_CODE}} should be inserted into the
parameterssection dynamically before sending.The same {{AUTH_CODE}} should be used across all relevant components (e.g., body text and buttons).
Override API
This feature is not fully supported and comes with risk, use your own discretion.
Message overrides (also referred to as passthrough) are a way to access newer META features that are not yet fully supported by C360.
To use the override feature, you need to include an "override" object that will contain your usual payload fields instead of the message object. Here is an example:
Last updated
Was this helpful?