canonical: https://jentic.com/apis/pushinator.com/pushinator

# Pushinator API

Pushinator provides a simple API to send push notifications to iPhone, iPad, and Android devices directly from your code. It is built around REST principles, accepts and responds with JSON objects. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically send a notification. Covers 1 operations with bearer authentication.

## Scope

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

## Capabilities

- Send a notification
- Access Pushinator API resources via REST API
- Access Pushinator API resources via REST API

## Use cases

### Communications Operations

Use the Pushinator API to perform communications operations programmatically. The API provides 1 endpoints covering core functionality including send a notification.

Example prompt: Call POST `/api/v2/notifications/send` to send a notification

### Data Retrieval and Monitoring

Query Pushinator API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows without manual intervention.

Example prompt: Query the Pushinator API API to retrieve current data and verify the response contains expected fields

### AI Agent Integration via Jentic

AI agents discover and call Pushinator 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 bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v2/notifications/send` | Send a notification |

## Key resources

- **Notifications** — Operations for notifications

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/pushinator.com/pushinator/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Pushinator by hand means setting up its bearer auth and posting to its single notification send endpoint yourself. Through Jentic you install once, import the Pushinator API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Pushinator sends notifications from the request body rather than through a path resource, so scope the agent to the operations it needs, which here is sending a notification. You choose that allowed set, so no operation runs unless you include it.
- **Credential handling:** Your Pushinator 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 notification to a channel', and Jentic returns the matching Pushinator 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 Pushinator API use?

The Pushinator API uses a Bearer token in the Authorization header. 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 notification with the Pushinator API?

Yes. Use the POST `/api/v2/notifications/send` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Pushinator 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 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 notification'. Jentic returns the matching Pushinator API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Pushinator API exposes 1 endpoints covering notifications operations.

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

Yes. Because Jentic One is self-hosted, you define the rules that decide which Pushinator operations and credentials your agent may use. The Pushinator API exposes a single operation, POST `/api/v2/notifications/send`, which sends notifications from the request body rather than a path resource, so you scope the agent to just the send-notification operation and nothing else runs unless you include it. Your bearer token stays with your own Jentic One instance and is injected only for the calls you have allowed.