News and status updates for the Pushover notification service.

Pushover for Android - Now With Tasker Support

A common request we’ve gotten from our Android users is to create a plugin for Tasker, a popular automation application. Up until recently, Tasker did not support 3rd party event plugins which made it difficult for an application like Pushover to integrate with it.

The recently released Tasker 4.3 now supports 3rd party event plugins, and Pushover for Android 2.1.2 released today includes a Tasker event plugin.

Demo - Disabling WiFi from a Pushover Notification

To demonstrate the kind of functionality that Pushover and Tasker can provide, we’ll create a task that responds to a Pushover notification sent from our “WiFi” application (so other Pushover applications don’t trigger it) with a message “disable wifi”, and then actually disable WiFi on the device.

First, open Tasker and create a new profile.

Choose “Event”, then “Plugin”.

If you’ve updated to the new version of Pushover, you should see it listed here:

Now we’ll create some criteria for matching notifications. We’ll enter “disable wifi” as the message name to match (matching for all fields except “priority” is case-insensitive and matches any part of the string) and require the Application Name to match “wifi”.

After entering the criteria and tapping on the checkmark icon, Tasker will take you back to the home screen and prompt you for a task name. We’ll create one called “disable wifi”.

Now we’ll add an action to disable the system WiFi. Choose “Net” from the action list, and then “WiFi”. The default will be to turn it off.

Tasker Variables

In addition to just responding to notifications, Pushover exports the title, message, application name, URL, URL title, and priority to Tasker so you can use them in your tasks. Display the received message as a popup, open the URL automatically in your browser, etc.

For our “disable wifi” task, we’ll add a Popup dialog just for some confirmation. Add another action and choose “Alert”, then “Popup”.

Here we’ll create a title with “Pushover - %pushoverapplication" and a text of "%pushovermessage”. These two variables starting with % will be dynamically updated with the values from the Pushover notification you’re working with. The variables we export are:

  • %pushovertitle
  • %pushovermessage
  • %pushoverapplication
  • %pushoverurl
  • %pushoverurltitle
  • %pushoverpriority

Now we’ll send a new notification from the Pushover dashboard as our WiFi application, with the message text “disable wifi”. As soon as the notification comes in, Pushover hands it off to Tasker, Tasker disables wifi, and shows our popup:

We hope you find this new Tasker functionality useful in automating your devices. For more possibilities with Tasker, check out the Tasker User Forum and the /r/tasker Subreddit.

If you’re not a Pushover user already, check out our Android and iOS apps.


Pushover CVE-2014-0160 / Heartbleed Information

Like many websites, Pushover’s servers were vulnerable to the recently discovered OpenSSL bug CVE-2014-0160, also known as “Heartbleed”. All of Superblock’s servers, including those for Pushover, were quickly patched to fix this bug by the evening of Monday, April 7. As a precaution, we expired all user sessions and created a new session encryption key for once the bug was patched.

Once it became verified that private SSL keys could be extracted, we also requested and installed a new SSL certificate for * this morning, Saturday, April 12. We have requested revocation of our old certificate as well.

While we do not have any evidence that this security vulnerability was used to gain access to any of our user accounts or that our private SSL key was ever extracted, we encourage users to update their Pushover password at Users concerned about their user keys or application API tokens can contact us for manual regeneration of these tokens.

As always, please feel free to contact us with any questions or comments.


Preview of Pushover for Desktop

Today we’re excited to give you a sneak preview of Pushover for Desktop: an in-browser desktop client for Pushover allowing you to receive instant push notifications on your desktop just like you already do on your iPhone, iPad, and Android devices.

While the Pushover for Desktop site is open in any tab of your Chrome or Firefox browser on Mac, Windows, and Linux/Unix, you’ll receive instant popup notifications for new messages with the same icons and sounds you’re used to from our mobile apps (which you can of course silence):

On Chrome, you’ll see notifications in its Notification Center which gives a quick history of your recent alerts:

On Mac OS X (Mountain Lion and newer), registering with Safari will take advantage of the new Notification Center and push notifications built into OS X, allowing you to receive push notifications without any browser open at all, even on your lock screen:

A handy feature of Pushover for Desktop is the ability to quickly send notifications to your other Pushover devices. While you’re on your desktop, you can quickly send a note or a webpage link to your phone for viewing later:

Today we’re opening up the Pushover for Desktop beta program and we invite current Pushover users to try it out for free and give us your feedback. If you’re an existing Pushover user on iOS or Android and would like to beta test Pushover for Desktop, please signup to our beta program (edit: Sorry folks, we’ve received a ton of beta signup requests and have closed the program to new applicants for now).

We’re very excited to bring this new desktop client to you and we expect to release it to all of our users in the coming weeks. Stay tuned to this updates site or follow us on Twitter @superblock for more updates on Pushover for Desktop.


Upcoming Maintenance on March 11

On March 11, 2014 between 02:00 and 02:45 Central Time, Pushover will be undergoing maintenance which requires taking our systems offline.

During this maintenance window, our API and website will be offline and no messages will be queued or notifications pushed. E-mail to your address will most likely remain queued on the remote sending servers until our servers come back online to accept it.

If you have any questions about this maintenance, please feel free to contact us.


Developers: Upcoming SSL Certificate Change

On March 1, 2014, the SSL certificates for and will be changing to a new wildcard certificate covering *

For most of our end-users, and developers accessing our API, this change will be transparent and nothing is required on your part. Your web browsers already support wildcard certificates, as do our iOS and Android device clients.

While the CA chain remains the same for the new certificate, some developers or users of our API may be using older SSL libraries that do not support wildcard certificates when doing SSL hostname verification. This may cause SSL validation errors and prevent your scripts and applications from properly accessing our API. Most modern SSL libraries like OpenSSL, as well as any clients that use it like curl, do support wildcard certificates.

