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

# Pushwoosh Messages API

The Pushwoosh Messages API enables creating, managing, and tracking push notifications. It supports multi-platform push delivery (iOS, Android, Web, etc.) with rich customization options including templates, targeting, scheduling, and platform-specific parameters. The API exposes 6 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a push notification, delete a push notification. Covers 6 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create a push notification
- Delete a push notification
- Get message details
- Cancel a scheduled message

## Use cases

### Communications Operations

Use the Pushwoosh Messages API to perform communications operations programmatically. The API provides 6 endpoints covering core functionality including create a push notification, delete a push notification, get message details.

Example prompt: Call POST /createMessage to create a push notification

### Automated Cancelmessage Management

Automate cancelmessage operations by combining multiple Pushwoosh Messages API endpoints. Agents can delete a push notification and then get message details in a single workflow.

Example prompt: Call POST /deleteMessage to delete a push notification, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Pushwoosh Messages 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 'create a push notification', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/createMessage` | Create a push notification |
| POST | `/deleteMessage` | Delete a push notification |
| POST | `/getMessageDetails` | Get message details |
| POST | `/createTargetedMessage` | Create a targeted push notification |
| POST | `/getPushHistory` | Get push history |
| POST | `/cancelMessage` | Cancel a scheduled message |

## Key resources

- **Cancelmessage** — Operations for cancelMessage
- **Createmessage** — Operations for createMessage
- **Createtargetedmessage** — Operations for createTargetedMessage
- **Deletemessage** — Operations for deleteMessage
- **Getmessagedetails** — Operations for getMessageDetails

## Why Jentic

- **Setup:** Wiring the Pushwoosh Messages API by hand means sending your auth token in the Authorization header and posting each message and history call yourself. Through Jentic you install once, import the Pushwoosh Messages API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Pushwoosh takes its message and targeting details in the request body rather than as path resources, so scope the agent to the operations it needs, such as creating a message or reading push history. You choose that allowed set, so deleting or cancelling messages is not included unless you add it.
- **Credential handling:** Your Pushwoosh 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 'create a push message' or 'get push history', and Jentic returns the matching Pushwoosh 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 Pushwoosh Messages API use?

The Pushwoosh Messages API uses an API key passed 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 create a push notification with the Pushwoosh Messages API?

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

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

### How many endpoints does the Pushwoosh Messages API have?

The Pushwoosh Messages API exposes 6 endpoints covering cancelmessage, createmessage, createtargetedmessage operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Pushwoosh operations and credentials the agent may use. Pushwoosh passes its message and targeting details in the request body rather than as path resources, so you scope the agent to just the operations it needs, such as creating a message with createMessage or reading push history with getPushHistory. Destructive calls like deleteMessage or cancelMessage stay out of that allowed set unless you explicitly add them.