Pushing data directly to a complication on your Apple Watch

Our new Pushover for iOS update is out today and includes many great features such as per-application icons in notifications, synching dismissals of notifications across all of your iOS 10 and Android devices, and a new Apple Watch app.

One new feature we’re announcing today is our new Glances API which lets you push data directly to a complication on your Apple Watch. This is separate from our Messaging API which is great for urgent push notifications that pop up on your iPhone and Apple Watch.

For those occasions when you want to send small amounts of data that you can glance at periodically throughout the day, such as the number of items sold at your store today, or an update from your alarm system notifying you the garage door is still open, our Glances API makes this possible.

To get started pushing data to your Apple Watch, just add the Pushover complication on your watch face, then consult our Glances API Documentation to send data to it.

While our Glances API currently only supports the Apple Watch, we plan on bringing this to other screens in the future such as other smart watches and widgets on Android and iOS. We are also working on adding this new API to our existing integrations such as IFTTT, to make it easier for everyone to use.

Pushover notifications with Zapier Push Chrome Extension

Pushover is excited to be a part of Zapier’s launch of their new Zapier Push feature which allows users to manually trigger Zap workflows from their new Chrome Extension. Users of Zapier and Pushover can easily send out Pushover notifications from the click of a button right from Chrome.

With Push by Zapier, you can quickly push out pre-saved Pushover templates or type in a new message each time.

You can find out more about Push by Zapier on their blog.

New E-mail Gateway features

Pushover’s E-mail Gateway is a popular feature used by many of our users to get Pushover notifications from websites and legacy systems that can’t integrate with our API. Every Pushover user has been able to receive e-mail at Your-Pushover-User-Key@api.pushover.net and instantly receive it as a push notification, and this week we’ve launched a new E-mail Gateway with some great new features.

Shorter E-mail Addresses

A common request we’ve received from our users is to have shorter e-mail addresses. Some websites and legacy systems would not accept a 47-character address such as uxu6r9d3hk3s7bbj4vwjzbgqtahrnk@api.pushover.net, and so our new e-mail gateway offers much shorter e-mail addresses at a new domain pomail.net, such as jc5apkksxz@pomail.net. Every existing Pushover account has a new shorter address already assigned to it (in addition to still supporting your old 47-character address), which you can find on your dashboard.

Saved Settings

After launching our initial E-mail Gateway years ago, we heard from users asking for the ability to customize notifications, such as which devices would receive the message, setting the high-priority flag, and setting a custom sound. We supported these settings by adding them to the e-mail address, creating addresses like uxu6r9d3hk3s7bbj4vwjzbgqtahrnk+device=iphone+p=1+s=pianobar@api.pushover.net. As you can see, these addresses got pretty long, and some outdated e-mail systems would not accept e-mail with an address containing the characters + and =.

Our new E-mail Gateway allows you to change these settings from your dashboard without having to change the e-mail address later.

Multiple Addresses

Some users were hesitant to use their old Pushover e-mail address on an untrusted website since it contained their Pushover user key, worried they might receive spam notifications if their e-mail address were to be given out by those sites. With our new shorter addresses that don’t contain your Pushover user key, you can create new aliases for each website or service, each with its own settings, and then delete them later without worrying about spam. Once an e-mail alias is deleted, any new e-mail to it will be rejected and bounced back to the sender.

Available Now

Pushover’s new E-mail Gateway is available now. You can find your new shorter e-mail address on your dashboard as well as customize options and create additional aliases.

Note: While our new E-mail Gateway offers new addresses and settings, we will always support the older @api.pushover.net addresses (with custom settings) that you may already be using.

If you have any questions or comments about our new E-mail Gateway, please contact us.

Improved IFTTT support

Today we’re happy to announce a new Pushover channel on IFTTT, the site that lets you connect hundreds of different services together with simple recipes.

Our new channel allows you to define more Pushover parameters such as message titles, sounds, priorities, and selected devices.

For existing IFTTT users, your Pushover recipes have already been converted to our new channel. You can edit your recipes on the IFTTT website to take advantage of these new features.

If you have any questions or comments about this migration, please contact us.

Application message capacity auto-upgrade

For commercial Pushover users that send large amounts of messages each month, we offer the ability to purchase additional capacity through our website. Until recently, these upgrades needed to be purchased each month (or however often it took to use up your additional messages).

Recently we have added the ability to automatically upgrade your application each time its capacity reaches a certain amount, which you can set when activating the feature. Your credit card information is securely stored with our credit card provider, Stripe, and this auto-upgrade can be canceled at any time.

To activate this new feature, just log-in to our website, click on your application under Your Applications, and then click Upgrade Message Capacity. You’ll now see a new option to automatically purchase the same upgrade each time your capacity reaches a number you can adjust.

Intermittent connectivity issues on December 21st, 2015

On December 21st, 2015 at approximately 03:15 CST, Pushover’s web services began experiencing intermittent connectivity and latency problems that persisted until 06:40. These issues have been resolved and Pushover’s website, API, and Desktop client should be responding normally for all users. If you continue to experience problems reaching any of our services, please contact us.