In order to test your applications with our new certificate, we have setup with the new wildcard certificate. All existing API endpoints are the same at the new host:


Note: This new hostname is for short-term testing only, and should not be used in your production environment. On March 1, 2014, we will switch to the new wildcard SSL certificate everywhere and the DNS record will be removed.

If you have any questions about this change, please feel free to contact us.

Tags: API

Pushover 2.0 for iOS

On the heels of our Pushover 2.0 for Android release, Pushover 2.0 for iOS has been released today.

Updated for iOS 7

Pushover 2.0 for iOS has been redesigned and adapted to the look of iOS 7. The Refresh button has been replaced by iOS’ standard pull-to-refresh behavior on the message list and the Settings button has been moved to the right.

Slide-out Application Menu

By sliding from left to right on the message list, or tapping the new button in the upper left corner, an application menu becomes available listing all of the different applications that have pushed notifications to you. Tapping on an application will filter the message list to show only the notifications from that app.

On iPads in landscape mode, the application list is visible at all times, making better use of the screen space.

Dedicated Message View

Tapping on a message will now slide in a dedicated message view rather than expanding it inline like previous versions did. This view shows your message in a larger font with dedicated copy and delete buttons.

Background Updates in iOS 7

Taking advantage of a new feature in iOS 7, Pushover 2.0 now does background updates of your message list when you receive new Pushover notifications. When you open the Pushover app on your device, your messages will now be already synced and ready for viewing.

We hope you enjoy this new Pushover release. As always, we welcome your feedback. If you’re new to Pushover, check us out and get our Android and iOS clients.

Update: We’ve received reports of the new app crashing on iOS 6 when viewing a specific message. We’ve found and fixed the bug and submitted a new release to Apple, but it will take some time for them to approve it. We apologize for the inconvenience.


Pushover 2.0 for Android

A year and a half ago we introduced our first Pushover client for Android. 26 releases later, we’re introducing Pushover version 2.0 with a facelift and new functionality.

Pushover now has a sleeker look that is unified across all versions of Android, bringing Android 3 and 4 design and functionality to our app while on Android 2, which we proudly still support.

Slide-out Application Menu

As Pushover has been adopted by an increasing number of applications, services, and websites, it’s even easier to get more Pushover notifications on your devices. With the new slide-out menu of Pushover 2.0, you can quickly get access to the messages from each application that you use.

Tapping on an application will filter the message list and show you only the notifications from that app.

On tablets in landscape mode, the app list is visible at all times.

New Message View

Pushover now has a dedicated message view, presenting your notifications in larger text and more detail. The message view has a dedicated share button to export message text to other Android applications, as well as a delete button.

Swipe to Delete

Perhaps the most often requested UI feature from our Android users has been swipe-to-delete. While our app used to follow the traditional Android behavior of long-pressing an item to pop up a context menu, times have changed and many Android apps have embraced the swipe-to-delete behavior native to iOS.

With Pushover 2.0, you can now swipe messages to the left to quickly get rid of them.

Pull to Refresh

While it’s usually not necessary to manually perform a message sync, this action is now even easier and can be done by just pulling down on the message list.

Notification Dismissal Sync

Pushover now has an optional feature to synchronize the dismissal of notifications across your Android devices. Let’s say you have an Android tablet and an Android phone activated on your Pushover account and you receive the same notification on both. With notification dismissal sync enabled, you can now dismiss the alert on your phone and not have to see it in the notification bar when you pick up your tablet, or vice versa. This feature is only for notification-bar alerts, and the messages will still remain viewable in the Pushover application.

We’ve developed this feature using our own servers so that we can bring notification dismissal syncing to other platforms on which Pushover is supported in the future (though due to limitations in iOS, we will not able to bring this feature to the iPhone and iPad).

We hope you enjoy this new functionality in Pushover 2.0 for Android, available today on Google Play.

To our iOS users, hang in there. We will be bringing much of these interface improvements to Pushover 2.0 for iOS after iOS 7 is released.


Introducing Delivery Groups

Over the past few months, we’ve heard from a number of Pushover users that are using it to broadcast notifications among small teams such as teachers, students, on-call technicians, and various volunteer organizations. The increasing number of applications and libraries that support Pushover’s API have made it easy for non-programmers to send custom notifications.

Today we’re introducing Delivery Groups to make it easier to manage lists of Pushover users and send notifications to them in a single API request. While larger-scale applications already have server-side databases and can easily manage dozens or hundreds of Pushover user keys, for small applications and teams it may be difficult to setup and manage a database.

With Delivery Groups, you can create and manage lists of users right from our website. Once you first create a group, you’ll get a Group Key that you can use to easily broadcast notifications to every user in the group with one API request. Our Group Keys have the same format as User Keys and can be used today with any application or library that has Pushover support.

As your team or list of users changes over time, you can add and remove users whenever you need without having to update any of your applications or scripts. Your Group Key will stay the same and will always broadcast notifications to the current list of users in the group.

We hope you’ll find this new feature useful and, as always, we love to hear feedback on how you’re using Pushover.


This month, 50% of Pushover revenue to be donated to EFF

For the month of June, 50% of all revenue brought in from our Pushover apps for Android and iOS will be donated to the Electronic Frontier Foundation. The EFF is a non-profit organization dedicated to defending free speech, privacy, innovation, and consumer rights.

If you’re already a Pushover user, we encourage you to learn more about the EFF and donate to protect your rights.

Tags: Pushover eff

API Change: Application Token Required for Sounds Request

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.

Tags: API