Bug Report

If you are experiencing a bug in our Pushover app, the first step is to reproduce the problem.  If you can't reproduce it, we probably can't either and won't be able to fix it.

Once you are able to reproduce the problem, tap the menu icon in the Pushover app, then tap Settings, then scroll down and tap Resolve a Problem.  Scroll down to the bottom and tap contact our support.  Choose "Bug report - Android app" as the request type and then include all of the relevant information in the Message field such as your steps for

For most Pushover users, you'll be receiving messages through applications and services that already support Pushover.  You'll input your Pushover User Key or go through the notification subscription process to receive notifications without having to enter a User Key.  You can also use our E-Mail Gateway to receive Pushover notifications from software and services that doesn't support Pushover, but which can send e-mail.

For developers or users wanting to send notifications to other users, you'll use our Message API to send notifications to other Pushover users.  Each user you want to send notifications to will need to have a Pushover

During normal operation, your devices will receive Pushover notifications within a second or so, often within a few hundred milliseconds.  If your notifications take a long time to receive (more than 10 seconds), here are some things to check:

Pushover Network Issues

Pushover has a network status page where we list any issues with our service.  If we are having delays sending out notifications, or if Apple's or Google's notification servers are having problems, we will update our network status page.

E-Mail Gateway Delays

Our E-Mail Gateway receives e-mails and turns them into Pushover notifications, but we can only do

No, Pushover does all of its communication with your device over the Internet, using the connection your phone already has to Google or Apple for receiving push notifications.

While you will not incur per-message SMS charges for receiving Pushover notifications, it also means that Pushover requires a working WiFi or cellular data connection to receive notifications. If your phone is out of range of a data provider, it will receive all queued up notifications once it establishes a working data connection.

No sounds when application is open

If you're testing out Pushover for the first time, you may have the Pushover app open while you wait for the message to arrive. In this scenario, you will not hear a notification alert sound and/or feel vibration and you might think something is wrong. By default, the Pushover apps do not play sounds or vibration when the screen is on and the Pushover application is visible, because no notification is generated with the system; the message is received and displayed directly by the running Pushover application which you can see at the top

Tasker Variables

Pushover for Android (as of version 2.1.2) includes a Tasker action plugin that can be used with the 3rd party Tasker app (sold separately) to perform actions whenever a Pushover notification is received. This plugin is built into the Pushover app and there is nothing extra to install (aside from Tasker).

Pushover exports a number of variables to Tasker which can be used in tasks, such as the content of the message, its URL, etc. These variables are:

• %pushovertitle - The message title (may be blank)
• %pushovermessage - The message body
• %pushoverapplication - The name of the application

iOS 10 introduced some additional notification features, such as image attachments. Pushover for iPhone uses this to show per-application icons, in addition to the standard Pushover icon. Our Apple Watch app for watchOS 3 has a dynamic notification interface that can show these icons as well. However, if the Pushover application is not installed on your Apple Watch, you will see the per-application icon as a full-screen image. To resolve this problem, you need to have the Pushover app installed on your watch.

If you still see these full-screen icons with the Pushover watchOS app installed, you may need to

If your local database of messages became corrupted, you will experience errors when visiting https://client.pushover.net/ and you will be redirected to an error page. You can try to re-initialize the local database of messages to resolve this problem. Note that this will delete all of your past Pushover messages that are stored in your browser.

Chrome

Open the Chrome settings, then click Show Advanced Settings at the bottom. Click the Content Settings button, then click All Cookies and side data. In the search box, type pushover.net, and then hover over the client.pushover.net entry, and click the X on the right

On both Android and iOS, our in-app purchase for a license on that platform is "non-consumable" which means it can only ever be purchased once (per Google Play or App Store account). If you have gone through the in-app purchase process and the purchase was successful the first time, going through the in-app purchase process a second time will not charge your card twice, but will instead fetch your previous purchase information and validate it.

If you have previously gone through the in-app purchase process and your account is still showing as on a trial, open the settings menu of

