Use case

OTP delivery that actually arrives.

Send one-time codes from your own SIM. No short-code filtering, no A2P registration, no per-code fee.

Why teams switch

Codes were arriving late — or not at all. Aggregator short codes get filtered; a 30-second delay on a 5-minute OTP is lost users.
Per-message billing on auth traffic adds up fast.
Registration slowed launch. A2P 10DLC vetting before you can even send.

How SMSKit fits

Real local number, carrier-trusted, ≤15s typical delivery (our target). Priority routing pushes OTPs ahead of bulk. Idempotency keys mean a retried request never sends two codes.

Note ·Roadmap: a dedicated OTP send + verify endpoint (managed code generation, rate-limiting, constant-time check) is coming. Today you build the code and send it through /api/sms/send.

Start free

Acme · Login

+254 712 345 678

Example bash

curl https://api.smskit.cloud/api/sms/send \
  -H "X-Api-Key: sk_live_your_key" -H "Content-Type: application/json" \
  -d '{ "recipient": "+254712345678", "message": "Your verification code is 481920", "priority": 9, "idempotencyKey": "signup-8841" }'