> ## Documentation Index
> Fetch the complete documentation index at: https://docs.uptimeio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pushover

> Send monitor alerts as push notifications to your phone with Pushover

The Pushover destination sends alerts to the Pushover app on your devices. You need a Pushover account and your **user key**.

## Connect Pushover

<Steps>
  <Step title="Get your user key">
    Install the Pushover app and sign in. Your **User Key** is shown on your Pushover account page.
  </Step>

  <Step title="Open Destinations">
    Click **Destinations** in the sidebar, then **Add Destination**, then choose **Pushover**.
  </Step>

  <Step title="Enter the keys">
    | Field | Required | Description |
    | - | - | - |
    | **User key** | Yes | Exactly 30 letters and digits. |
    | **API token** | No | The token of your own Pushover application, exactly 30 letters and digits. Leave empty to send through UptimeIO's shared application. |
  </Step>

  <Step title="Choose events and save">
    Toggle which events are pushed (all are enabled by default; at least one must stay enabled), use **Test** to send a test notification, then assign the destination to monitors in each monitor's **Notifications** section.
  </Step>
</Steps>

<Note>
  Pushover destinations can only be set up from the dashboard. An API key cannot create one: `POST /api/integrations` with `"type": "PUSHOVER"` returns `403` with code `JWT_REQUIRED` and the message `Pushover and Telegram integrations can only be set up from the dashboard. Sign in to the dashboard and add the integration there.` Once it exists, you can [assign it to monitors through the API](/api-reference/monitors/update) with `notification_target_ids`.
</Note>

<Tip>
  Pushover works well for on-call alerts. Enable only "Monitor goes down" and "Monitor recovers" to keep your phone quiet.
</Tip>

## Events

| Event | Preference key |
| - | - |
| Monitor goes down | `on_failure` |
| Monitor recovers | `on_recovery` |
| SSL certificate warnings | `on_ssl_expiry` |
| Domain expiry warnings | `on_domain_expiry` |
| Response time exceeds threshold | `on_slow_response` |
| Response time returns to normal | `on_slow_response_resolved` |

## Troubleshooting

| Issue | Solution |
| - | - |
| "Pushover user key must be exactly 30 characters" or "Invalid Pushover user key format. Expected 30 alphanumeric characters" | Copy the key again from your Pushover account page without spaces. A user key is exactly 30 letters and digits. |
| "Pushover application token must be exactly 30 characters" or "Invalid Pushover application token format. Expected 30 alphanumeric characters" | Copy the token again from your Pushover application page, or leave the field empty to use UptimeIO's shared application. |
| No push arrives | Confirm the destination is assigned to the monitor, the event is enabled, and the Pushover app is signed in on your device. |

## Next steps

<CardGroup cols={2}>
  <Card title="Setting Up Alerts" icon="bell" href="/essentials/setting-up-alerts">
    Assign destinations to monitors
  </Card>

  <Card title="Telegram" icon="paper-plane" href="/integrations/telegram">
    Alerts in a Telegram chat
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.