At the moment EZAlert.me supports the following platforms:
EZAlert.me supports messages long up to 4096 chars. Some additional limit can apply on the destination istant messaging platform.
You can use EZALert.me for free.
In the future we will probably add paid plans that will provide advanced features, like more than one channel per account, a higher hourly API call rate limit, and higher priority messages.
Yes, BUT there is a limit for the hourly usage of the API.
In the free plan the limit is set to 10 API calls per hour, so you can send a maximum of 10 alerts per hour.
Since anybody can use EZAlert.me for free, we need to limit the use of the platform of each account to allow all users to beneft from our alerts delivery.
Each API response will include a x-ezalertme-apilimit header that will export the number of calls you did and actual hourly limit.
means that you used 3 calls on the 10 available in the hour.
In any event if you go over the limit the API will reply with an error.
We are working on that and the more people will use and support EZAlert.com the more effort we will spend in adding new features.
However, we also have to consider that not all instant messaging platforms can be connect.
At the moment Whatsapp terms of service do not allow us (or anyone) to build bots that can send messages to their users. Anyway we will be more than happy to add Whatsapp in the future if things change.
In the meanwhile, we strongly suggest you to give Telegram a try.
At the moment Twitter impose a strict limit to the number of daily direct messages an App can send. This limit looks low and can be a severe limitation to the ability of EZAlert.me to deliver alerts via twitter to the whole userbase.
Yes, but whoever needs to receive your alerts must first register to your EZAlert.me channel, sending a message to EZAlert.me BOT containing the channel start code.
Each channel has a different start code, so only people that know the code can receive your alerts.
This registration process also prevents the use of EZalert.me to deliver marketing messages.
EZAlert.me can only be used as an alerting tool, it is not for marketing!
Once your program/device calls EZAlert.me API to send an alert, the alert is stored in a queue with all the alerts sent by all the other users.
Alerts queue is usually processed in a first-in-first-out fashion, but we also planning to have queue priorities for paying customers in the future.
We do our best to transport your alerts to destination, but Internet is a complex ecosystem and many things can go wrong in the transport process.
This means that EZAlert.me uses a best effort strategy to deliver your alerts but we can't guarantee they will be always delivered.
As soon as this service will be more stable (out of the beta stage) we are going to publish delivery statistics.
We do our best to keep our systems safe. Anyway all the alerts processed by EZAlert.me are short term stored in unencrypted form, so we strongly suggest you to not send sensible/classified data via EZAlert.me.
EZAlert.me aim is to allow you a convenient way to be notified about events from automatic systems, and is not intended to be suitable for transporting confidential information.
Yes! Each EZAlert.me channel also has an email gateway that can deliver email alerts via istant messages.
EZAlert.me collects and stores the minimum viable set of data needed to provide you the service: usually only the username and full name you used on the IM. We are not interested in collecting user data.
EZAlert.me will only send you messages strictly related to the service itself. If you connect to one of EZAlert.me bots you will receive the alerts you will send via API or email gateway and few very rare general communications about the service itself (like maintenance schedules, service changes, and so on). We do not and will not spam, send advertisement or any other messages which is not strictly related with EZAlert.me service.