Teklink customers using ChatServ SMS Platform can send outbound SMS by calling the messaging API. Teklink will provide:
API Token (Bearer token)
Channel ID (the ChatServ channel / number that sends the message)
This KB covers API sending only (no Kazoo webhook/callflow content).
Use Teklink’s base URL:
Base URL: https://sms.theteklink.com
Method: POST
Path: /api/v1/channels/{CHANNEL_ID}/messages
CHANNEL_ID = the telephone number's backend channel ID that is sending the message.
Use a Bearer token (preferred):
Headers
Authorization: Bearer <token>
Content-Type: application/json
Accept: application/json
Alternative auth (not preferred):
If you are not using the Bearer header, the request body can include api_token (required in that case).
You must include either:
template_id, or
message_text
You must also provide the destination:
to_telephone_number (A 10 digit SMS enabled phone number)
new_conversation_state: "open" or "closed" (default is "open")
from_name: sender name shown in the portal (default "Automated Message")
duplicate_send_reject_timeout_minutes: prevents repeated automated sends to the same recipient within a time window (0 = continuous auto replies)
force_send: force send regardless of existing delay
send_delay_seconds: delay send (seconds)
curl --location 'https://sms.theteklink.com/api/v1/channels/{CHANNEL_ID}/messages' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <token>' \
--data '{
"to_telephone_number": "2125551212",
"template_id": "1e3fa777-17bf-4400-ba80-81e6ba524734",
"new_conversation_state": "closed"
}'Typical response:
{
"success": true,
"message": "Message sent",
"data": []
}
Expected status code for a successful send:
201
ChatServ supports webhooks for inbound SMS (so your system can receive messages in real time). To enable this:
Customer provides Teklink with the public HTTPS webhook URL to receive inbound events.
Teklink configures the webhook on the customer’s tenant/channel(s).
Customer validates they can receive and process inbound payloads, and returns HTTP 2xx quickly (best practice).
If you want inbound webhooks enabled, reach out to Teklink support with:
Customer name / account
Channels (numbers) that should trigger inbound webhooks
Destination webhook URL(s)
ChatServ’s API is actively evolving; additional capabilities (for example MMS sending) may be added later.