Kudosity Sms

Send SMS Messages

Kudosity supports two ways to send SMS depending on the use case:

• Single recipient → V2 API (simpler, JSON-based)
• List-based send / multiple recipients → V1 API (supports list_id and comma-separated numbers)

Authentication

V2 API (single recipient):

• Header: x-api-key: {KUDOSITY_API_KEY}

V1 API (list-based or multi-recipient):

• Header: Authorization: Basic {base64(KUDOSITY_API_KEY:KUDOSITY_API_SECRET)}

Credentials come from the Kudosity dashboard under Developers → API Settings. Set KUDOSITY_API_KEY (and KUDOSITY_API_SECRET, which the V1 API needs) in the environment before calling.

Option A: Send to a Single Recipient (V2 API)

Endpoint: POST https://api.transmitmessage.com/v2/sms Content-Type: application/json

All API calls use curl commands.

Required parameters:

• message (string): The SMS body text
• sender (string): The sender number (must be assigned to the account) or alphanumeric sender ID (max 11 chars)
• recipient (string): Destination number (local or E.164 international format)

Optional parameters:

• message_ref (string, max 500 chars): Your reference ID, returned in webhooks
• track_links (boolean): Enable link tracking with shortened URLs

Example curl command:

curl -s -X POST "https://api.transmitmessage.com/v2/sms" \
  -H "x-api-key: ${KUDOSITY_API_KEY}" \
  -H "User-Agent: kudosity-skills/0.2.1" \
  -H "Content-Type: application/json" \
  -d '{"message": "Your order has shipped!", "sender": "61481074185", "recipient": "61491570156"}'

Response

The SMS response is a flat object — it is not wrapped in a data envelope.

{
  "id": "2d2c8fb6-e514-4f5f-9706-0672b0259218",
  "recipient": "61478038915",
  "recipient_country": "AU",
  "sender": "61481074185",
  "sender_country": "AU",
  "message_ref": "ncc1701d",
  "message": "Report to the ready room! Opt-out reply STOP",
  "status": "delivered",
  "sms_count": "1",
  "is_gsm": true,
  "routed_via": "",
  "track_links": true,
  "direction": "OUT",
  "created_at": "2022-03-28T06:12:52.450674000Z",
  "updated_at": "2022-03-28T06:12:52.450674000Z"
}

Two things to get right:

• sms_count is a string, not a number — "1", not 1. So is total_records on the list endpoint. Parse it before doing arithmetic, or sms_count + 1 quietly gives you "11".
• Envelope shape varies across the V2 API. SMS and MMS return the object flat, as above. WhatsApp, RCS, RCS capabilities and sender registrations wrap it: { "data": { ... }, "request": {}, "meta": {} }. Code written against one and reused for the other reads undefined. json.data ?? json handles both.

Keep id — it's what webhook events match against.

Option B: Send to a List or Multiple Numbers (V1 API)

Endpoint: POST https://api.transmitsms.com/send-sms.json Content-Type: application/x-www-form-urlencoded

Required parameters:

• message (string): The SMS body (up to 612 alphanumeric characters)
• One of:
  • to (string): Single number or up to 500 comma-separated numbers
  • list_id (integer): ID of a contact list to send to

Optional parameters:

• from (string): Sender ID — a virtual number, short code, or alphanumeric sender (max 11 chars)
• countrycode (string): 2-letter ISO country code to auto-format local numbers
• send_at (datetime): Schedule send in ISO8601 format YYYY-MM-DD HH:MM:SS (UTC)
• validity (integer): Message expiry in minutes (0 = max validity, auto-expires after 72hrs)
• dlr_callback (URL): Delivery receipt callback URL
• reply_callback (URL): Reply notification callback URL
• tracked_link_url (URL): URL to convert to a tracked shortened link (use [tracked-link] in message)
• replies_to_email (email): Forward replies to this email address

Example curl command (list-based):

curl -s -X POST "https://api.transmitsms.com/send-sms.json" \
  -u "${KUDOSITY_API_KEY}:${KUDOSITY_API_SECRET}" \
  -H "User-Agent: kudosity-skills/0.2.1" \
  -d "message=Sale starts tomorrow!&list_id=4213644&from=61481074185"

Choosing Between V1 and V2

Message Length

• GSM encoding (standard characters): 160 chars per single SMS, 153 chars per part for multi-part
• Unicode (emoji, non-Latin characters): 70 chars per single SMS, 67 chars per part for multi-part
• Maximum: 612 alphanumeric characters (V1) or multi-part as needed (V2)

Important Notes

• Always ask the user which sender number to use if not specified
• The sender must be a number assigned to the account, or an approved alphanumeric sender ID
• Alphanumeric senders cannot receive replies — max 11 characters, no spaces
• If opt-out is required with an alphanumeric sender, use [unsub-reply-link] in the message (V1) or [opt-out-link] (V2)