canonical: https://jentic.com/apis/pushover.net/pushover

# Pushover API

Pushover API for sending real-time notifications to Android, iOS, and desktop devices. Includes message sending, user/group validation, group management, emergency receipt tracking, glances, and subscription management. The API exposes 17 endpoints secured with apiKey authentication.

## For AI agents

Programmatically send a push notification, validate a user or group key. Covers 17 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Send a push notification
- Validate a user or group key
- List available notification sounds
- Get application message limits
- Cancel an emergency priority notification

## Use cases

### Communications Operations

Use the Pushover API to perform communications operations programmatically. The API provides 17 endpoints covering core functionality including send a push notification, validate a user or group key, list available notification sounds.

Example prompt: Call POST /messages.json to send a push notification

### Automated Messages Management

Automate messages operations by combining multiple Pushover API endpoints. Agents can validate a user or group key and then list available notification sounds in a single workflow.

Example prompt: Call POST /users/validate.json to validate a user or group key, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Pushover API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'send a push notification', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /messages.json | Send a push notification |
| POST | /users/validate.json | Validate a user or group key |
| GET | /sounds.json | List available notification sounds |
| GET | /apps/limits.json | Get application message limits |
| GET | /receipts/{receipt}.json | Get emergency notification receipt status |
| POST | /receipts/{receipt}/cancel.json | Cancel an emergency priority notification |
| POST | /receipts/cancel_by_tag/{tag}.json | Cancel emergency notifications by tag |
| POST | /groups.json | Create a new group |

## Key resources

- **Messages** — Push notification message operations
- **Users** — User and group validation
- **Groups** — Group management operations
- **Receipts** — Emergency priority receipt and callback operations
- **Glances** — Glance data updates for smartwatch and widget displays

## Why Jentic

- **Setup:** Wiring Pushover by hand means passing its token on every query string and handling message, receipt, and group calls yourself. Through Jentic you install once, import the Pushover API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Pushover sends messages from the request body and identifies receipts and tags per call, so scope the agent to the operations it needs, such as sending a message or checking a receipt. You choose that allowed set, so cancelling receipts is not included unless you add it.
- **Credential handling:** Your Pushover token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a push notification' or 'check a message receipt', and Jentic returns the matching Pushover operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Pushover API use?

The Pushover API uses an API key passed in the `token` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I send a push notification with the Pushover API?

Yes. Use the POST /messages.json endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Pushover API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I send a push notification through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send a push notification'. Jentic returns the matching Pushover API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Pushover API have?

The Pushover API exposes 17 endpoints covering messages, users, groups operations.

### Can I limit what my agent is allowed to do with the Pushover API?

Yes. Because Jentic One is self-hosted, your own rules decide which Pushover operations and credentials the agent may use, so you can allow only what it needs, such as sending a message with POST /messages.json or checking a receipt with GET /receipts/{receipt}.json. Since messages are sent from the request body and receipts and tags are identified per call, you can permit sending while withholding actions like cancelling a receipt or creating a group unless you explicitly add them. The stored Pushover token is injected only for the operations you have allowed, keeping the agent inside that boundary.