Developer checklist
Before connecting the SMS API to live customer events, run one controlled send from your backend. Check your balance, record the response and confirm how you’ll investigate a send whose outcome is unclear.
Run one controlled test send
- Authenticate from your backend. Use your client credentials to obtain a token, and keep the credentials out of browser code, public repositories and logs.
- Check your credit balance. Review the message text and its expected SMS parts before you send. A real test send uses credits.
- Send one short message to a number you control or have permission to use for the test. Check the response and record the time and any reference, keeping credentials and message bodies out of logs.
- Check delivery information through the workflow available to your account. An accepted API request tells you the send was received for processing. Check delivery separately.
What should I do when a request fails?
| What you see | What to check |
|---|---|
| Authentication fails | Verify the account credentials and token configuration against the authentication reference. |
| Balance is too low for the send | Check available credits and the expected message parts before trying again. |
| The send times out | The request may have been accepted. Check the sending record and available status before sending again. |
What should be in place before go-live?
Use test data to exercise normal and failure cases in development. For the first live workflow, agree who can pause sending, who checks exceptions and what evidence your team needs to review before increasing volume.
Use the official .NET, Node.js or Python SDK for authentication, sending and checking balance, or use the HTTPS reference directly. If your workflow needs delivery status or replies, confirm the supported route before relying on it. SQL Server integrations have a separate worker and queue setup.