Including an open source application's API token in its source code

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 affected by other users. For popular applications listed on our Featured Public Applications page, we can enable a special cloning URL that you can direct users to that will simplify this registration process for them.

Please note, this does not apply to SaaS/hosted applications.  If you are managing a service or application for multiple users, you may only use one API token and you are not permitted to store or use API tokens registered by end-users.

For example, users setting up irssi can be directed to https://pushover.net/apps/clone/irssi which will automatically clone the app's icon, description, and URL. The user just has to confirm the terms of service, click a button, and they can easily get their own API token to copy and paste into the irssi plugin configuration. For developers looking to get this functionality with their apps, please register your own application and set a proper description and icon, and then contact us with the details of what your application does, how it integrates with Pushover, and the API token you have registered that you would like to be made cloneable.

If you are providing a free service that uses Pushover where you are still in control of your API token (such as a website or server-side app that you run), contact us to inquire about getting a free upgrade of your permitted monthly notifications.