Everything worth knowing, nothing that isn't.
Start with your test credentials
Test credentials work against the production endpoint, https://api.broadnet.me, and test messages go only to your own verified number, so you test the real API without reaching real customers. Confirm auth works and the submit call returns the expected message id and status. See /answers/what-is-sandbox-vs-production and /developers/quickstart.
Verify the delivery receipt
A successful submit is not a delivered message. Point a webhook at your endpoint and confirm the DLR arrives with an operator-level status, so you know end-to-end delivery works. See /answers/what-is-dlr and /answers/what-is-a-messaging-webhook.
Check encoding and segments
Send a message with an emoji or non-Latin character to confirm your pipeline handles Unicode and counts segments correctly — a silent encoding bug inflates cost and can trip filters. See /answers/what-is-encoding-gsm-7-ucs-2 and /tools/sms-segment-calculator.
Then test real routes
Your test messages prove your code; only a small first campaign to your actual destination countries, after approval, proves route quality. Audit the DLR feed for operator-specific codes and stable delivery before scaling. See /answers/how-to-choose-sms-provider.