Send push alerts to your users' phones through our free application. Built for what cannot wait: an alarm, a critical incident, an authorisation someone has to give right now.

Unlike an SMS or an email, the alert can ring with the phone asleep and, if you mark it as critical, even with Do Not Disturb switched on. And you get to know whether it arrived, whether it was opened and whether it was accepted.

Devices are linked from your panel (Alerts section), not through the API: that is where you generate linking codes —for yourself or for any of your authorized users, including staff who never log into the panel: hand them the code and all they need is the app—, see every device on your account and revoke them.

You can give each device an alias (warehouse-1, night-shift…): that alias is the REF parameter of EnviarPush. Without REF, the alert goes to every device on the account.

Groups are words inside the alias. If your devices are named warehouse-oncall-1, store-oncall-2…, then REFCONTIENE=oncall alerts the whole on-call group in a single call. Moving somebody to another group is just editing their alias in the panel (they change department, leave the on-call rota…) — nothing to register or maintain.

Your alerts also carry an application code (APLICACION parameter: alerta, aviso… whatever you invent). Each application shows up automatically in the panel as one more source, and the owner of each device chooses which sources each device receives: application alerta on phones 1 and 3, aviso on 1 and 2… No registration needed: the first time you send with one, it exists.

1. In your panel, Alerts section, generate a linking code (for yourself or for an authorized user).
2. The person installs the alerts app and types that code.
3. Give the device an alias in the panel list (optional: without one it still receives account-wide alerts).
4. You can now send alerts with EnviarPush, with REF=alias for one device or without REF for all of them.

No password is ever typed into the app. The code lasts a few minutes, works once, and generating a new one voids the previous one. There are no user credentials for you to store or protect.

Each level is a separate notification channel on the phone, so the recipient can silence informational alerts and keep critical ones ringing without disabling the whole application.

Every alert goes through up to four states. The last three are pushed to your server as they happen (see Receiving state changes):

There is no «read» state, and that is deliberate: a notification is read on the lock screen without ever being touched, and there is no technical way to know. Calling «delivered» «read» would mislead you on a figure you are going to use to decide whether to alert someone again.

The states are set by the recipient's phone, not by us, so they arrive when that person picks up the device. That is why we push them to a script on your server as they happen, just like the rest of our APIs: switch it on in your panel and your system finds out immediately without making a single request.

You are charged per recipient alerted, not per device: if that person has both a phone and a tablet linked, both receive the alert and you pay for one.

Generating codes, receiving state changes and managing devices cost no credits.

Same as the rest of our APIs: Basic authentication with your user and your API Token, which you will find in your panel under Your data → Configure → Security. Remember to authorise there the public IP address you will be calling from.