Background: during the morning of Friday, December 18th, 2015, the upstream network provider for Pushover began experiencing intermittent packet loss along networks reaching some users. At this time, Pushover was switched over to its secondary server configuration, which exists on separate hardware at a different datacenter with a different upstream provider. This transition was performed seamlessly and all traffic was being routed to its backup network by the afternoon.

However, on the morning of Monday, December 21st, 2015, some users began experiencing high latency or failed connections to Pushover’s website and API. It was determined that these failures were caused by certain parts of the server software reaching built-in resource limitations. These limits had not been raised on the secondary server to the level that they were on the primary server that had been processing most traffic up until Friday. The limits were raised on the secondary server and it began processing all requests normally by 06:40.

API: Upcoming upgrade to SHA256 SSL certificate

Note: This announcement should not have any effect on end users. Many technical users, developers, and consumers of our API will not need to make any changes, but testing is advised to ensure compatibility with your systems accessing our API.

In approximately one month on Tuesday, September 15, 2015, Pushover will be upgrading its SSL certificate for api.pushover.net to be signed with SHA256. Our current certificate is signed with SHA1, which has already been deprecated by most browser vendors.

Last year we upgraded to a SHA256-signed SSL certificate for https://pushover.net and https://client.pushover.net. Since web browsers like Firefox, Chrome, and Safari are updated on a weekly or monthly basis with new security features, our users did not encounter any compatibility issues with these new certificates while browsing our website or accessing our Desktop client.

However, since some of our users are accessing our messaging API from older systems that are not updated as frequently, some encountered compatibility issues when we also updated the SSL certificate on https://api.pushover.net at that time. In response to those problems, we rolled back the certificate upgrade for just api.pushover.net.

As SHA1 certificates are now widely considered to be in need of replacement and are displaying with broken lock icons in some browsers, we are moving ahead with our SHA256 certificate upgrade.

To test your systems against our new certificate before we make the switch on Tuesday, September 15, 2015, you can temporarily use an API endpoint of:


instead of:


If you are able to send messages through api-newssl, then your systems are up to date and will not experience problems when we switch over. You can continue using api.pushover.net and when we upgrade next month, you will not need to do anything further.

If your systems are not able to negotiate an SSL connection to api-newssl.pushover.net, then you will need to upgrade your SSL library or operating system before Tuesday, September 15, 2015 or you will not be able to send Pushover messages after that date. You may need to contact your vendor to inquire about updates needed to access SHA256 SSL certificates in your software.

Note: api-newssl.pushover.net is only temporary and should not be used in production. Afer September 15, 2015, api-newssl.pushover.net will no longer exist.

Pushover for Apple Watch

A new release of Pushover for iOS is available today and along with important bugfixes and performance improvements, includes an Apple Watch app:

When you install the Pushover app on your Apple Watch, you’ll be able to scroll through a list of your recent messages.

Our Watch app also features dynamic notifications allowing you to see the application icon and full message text of your Pushover notifications. For emergency-priority messages, you can even acknowledge them right from your wrist:

Pushover for iOS is available now, along with Pushover for Android and Pushover for Desktop, all available with a free 7-day trial.

HTML Message Support

One of the features added to version 2.3 of our Android, iOS, and Desktop clients is support for HTML messages to style text. By sending messages to our API with the html flag set to 1, HTML tags in the message body will be interpreted by our apps and be used to style text. The current HTML tags we support are:

  • <b>word</b> - display word in bold

  • <i>word</i> - display word in italics

  • <u>word</u> - display word underlined

  • <font color="blue">word</font> - display word in blue text (most colors and hex codes permitted)

  • <a href="http://example.com/">word</a> - display word as a tappable link to http://example.com/

Due to the way notifications are handled on most platforms, HTML tags are stripped out when displaying notifications (leaving just the text content) but are shown inside the Pushover app once the client has synced with our servers.

Notifications on iOS intermittently not being received (Resolved)

We are working to resolve a problem that is affecting Pushover users on iOS where notifications are intermittently not being received. Once the Pushover app is opened, all of the messages download from our servers and are visible, but users are finding that some or all of those messages did not generate instant notifications on the device.

Unfortunately this problem is proving difficult to troubleshoot as all of the missing notifications are recorded as being sent out to Apple’s push servers successfully and we do not receive any indication from Apple’s servers that any of those messages have failed, so our servers do not retry delivery.

We will update this post as more information is gathered and when the problem is resolved. We apologize for the inconvenience this is causing our users.

Update Apr 16 12:17 CDT: We have identified a potential source of the problem and have implemented a workaround. We are continuing to monitor the reception of notifications on our various test devices.

Update Apr 16 15:20 CDT: We have been monitoring test devices for the past 3 hours and have not seen any dropped notifications, so we are considering this issue resolved. If you continue to have missing notifications for messages sent after today at 15:00 CDT, please contact us.