The Shortcuts app for iOS can be used to send Pushover notifications by sending HTTP requests to our API.  These shortcuts can be run manually or automatically in response to an Automation, such as "send a message when a HomeKit action happens".

Open the Shortcuts app, and tap the + button.

Tap the Add Action button.

Tap Web.

Then select Get Contents of URL.

Tap on the URL, and enter https://api.pushover.net/1/messages.json and change the Method to POST.

Tap Add new field and add new fields for each required API parameter, such as token, user, message, etc.

For certain fields such

Our API that websites and applications use to send you messages allows for each message to have a particular sound, in the case of applications sending multiple types of messages.  For example, a network monitoring system sending a "host down" message could choose a longer, more severe sound, but on a "host up" message, choose a softer, more subtle sound. When an application specifies a message sound, it will override the default sound that you have chosen in your app settings. For this reason, we encourage most applications that don't need this special functionality to leave the sound setting to

Slide out the application list by sliding left-to-right, then tap-and-hold on a particular application to access its context menu where you'll be able to delete all of its messages or re-fetch its icon.

To delete all messages globally, tap-and-hold on the All Messages entry and then tap on the Delete All Messages option.

Unfortunately this is a limitation of macOS's Safari notifications. We deliver these notifications to Apple's servers in order to deliver them to your desktop, and there is currently no way to specify a sound to be played. This limitation does not exist with our in-browser desktop client, since we generate notifications ourselves and can play a sound in the browser at the same time.

Please see our security page for vulnerability disclosure and other information.

The Apple Watch complications included with the Pushover Watch app are designed to display data from our Glances API, not our general Messages API.

This separate API was created for a few reasons:

1. Messages (notifications) are generally much longer than the amount of data that can fit in most Apple Watch complications which are limited to one or three short lines of text, or sometimes just a single number.
2. Messages can be received at any rate, while Apple Watch complication updates are severely rate limited by watchOS.  Attempting to update a complication every time a notification was received may cause

Pushover Subscriptions are a great way to add other Pushover users to a Delivery Group to be able to broadcast messages to them, all without having to manually collect Pushover User Keys.  Subscribed users can also unsubscribe from your notifications at any time in the future without any effort required on your part.

By creating a Group-based Subscription, users can visit a URL that we create for your application and choose to subscribe to notifications from your application.  Once subscribed, the user will be added to a Delivery Group with a single-use User Key that is deleted as soon as

Due to the design of our systems, we do not store messages on our servers once they have been reliably received by your device client. To view a notification on multiple devices on your account, it must have been delivered to those devices. By default, all notifications sent to your account will be delivered to all active devices on your account. If you delete a message on one device, it will not affect that message stored on any of your other devices.

Each application registered to send Pushover notifications may send 10,000 messages per month for free, where one message is defined as successfully sending a message through our API to one user, regardless of the number of devices on their account. For Delivery Groups, each user in the group receiving that message counts as one message towards the application's quota.

One application assigned to a Team can send up to 25,000 messages per month for free. All other applications can send the usual 10,000 amount for free.

To send more than the free amount of messages per month, upgrade packages are

This situation often occurs from misconfigured 3rd party software that sends messages through our API.

Emergency-priority Messages

Each message sent to Pushover's API can include a user-specified priority which alters how the message is handled. (Contrary to the documentation of some 3rd party software, this priority has no affect on how quickly your message is processed or delivered through Pushover.) The highest priority, emergency (2), will repeat the alert multiple times until you acknowledge it by tapping on the notification and then tapping on the "Acknowledge" button in the app. These emergency-priority messages are indicated by a bright red background

We use industry-standard TLS (HTTPS) encryption for all communication in Pushover, in every step of the process between your servers and our API servers, our servers and Apple's and Google's push notification servers, those push servers to your devices, and our apps back to our servers.

Our iOS and Android apps use AES-256 message encryption with a random, per-device key automatically generated for your device upon registration. Our servers encrypt your messages before sending them through Apple's and Google's notification servers, then our apps running on your devices decrypt the messages before showing them as notifications.

Our desktop/browser app uses TLS