SMS
Sender IDs

Sender IDs

List the sender IDs assigned to your organisation. Use the sender_id value when sending an SMS to control which name appears on the recipient's device.


Endpoint

GET /v1/bulk-sms/sender-ids/

Authentication: Bearer API key


Request

No body or query parameters required.

curl https://api.talkntalk.africa/v1/bulk-sms/sender-ids/ \
  -H "Authorization: Bearer tk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Response

200 OK

{
  "count": 2,
  "results": [
    {
      "id": 12,
      "sender_id": "TALKNTALK",
      "type": "promotional",
      "network": "safaricom",
      "status": "active",
      "is_default": true,
      "provider": "textsms"
    },
    {
      "id": 13,
      "sender_id": "TALKNTALK",
      "type": "transactional",
      "network": "airtel",
      "status": "active",
      "is_default": false,
      "provider": "usermobivas"
    }
  ]
}
FieldTypeDescription
countintegerTotal number of assigned sender IDs
results[].idintegerAssignment ID
results[].sender_idstringThe sender name shown on recipient devices
results[].typestringpromotional or transactional
results[].networkstringTarget network: safaricom, airtel, telkom, faiba, or other
results[].statusstringactive or inactive
results[].is_defaultbooleanWhether this sender ID is used when none is specified in a send request
results[].providerstringUnderlying SMS provider routing this sender ID

The default sender ID (is_default: true) is used automatically when you do not specify a sender_id in your send request. If your organisation has multiple sender IDs for different networks, the API selects the best match for the recipient's network automatically.


Code Examples

curl https://api.talkntalk.africa/v1/bulk-sms/sender-ids/ \
  -H "Authorization: Bearer tk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Error Responses

StatusMeaning
401 UnauthorizedMissing or invalid API key
{
  "detail": "Invalid or revoked API key."
}