Built on Safaricom SDP

The telco layer for African products and the artists behind them

Skiza monetization, USSD, SMS, OTP and carrier billing, built in Nairobi on Safaricom's Value-Added Services platform.

CON / END
The session protocol your USSD handlers speak: 2547 / 2541
MSISDN normalization at every API boundary: 5
Product lines from one partner: Nairobi
Where the platform is engineered and supported

For artists

From track to 811 code

Upload a track, check its metadata and follow your share of monthly airtime revenue. Your fans dial one code to set your music as their tune.

How Skiza pays

Skiza code preview

Illustrative code

Track title

Artist

Live codes are assigned when Safaricom provisions your track.

For engineers

USSD menus as plain HTTP

Every hop is a stateless request that returns CON to continue or END to finish. Dial *384# on the handset and try it.

See it on the wire

Dial a code to start.
Try *384#

Products

One partner for Safaricom VAS

Register a Skiza code in one request

These samples call this site's sandbox endpoint, so you can run them as they are.

Open the API playground

curl -X POST https://tekglob.com/api/v1/skiza \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Baraka",
    "artist": "Amani Sounds",
    "language": "Swahili",
    "category": "Gospel",
    "payoutMsisdn": "0712345678",
    "audioFormat": "mp3"
  }'

Architecture

Where Tekglob sits

01
Your platform
REST calls and CON/END callbacks
02
Tekglob gateway
Validation, MSISDN normalization, sessions
03
Safaricom SDP
Provisioning, billing and messaging
04
Subscriber
Handset: USSD, SMS, Skiza, airtime