Send alerts to a Gotify server

Send Uptime Tracker alerts to your self-hosted Gotify server. Create a Gotify application, copy its token and add the destination on Pro or Team.

Updated By the Uptime Tracker team
  1. Create a Gotify applicationIn your Gotify web UI, open Apps, choose Create Application, name it "Uptime Tracker" and copy its token.
  2. Add the destinationIn Integrations → Add destination, choose "Set up Gotify". Enter the Gotify server URL (the HTTPS root) and the Application token.
  3. Save and testChoose "Add destination", then "Send test", and check the Gotify app.

Gotify is a self-hosted push notification server. Uptime Tracker posts each alert as a Gotify message. Gotify destinations are available on the Pro and Team plans.

Before you start

  • A workspace on Pro or Team.
  • A Gotify server reachable from the internet over HTTPS, at the root of its host name (https://gotify.example.com) or under a sub-path (https://example.com/gotify). Servers on private networks and plain HTTP are not supported.

Create an application token in Gotify

  1. Sign in to your Gotify web UI and open Apps.
  2. Choose Create Application, enter a name such as "Uptime Tracker" and create it.
  3. Reveal and copy the application's token. Use an application token, not a client token.

Add it in Uptime Tracker

  1. Go to Integrations → Add destination, find Gotify and choose Set up Gotify.
  2. Enter a Name and the Gotify server URL: the address you open the Gotify web UI at, such as https://gotify.example.com or https://example.com/gotify, without /message or a query string.
  3. Paste the Application token. It is stored encrypted and never shown again.
  4. Choose Add destination, then Send test.

What you receive

Down, reminder and escalation alerts are sent with priority 8, which most Gotify clients show as a high-priority notification, and include a Reason: line such as HTTP 503 Service Unavailable. Recoveries, acknowledgements and tests are sent with priority 4.

Change the server or token

Choose Edit connection on the destination, enter a new server URL and/or application token, and choose Save connection. The values are checked like a new destination, and saving re-enables a destination that was disabled after delivery failures.

Troubleshooting

  • "The endpoint is not a valid gotify URL": enter the server's base address only. Remove /message, any query string (such as ?token=), .. segments and percent-encoded characters; a sub-path may have up to 5 segments.
  • HTTP 401 or 403 under Integrations → Deliveries: the token is wrong or belongs to a client rather than an application. The destination is disabled; enter an application token with Edit connection, which re-enables it.
  • HTTP 404 under Integrations → Deliveries: the server URL is missing its sub-path, so /message was not found. Correct it with Edit connection.
  • "Destination must be a publicly routable HTTPS endpoint": the host name resolves to a private address, or the server does not offer HTTPS.
FAQ

Frequently asked questions

Can Uptime Tracker reach a Gotify server on my home network?

Only if it is published on the internet over HTTPS. Private and internal addresses are refused for security.

Which token do I need?

An application token from the Apps tab in Gotify. Client tokens can only read messages.

Which plan includes Gotify?

Pro and Team.

Uptime Tracker

Start monitoring in under five minutes

Start on the free plan — commercial use allowed. No credit card required.

  • Free forever plan
  • No credit card
  • Cancel anytime