Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pushwoosh Messages API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpushwoosh.com%2Fpushwoosh" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpushwoosh.com%2Fpushwoosh" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Pushwoosh Messages API.
Create a push notification
Delete a push notification
Get message details
Cancel a scheduled message
Patterns agents use Pushwoosh Messages API for, with concrete tasks.
GET STARTED
★ 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.
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.
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.
Search Jentic for 'create a push notification', load the operation schema, and execute with Jentic-managed credentials
6 endpoints — the pushwoosh messages api enables creating, managing, and tracking push notifications.
METHOD
PATH
DESCRIPTION
/createMessage
Create a push notification
/deleteMessage
Delete a push notification
/getMessageDetails
Get message details
/createTargetedMessage
Create a targeted push notification
/getPushHistory
Get push history
/cancelMessage
Cancel a scheduled message
/createMessage
Create a push notification
/deleteMessage
Delete a push notification
/getMessageDetails
Get message details
/createTargetedMessage
Create a targeted push notification
/getPushHistory
Get push history
/cancelMessage
Cancel a scheduled message
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Pushwoosh Messages API through Jentic.
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.
For Agents
Programmatically create a push notification, delete a push notification. Covers 6 operations with apiKey authentication.
Use for: I need to a push notification, I want to a push notification, Search for message details, Find all a targeted push notification
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
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.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>