What it does
Recipients, text and sender name in a JSON body, with your key in the header from your server.
Developers
The shape of a request. Recipients, text and sender name in a JSON body, with your key in the header from your server.
Recipients, text and sender name in a JSON body, with your key in the header from your server.
One key, sent from your server, covers sending, scheduling and reading statuses. There is nothing to install and no SDK you are forced to adopt.
API traffic is priced exactly like traffic sent from the workspace: one published price per segment in EUR per destination, reserved before the job runs.
Keys belong on your server, in a secret store. A key can be replaced at any time with no downtime if you deploy the new one before deleting the old.
A person on Telegram at @exerioco answers integration questions in minutes, including during your first test sends.
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.
The shape of a request. Recipients, text and sender name in a JSON body, with your key in the header from your server.
No. Any language that can make an HTTPS request can send.
No. The same published price per segment applies whether you send from the workspace or from your own system.
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.
Message support on Telegram at @exerioco, get an account and create a key in minutes.