Docs
Error handling
HTTP status
Treat non-success HTTP statuses as failures. Retry only when appropriate for your use case (for example after fixing credentials or payload).
Do not assume a fixed catalogue of application error codes from this page — confirm codes and messages in your portal response.
Common causes
Invalid or missing Basic Auth / un/up credentials.
Missing FUN, senderID, to, or msg.
Sender ID not approved for the account.
Insufficient balance — use CHECK_BALANCE before large sends.
Debugging tip
Log the full HTTP status and response body from a failing call (without printing secrets). Compare a working curl sample from Send SMS against your client.
Create account
Sign up in the portal and get your API key — username is your email, password is the key.
Open portal — get API key