BroadNet
Commercial BroadNet answer

Test credentials vs production: what changes when you go live?

Last reviewed 1 min readReviewed by BroadNet engineering
Quick answer

BroadNet does not run a separate sandbox. Your test credentials work against the production endpoint, https://api.broadnet.me, with the same API and the same code you will run in production; test messages go only to your own verified number(s), and their delivery receipts come back to your webhook. Production access and routes are switched on for your account after approval (sender identity, traffic purpose and sender IDs), typically 5–15 business days from request, and your code does not change.

Plain-language definitionVendor-neutralReviewed September 29, 2026
The long answer

Everything worth knowing, nothing that isn't.

§01

What you can test with test credentials

The whole integration against the real API: authentication with your Bearer token, POST /sms/sendSms, the message ID in the response, delivery receipts to your webhook, error handling, encoding and segment counts. Test messages go only to your own verified number(s). The allowance, cost and expiry of your test are confirmed in our reply, with your credentials.

§02

What changes at go-live

Your code and your endpoint stay the same. What changes is who you can reach: after approval (sender identity, traffic purpose and destination rules reviewed, sender IDs registered with each regulator), production access and routes are switched on for your account, and traffic runs on your commercial terms. Approval takes 3–10 business days and runs in parallel with 2–5 business days of integration.

§03

Why testing uses the production endpoint

A separate test environment usually simulates delivery, so its receipts and latency tell you little about real routes. Testing on the production endpoint means the API, the responses and the delivery receipts you see during integration are the ones you get in production, and nothing needs re-pointing at go-live.

§04

Before you send live traffic

Keep the token in an environment variable or a secrets manager from day one: it calls the production endpoint. Store each message ID, retry without re-sending blindly, and confirm the delivery receipts reach your webhook. Then send a small first batch to real recipients in each new market and watch the receipts before you scale. See /developers/quickstart.

Test credentials vs production at a glance

Test credentialsProduction
Endpointhttps://api.broadnet.mehttps://api.broadnet.me
RecipientsYour own verified number(s)The recipients your approval covers
Sender IDsConfirmed with your test credentialsRegistered with each regulator during approval
Delivery receipts
Allowance, cost and expiryConfirmed in our reply, with your test credentialsYour commercial terms
Good forIntegration, webhooks, error handling, encodingLive traffic after approval
BNWritten by the BroadNet engineering team·Operating carrier-grade messaging since 2003, headquartered in Dubai·Editorial standards
FAQ

Frequently asked questions

Is there a separate test environment?
No. Test credentials work against the production endpoint, https://api.broadnet.me. Test messages go only to your own verified number(s), and their delivery receipts come back to your webhook.
What can I test with my test credentials?
The whole integration: authentication, POST /sms/sendSms, message IDs, delivery receipts to your webhook, error handling, encoding and segment counts, sending to your own verified number(s).
What changes at go-live?
Only who you can reach. After approval, production access and routes are switched on for your account; the endpoint and your code stay the same, and traffic runs on your commercial terms.
How long does it take from test access to production?
We reply within one business day with test credentials, and your first test message goes out about five minutes after you have them. Integration takes 2–5 business days and approval 3–10 in parallel, so most markets reach production in 5–15 business days; longer where a regulator's sender-ID lead time is longer.
Build with this

Need help wiring this up?

The pages below are the products and integration guides that put this concept on the wire. If you'd rather walk through it live, our engineering team takes calls same-day during MENA working hours.

Talk to our engineering team
Feedback

Was this answer helpful?

Your vote helps us prioritise which answers to expand with examples, diagrams, and code snippets.

Was this answer helpful?
Thanks — noted. We'll keep this answer maintained.
Got it. Tell us what was missing — send a quick note.

How we write and review content

Still need help?

Talk to a real engineer about your build.

We reply within one business day, and production accounts get 24/7 support. Our solutions engineers ship code, not scripts.

$ curl -X POST https://api.broadnet.me/sms/sendSms
Response SLA
Test-access requestsReply within 1 business day
Production24 / 7 · < 15 min
Operator NOC24 / 7 · pager