The short answer
A long unique password, changed if anyone leaves, and API keys stored on the server only. Repeated failed logins lock the address out temporarily.
Help centre · Developers
Keeping the account secure for developers
Another messaging integration to maintain. How do I protect the login? A long unique password, changed if anyone leaves, and API keys stored on the server only. Repeated failed logins lock the address out temporarily.
- Developers
- Keeping the account secure
- Plain English
- Live in 5 minutes
Why developers ask this
Another messaging integration to maintain. It usually surfaces the first time a real list goes out, when codes, alerts and notifications straight from your own code stop being a plan and become a send.
What it changes for you
Get this right and the outcome is one key, one endpoint and statuses pushed back. Get it wrong and the cost shows up quietly, in messages nobody read and money already spent.
Doing it in the platform
The compose screen shows the segment count, the cost and the sender name before anything leaves, so the decision is made before the money moves.
Getting started
Message support on Telegram at @exerioco. The account is usually open in under five minutes. Then you log in, paste your numbers, write the message, pick the sender name and send.
FAQ
How do I protect the login?
A long unique password, changed if anyone leaves, and API keys stored on the server only. Repeated failed logins lock the address out temporarily.
Is this different for developers?
The mechanics are the same. What changes is the volume and the timing, because developers mostly send codes, alerts and notifications straight from your own code.
How do I get started?
Message support on Telegram at @exerioco. The account is usually open in under five minutes. Then you log in, paste your numbers, write the message, pick the sender name and send.
Related pages
Messaging for developers
Support on Telegram at @exerioco sets you up in under five minutes.