Everything worth knowing, nothing that isn't.
1. Request test access
Submit the short form at /signup. A BroadNet engineer replies within one business day with your test credentials. They work against the production endpoint, https://api.broadnet.me, and test messages go only to the mobile number you verify, so you can wire up your integration and test end to end before any live traffic. Integration testing typically takes 2–5 business days, and no test message reaches a real customer.
2. Complete business / KYC verification
To send to real recipients, submit your business details for verification (KYC). This is what unlocks live sending and lets you register the alphanumeric sender IDs your messages will use — most regulators require sender IDs to be pre-registered before any A2P traffic is accepted. In the dashboard, go to your account/verification section and provide the requested company documents.
3. Add billing
Before live sending is enabled you add a billing method in the dashboard under Billing. BroadNet bills AED or SAR for MENA accounts and USD for international accounts. Prepaid accounts add funds up front; enterprise accounts can arrange monthly invoicing. See /answers/payment-methods and /answers/top-up.
4. Go live — no code change
Once verification, sender-ID approval and billing are complete, BroadNet switches on production access and routes for your account. Your integration already calls https://api.broadnet.me, so there is nothing to re-point and no code to rewrite. See /answers/what-is-sandbox-vs-production.
Why test access comes first
Every account starts with test access: integration usually takes 2–5 business days, while sender-ID and compliance approval (3–10 business days) runs in parallel, so you can build, run automated tests and demo internally with no risk of a stray message reaching a real customer: until production access is switched on, messages go only to your verified numbers. See /developers/quickstart and /developers/authentication.