Note: This does not affect most Pushover users, only developers that have integrated Pushover into their applications or created Pushover libraries.
Starting April 15, 2013, our API will require a valid application token to be passed to our /1/sounds.json (or .xml) endpoint, similar to our messages and receipts endpoints. Requests without a valid application token will be rejected after April 15. Application and Pushover library authors are encouraged to take this change into consideration as soon as possible.
As a reminder, the results of this API endpoint should be cached for a reasonable length of time, such as 24 hours. Our sounds list does not change very often and calling it every time your application needs to present the list of sounds to your users is wasteful.
We’re happy to announce that all Pushover applications now have realtime API usage statistics, viewable for the past 45 days.
When viewing your registered application’s details, you will now see an interactive graph showing how many messages were sent each day, along with the current month’s total.
You can see usage statistics for your applications now by visiting the Applications & Plugins page while logged in.
makes it easy to integrate notifications into a wide variety of applications and services. Today we’re announcing an e-mail gateway that makes it possible to receive Pushover notifications from devices and services where API integration is not possible, such as with embedded devices, SAN servers, routers, and websites.
Our new e-mail gateway provides every Pushover user with an e-mail address that will turn any e-mails received into Pushover notifications. To get started, just send an e-mail to Your-Pushover-User-Key@api.pushover.net. By default, all notifications will be sent to all active devices on your account, just like other Pushover notifications. To have messages sent to only one particular device, use the e-mail address Your-Pushover-User-Key+Device-Name@api.pushover.net.
For example, if your user key were abcdefg12345 and you wanted to send a notification to your device iPhone, you would use the e-mail address abcdefg12345+iPhone@api.pushover.net.
HTML e-mails received by our gateway will be converted into plain-text with URLs preserved to enable them to be tapped on in the iOS and Android Pushover clients. Just like other Pushover notifications, e-mail notifications are limited to 512 characters and long e-mails will be truncated.
A new feature has been added to our API and is now supported by version 1.3 of our Android and iOS clients: supplemental URLs.
As before, all URLs included in the Pushover message body will be automatically turned into tappable links when viewed on our device clients. Sometimes, however, it is useful to include a URL that is not the actual content of the message, may be too long, or may use a custom URL scheme that is not recognized.
For example, an application using Pushover to send Twitter messages to devices may include a supplemental URL of “twitter://direct_message link?screen_name=someuser” and a URL title of “Reply to @someuser”. When the message is expanded in the Pushover client, the user will be given the option of opening the supplemental URL, which in this case would launch a Twitter client installed on the device and send a direct message to “@someuser”.
For more information on using this new feature, check out our API documentation.
Please note that supplemental URLs require version 1.3 of our iOS and Android clients, both released today.