Home / API

Simple API. Powerful results.

Integrate SMS into any application — web, mobile or backend — with a clean REST API. Full OpenAPI documentation, WebSocket support for real-time delivery updates, and SDK-ready key authentication.

Read the documentation Get your API keys
Computer lab in a Tanzanian schoolNewHope
Endpoints

Send in one request.

Authenticate with your key and secret in the Authorization header, post JSON, and read the delivery status back.

  • POST/v1/sms/send/Send single SMS
  • POST/v1/sms/send-batch/Bulk send
  • POST/v1/otp/send/Send OTP code
  • POST/v1/otp/verify/Verify OTP code
  • GET/v1/sms/{id}/status/Delivery status

          
201 Created  {"status": "sent", "cost": 18.00}

        

      

    

  






  

    

      
Built for production

      
What you get with the API.

    

    

      
KEY
Key + secret auth
Separate keys for SMS sending and OTP, so a leaked key can only do what it was issued for.

      
JSON
Predictable responses
Every endpoint returns JSON with clear status fields and error messages you can show to users.

      
WS
Real-time status
Delivery updates over WebSocket and a status endpoint for polling, with detailed logs.

      
TEST
Test before approval
Test keys send from the default NewHope sender so you can integrate while your Sender ID is reviewed.

    

  






  

    

      
Quick start

      
Live in three steps.

    

    

      
1
Create keys
Register, open API Keys in the dashboard and create an SMS or OTP key. The secret is shown once — store it as an environment variable.

      
2
Send a test
Post to /v1/sms/send/ with the Authorization header from the example above and your own number.

      
3
Go live
When your Sender ID and top-up are ready, your production keys send from your brand name.

    

  






  

    
Read the full reference.

    
Every endpoint, parameter, error code and example is in the documentation.

    

      Open documentation
      See pricing