Developers

Securing callbacks

Verify anything that calls you. Check the signature on every inbound call before acting on it, and never trust a payload because it arrived at the right address.

SMS API
Securing callbacks
One key
Live in 5 minutes

What it does

Check the signature on every inbound call before acting on it, and never trust a payload because it arrived at the right address.

How it fits an integration

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.

Cost is the same as the interface

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.

Security

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.

Support while you build

A person on Telegram at @exerioco answers integration questions in minutes, including during your first test sends.

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

What is securing callbacks?

Verify anything that calls you. Check the signature on every inbound call before acting on it, and never trust a payload because it arrived at the right address.

Do I need a library?

No. Any language that can make an HTTPS request can send.

Is API pricing different?

No. The same published price per segment applies whether you send from the workspace or from your own system.

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

Build with it today

Message support on Telegram at @exerioco, get an account and create a key in minutes.