We've put together some various sizes of our logo to show off your Pushover integration. Please download and host these logos on your own websites and documentation rather than hotlinking directly to these files on our site.

For libraries that encompass our API in a particular programming language, you are permitted to use the Pushover name in your project name (e.g., "php-pushover") as long as you make it clear in your documentation and source code that the library is not written or supported by Pushover. All references to our product or service should be written as Pushover with a capital

Our desktop app running in Chrome/Firefox/Safari plays sounds when presenting notifications.  If you do not hear sounds when receiving popup/desktop notifications, first make sure the sound icon is enabled:

If it's greyed out, click it to enable sounds.  Next, ensure that the browser has allowed the client.pushover.net site to auto-play sounds.  In Chrome and Firefox, click the icon to the left of the URL bar and you should see site-specific settings:

If you do not see a setting for Sound, click Site settings and then change Sound to Allow.  You may then be asked to reload the page for these

No, Pushover's API only integrates with our branded iPhone/iPad, Android, and Desktop client apps and is designed to be a complete, end-to-end solution for individuals and organizations needing to send notifications out, and receive them on their own devices.

Unlike wholesale notification providers like Urban Airship or Parse, who provide an API to handle dispatching bulk notifications through Apple and Google servers to be received by your own iPhone and Android apps, Pushover only works with our own apps and we cannot send notifications to other mobile apps.

Additionally, our service cannot be integrated into other websites to push notifications

On the first of each month at midnight Central Time, all application usage limits reset back to the free allowance of 10,000 messages. Once an application has sent 10,000 messages in a month, it will receive an error from our API and will no longer be able to send messages until the first of the next month when the allowance resets.

For high-volume applications that need to send more than 10,000 messages per month, additional capacity can be purchased from our website (10,000 for $50.00 USD, 25,000 for $115.00 USD, 50,000 for $200.00 USD, 100,000 for $300.00 USD, 500,000 for

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 - iPhone/iPad app" as the request type and then include all of the relevant information in the Message field such as your steps for

Our Pushover for Desktop web application has built-in error handling, so in most cases you will be redirected to a page where you can submit your bug report when an error happens.

Enable Debugging

If there is a problem loading the desktop application and your screen is stuck on "Loading messages, please wait", there may be a larger problem that our application was not able to handle.  In this case, please enable debugging by visiting this address in a new tab:

https://client.pushover.net/?debug=1

After a few seconds, if the "Loading messages" screen does not go away, you will need to open

Pushover's API and Delivery Groups support restricting messages to be sent to a specific device (or multiple specific devices) on a user's account, rather than sending it to all devices which we do by default.

When the device being specified in the device parameter through our API or the device column in a delivery group does not exist, has been renamed, or has been temporarily disabled, messages being sent to that user will instead be directed to all other active devices on the user's account.

This behavior is by design so the message to the user is not lost, and

We require all users to confirm their e-mail addresses in order to register for Applications/API tokens so that we can ensure we have a way of contacting users if problems arise with their applications.

If you do not receive a welcome e-mail when you initially create your Pushover account, please check your e-mail Spam folder.  If the message arrived there, please click "Not Spam" or a similar button to continue receiving e-mails from Pushover in the future.

In order for users of Hotmail/Outlook.com/Live.com to receive e-mails from Pushover, you will need to first add support@pushover.net as a "Safe Sender" on

To send multi-line notifications with line-breaks, send regular newline ("\n", ASCII 10) characters in your message. Your library or programming language may not interpret "\n" characters properly inside strings and may send them as a literal backslash and "n". In those cases, you may need to use your language's chr() or similar function to represent a single character with ASCII value 10.

When using curl in shell scripts, you may find it easiest to just insert literal line breaks in your file:

Pushover's Featured Public Applications page provides our users with a list of applications, plugins, websites, and services that provide Pushover support and integrate with our API.

To get your application listed, it must follow these guidelines:

• The resource must be publicly available (i.e., not an internal company application). You may charge money for the app, plugin, or service, but you cannot charge extra for Pushover functionality.
• For externally hosted services, you must use one API token per service/application and you are responsible for purchasing additional capacity as needed. You may not register multiple API token to get around our message

We use bcrypt for one-way password hashing. For device identifiers, we create a one-way hash of a stable device identifier available from the operating system together with a randomly generated identifier specific to each Pushover account. We do not use "UDIDs", advertising IDs, or other cross-app personal identifiers.

Access to our servers and databases is tightly controlled, logged, and monitored. Encrypted backups of our entire systems with separate database snapshots are done off-site every day. For increased security and privacy, we do not backup the contents of the temporary message queue database table (but we do backup all of the

Pushover currently supports TOTP-based two-factor authenticaiton (2FA) for all accounts.

When logged in, visit your Settings page. Enter your current account password, check the box for "Setup Two-Factor Auth", and then click "Save Account Settings".

You'll be given instructions for the setup of two-factor authentication for your account, which includes scanning a QR code in your 2FA application (or manually entering the secret).  You will be given a list of recovery codes which you must write down and securely store somewhere.

Important Account Recovery Information

Enabling two-factor authentication on your account requires a current code from your 2FA application/device every

Each application that uses Pushover's API must be registered to receive its own API token. For most users, this API token will be kept secret in your own application, script, or website and you will be able to monitor and restrict its use.

For those distributing software that is installed and managed by your end-users, such as libraries and open source projects that use Pushover's API, each user must register their own application and then enter that unique API token in their copy of your software. This way each user will get their own monthly quota of messages without being

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

Pushover is a service of Pushover, LLC (formerly Superblock, LLC), a private, independently-financed software development company based out of Chicago, Illinois.

We have been developing and supporting Pushover since March 2012 when we first released our apps to the App Store and Google Play (then called Android Market). We introduced Pushover for Desktop in April 2014.