Request test access.
Test with your verified number. Before production, we review sender identity, traffic purpose and destination requirements. Tell us what you're building — a messaging engineer replies within one business day with test credentials and a 30-minute onboarding call.
Request test access
Reply within 1 business dayA messaging engineer replies with your test credentials and books a 30-minute call on your countries, volumes and use case.
First test message
About 5 minutes after credentialsSend a test message to your own verified number with the quickstart code. The delivery receipt comes back to your webhook.
Integration
2–5 business daysBuild and test with your test credentials against the same endpoint as the code samples. A BroadNet engineer pairs with you on REST or SMPP.
Approval
3–10 business daysSender identity, traffic purpose and destination rules are reviewed, and sender IDs are registered with each regulator, in parallel with your integration.
Production
Cutover dayProduction access and routes are switched on for your account. Your integration already calls https://api.broadnet.me.
Overall: 5–15 business days from request to production for most markets; longer where a regulator's sender-ID lead time is longer.
See the full onboarding playbook.
Test terms
- Destinations
- Your own verified number(s).
- Delivery receipts
- Available for your test messages.
- Allowance, cost and expiry
- Confirmed in our reply, with your test credentials.
Production traffic starts after approval, on your commercial terms.
Trusted by leading GCC operators, banks and 60,000+ enterprises since 2003.
Your test access request
Two short steps. An engineer reviews every request and replies within one business day with test credentials for your own verified number.
- 1You
- 2Your test