Send SMS via API (ChatServ)

Send SMS via API (ChatServ)

Overview

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).


Base URL

Use Teklink’s base URL:

  • Base URL: https://sms.theteklink.com


Send SMS endpoint

  • 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).


Request body

Required fields

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)

Optional fields (commonly used)

  • 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)


Example (cURL)

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"
}'

Response format

Typical response:

{
"success": true,
"message": "Message sent",
"data": []
}

Expected status code for a successful send:

  • 201


Incoming SMS (webhooks)

ChatServ supports webhooks for inbound SMS (so your system can receive messages in real time). To enable this:

  1. Customer provides Teklink with the public HTTPS webhook URL to receive inbound events.

  2. Teklink configures the webhook on the customer’s tenant/channel(s).

  3. 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)


Notes / roadmap

  • ChatServ’s API is actively evolving; additional capabilities (for example MMS sending) may be added later.

    • Related Articles

    • Understanding TCR Requirements for A2P 10DLC Messaging

      What is 10DLC? 10DLC (10-Digit Long Code) was introduced to allow businesses to send SMS/MMS messages using standard phone numbers while ensuring compliance with regulations. Originally, SMS was designed for P2P (Person-to-Person) messaging between ...
    • Firewall Rules (Kazoo)

      In some cases phones will might have issues with static or no audio, and sometime calls are being dropped or incoming calls are failing. In such cases it might be related to a firewall or other network issues, to resolve this please refer to this ...
    • Call Features (SkySwitch)

      1. Voicemail Description: Listen to recorded messages left when you were unavailable. You can also set up your voicemail greeting from here. Codes: Check Voicemail: *62 or 5000 Check Voicemail (Auto login): *61 or 5001 - Requires Setup How to use: ...
    • Call Features (Kazoo)

      1. Voicemail Description: Listen to recorded messages left when you were unavailable. YOu can also set up your voicemail greeting from here. Codes: Check Voicemail (Any box): *97 - Check the voicemails of any extension. You will be prompted for that ...
    • Phone Registration Issue and Troubleshooting Steps at a Workplace

      Introduction: In a workplace setting, phone registration issues can often occur due to various factors such as network-related problems or power outages causing disruptions in the operating system. Resolving these issues promptly is essential to ...