Programmatic virtual numbers, over a REST API
Everything you can do in the dashboard — buy a number, watch for its SMS, cancel it, manage webhooks — is also a plain HTTP call. No SDK required.
curl -X POST https://connect369.vercel.app/api/v1/numbers \
-H "Authorization: Bearer c369_live_..." \
-H "Content-Type: application/json" \
-d '{"country":"US","app":"whatsapp"}'
curl https://connect369.vercel.app/api/v1/numbers/{id}/sms \
-H "Authorization: Bearer c369_live_..."A simple REST API
Plain JSON over HTTPS. Buy a number, poll for its SMS, cancel it — three calls to integrate the core flow.
Webhooks, not just polling
Register an endpoint and get an HMAC-signed POST the moment an SMS/OTP arrives, instead of polling on a timer.
Sandbox mode
Test-mode API keys simulate the full purchase flow with no real wallet debit and a deterministic fake OTP — build and test your integration without spending real balance.
Scoped API keys
Issue read-only keys for reporting/monitoring separately from full-access keys that can buy and cancel numbers.
Real-time delivery
SMS is relayed to your webhook or available via polling typically within seconds of arriving upstream.
Verifiable webhooks
Every webhook delivery is signed — verify the X-Connect369-Signature header before trusting the payload.
Common use cases
Account verification at scale
Provision a number per signup for OTP-based verification without managing telecom infrastructure.
QA & test automation
Use sandbox keys in CI to test SMS/OTP flows deterministically, with zero wallet spend.
Multi-app social bot management
Register apps across WhatsApp, Telegram and more, each on its own number, all through one API.
Internal tooling
Wire webhook delivery straight into your own ticketing/ops system instead of a shared inbox.