Start here
Textly gives businesses a dashboard for campaigns and a public API for messages sent by their own software. Both use the same account, sender IDs, wallet, and delivery history.
QuickstartCreate an account, get an API key, and submit your first message.API referenceSee authentication, send requests, status lookup, and workspace endpoints.Delivery webhooksReceive signed events when a message changes state.Explore the platformSee how the dashboard and API fit together.
How Textly works
Your application or dashboard submits messages to Textly. Textly validates the recipient, checks the sender ID and wallet, reserves the estimated charge, and queues each message for dispatch. A separate worker sends to our upstream SMS provider and records the provider message ID. Delivery receipts update the message status afterward.
Provider acceptance is not delivery.
A message can move from queued to accepted before a delivery receipt says delivered or failed.
Key concepts
- Organization: your business account and its contacts, templates, sender IDs, wallet, and API keys.
- Sender ID: the name shown as the sender. It must be approved before use. Public sender IDs may also be available.
- Wallet: your available balance and funds reserved for queued messages. Amounts are recorded in integer KES cents.
- Idempotency key: a unique value on each send request that makes client retries safe.
- Delivery webhook: an optional HTTPS endpoint where Textly sends signed status events.