PushEngage API

Name: PushEngage API
Brand: PushEngage API
Availability: InStock

✓ Official Vendor SpecMarketingEmail MarketingapiKey10 EndpointsREST

For Agents

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

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

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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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

GET STARTED

Start building with PushEngage API

Explore with Jentic

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PushEngage API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'send notification') and Jentic returns the matching PushEngage API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct PushEngage API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

PushEngage API

Connect the PushEngage API to your agent

Capabilities

Start building with PushEngage API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs