Migrate from Pushover to PushPiper: same endpoints, parameters and responses, switch the host and keys in a few minutes, free for 10,000 messages

Five steps

Sign in on your devices. Open pushpiper.com/app on each phone and computer, sign in and allow notifications. Reuse your Pushover device names so device targeting keeps working.
Create your apps. Make one PushPiper app for each Pushover app, with the same name and icon. Each one gets a new API token.
Change the host and keys. Replace api.pushover.net with api.pushpiper.com, and swap in your PushPiper app token and user key.
Recreate your groups. Create them in the app or with the Groups API, then send to the new group keys.
Test, then retire the old keys. Run both side by side for a day if you like, then delete the Pushover credentials.

Change the host

Only the host changes. Paths, parameters and responses stay the same:

Before and after

https://api.pushover.net/1/messages.json
https://api.pushpiper.com/1/messages.json

To swap the host across a whole project:

grep -rl "api.pushover.net" . | xargs sed -i 's/api\.pushover\.net/api.pushpiper.com/g'

grep -rl "api.pushover.net" . | xargs sed -i '' 's/api\.pushover\.net/api.pushpiper.com/g'

What changes and what stays

Pushover	PushPiper	Action
`api.pushover.net`	`api.pushpiper.com`	Change
App tokens	New PushPiper app tokens	Change
User and group keys	Your PushPiper user key and new group keys	Change
Parameters, priorities and sounds	The same	Keep
Receipts, callbacks and cancel by tag	The same	Keep
Your 64-character E2EE key	The same key, added in the PushPiper app	Keep
Email address at pomail.net	A new address at pushpiper.app	Change
Subscribe URLs	`pushpiper.com/subscribe/...`	Change

Tools with a built-in Pushover integration

Many tools ship a Pushover integration that's locked to api.pushover.net, so changing a URL isn't an option there. Use the tool's own webhook or REST support instead. Each guide has a config you can paste:

Home Assistant: a RESTful notify service instead of the Pushover integration.
Uptime Kuma: the Webhook notification with a custom body.
Grafana: a webhook contact point with a custom payload.
n8n: the HTTP Request node instead of the Pushover node.
Apprise: a json:// or form:// URL instead of pover://.
GitHub Actions: a curl step instead of a Pushover action.

Subscribers

Pushover subscribers belong to Pushover accounts, so they need to subscribe again through your PushPiper subscribe URL. Share the new link where the old one lived, and keep sending to both until the new list fills up.

Questions and answers

Do my Pushover keys work on PushPiper?

No, keys belong to each service. Create an app on PushPiper for a new token and use your PushPiper user key. The format is identical, so key validation in your code keeps working.

Do Pushover libraries work?

Yes, if they let you set the API URL or host. For libraries that hardcode api.pushover.net, a plain HTTP POST takes a few lines: see the quickstart.

Can I run Pushover and PushPiper side by side?

Yes. Send to both until you've checked every script, then remove the Pushover credentials.

Do emergency alerts work the same way?

Yes. Priority 2 with retry, expire, receipts, callbacks and cancel by tag behaves the same. PushPiper can't send iOS critical alerts that break through Do Not Disturb yet.

Is there an email gateway like Pushover has?

Yes. Every user gets an address at pushpiper.app that turns email into notifications, with aliases for their own priority and sound. The first image attachment comes along, so camera snapshots work like they do on Pushover. Point anything that mailed your pomail.net address at the new one.

What does it cost?

Nothing for up to 10,000 messages a month on 10 devices. Pro is €4 a month or €40 a year for 50,000 messages.

Move from Pushover in a few minutes