Install Jentic One Beta

Connect the PushEngage API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PushEngage 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%2Fpushengage.com%2Fpushengage" | sh

Step 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%2Fpushengage.com%2Fpushengage" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with PushEngage API.

Send notification

Schedule notification

List notifications

Get subscriber

Add subscriber to segment

GET STARTED

Start building with PushEngage API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PushEngage API for, with concrete tasks.

★ Marketing Operations

Use the PushEngage API to perform marketing operations programmatically. The API provides 10 endpoints covering core functionality including send notification, schedule notification, list notifications.

Call POST /apiv1/notifications/send to send notification

Automated Analytics Management

Automate analytics operations by combining multiple PushEngage API endpoints. Agents can schedule notification and then list notifications in a single workflow.

Call POST /apiv1/notifications/schedule to schedule notification, then verify the result

AI Agent Integration via Jentic

AI agents discover and call PushEngage 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 'send notification', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

10 endpoints — pushengage push notifications api for managing subscribers, segments, notifications, and campaigns.

METHOD

PATH

DESCRIPTION

POST

/apiv1/notifications/send

Send notification

POST

/apiv1/notifications/schedule

Schedule notification

GET

/apiv1/notifications

List notifications

GET

/apiv1/subscribers

List subscribers

GET

/apiv1/subscribers/{subscriberHash}

Get subscriber

POST

/apiv1/subscribers/{subscriberHash}/segments

Add subscriber to segment

POST

/apiv1/segments

Create segment

GET

/apiv1/segments

List segments

POST

/apiv1/notifications/send

Send notification

POST

/apiv1/notifications/schedule

Schedule notification

GET

/apiv1/notifications

List notifications

GET

/apiv1/subscribers

List subscribers

GET

/apiv1/subscribers/{subscriberHash}

Get subscriber

POST

/apiv1/subscribers/{subscriberHash}/segments

Add subscriber to segment

POST

/apiv1/segments

Create segment

GET

/apiv1/segments

List segments

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring PushEngage by hand means sending its X-API-Key header on every request and handling notification, subscriber, and segment calls yourself. Through Jentic you install once, import the PushEngage API from the API Directory, store the key once, and your agent calls it.

Permission scoping

PushEngage puts the subscriber hash in the URL path (/apiv1/subscribers/{subscriberHash}), so a rule can pin your agent to one subscriber: it can read that subscriber or add it to a segment and nothing else. You choose the operations it may call, so sending or scheduling notifications is not included unless you add it.

Credential isolation

Your PushEngage key 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 'send a push notification' or 'create a subscriber segment', and Jentic returns the matching PushEngage operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PushEngage API through Jentic.

What authentication does the PushEngage API use?

The PushEngage API uses an API key passed in the `X-API-Key` 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 notification with the PushEngage API?

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

What are the rate limits for the PushEngage 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 notification through Jentic?

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

How many endpoints does the PushEngage API have?

The PushEngage API exposes 10 endpoints covering analytics, notifications, segments operations.

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

Yes. Because you run Jentic One yourself, you decide which PushEngage operations your agent may call, so sending or scheduling notifications is excluded unless you add it. Since PushEngage puts the subscriber hash in the URL path (/apiv1/subscribers/{subscriberHash}), you can pin the agent to a single subscriber, letting it read that subscriber or add it to a segment and nothing more. Your own rules and stored credentials govern every call the agent is allowed to make.

PushEngage API

Name: PushEngage API
Brand: PushEngage API
Availability: InStock

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail MarketingapiKey10 EndpointsREST

For Agents

Programmatically send notification, schedule notification. Covers 10 operations with apiKey authentication.

Use for: I need to send notification, I want to schedule notification, Search for notifications, Find all subscribers

Not supported: Does not handle payments, communications, or crm - use for marketing only.

PushEngage push notifications API for managing subscribers, segments, notifications, and campaigns. The API exposes 10 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

48%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PushEngage API to your agent

Capabilities

Start building with PushEngage API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PushEngage API

Jentic AI Readiness Score

PushEngage API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness