OmniPUSH API

Name: OmniPUSH API
Brand: OmniPUSH API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbasic16 EndpointsREST

For Agents

Run sales-outreach campaigns and manage message templates and trigger hooks for the OmniPUSH remote-sales platform.

Install Jentic One Beta

Connect the OmniPUSH API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OmniPUSH 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 OmniPUSH API.

Create OmniPUSH user accounts and mint per-user API keys

Create and update outbound campaigns with associated message templates

Start and stop a running campaign without deleting it

List, retrieve, and delete campaigns by ID

GET STARTED

Start building with OmniPUSH API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for OmniPUSH API, keeping it validated and agent-ready. The OmniPUSH API is the integration layer for the OmniPUSH SaaS platform aimed at remote sales professionals, exposing campaign management, message templates, hooks (trigger webhooks), and a small user-management surface. It exposes 16 endpoints covering user creation and API-key minting, campaign CRUD with start/stop control, message-template management, and hook creation, deletion, and authentication testing. Authentication uses HTTP Basic.

Use Cases

Patterns agents use OmniPUSH API for, with concrete tasks.

★ Outreach Campaign Lifecycle

Sales-ops teams use POST /campaign to create a new campaign, GET /campaign/list to see what's running, and PUT /campaign/start_stop to pause or resume campaigns based on engagement signals. DELETE /campaign/{id} cleans up campaigns that have run their course.

Create a campaign via POST /campaign with a template ID and target list, monitor via GET /campaign/list, then PUT /campaign/start_stop to pause when daily quota is hit.

Template Library Management

Reusable cold-outreach copy lives in OmniPUSH templates. POST /message_template adds a new variant, PUT /message_template updates an existing one, and DELETE /message_template/{id} retires the ones that no longer convert. Templates can be assigned to multiple campaigns at once.

POST a new template with subject, body, and merge tags via /message_template, then attach it to two existing campaigns via PUT /campaign.

Event-Driven Campaign Triggers via Hooks

Hooks let external systems trigger campaign actions when events occur (a new CRM lead, a closed deal). POST /hook creates the hook, GET /hook/auth/test verifies the API key works, and POST /hook/test fires a fake payload so you can validate the hook's behaviour before connecting a live event source.

POST /hook with the trigger URL and campaign ID, then POST /hook/test with a fake lead payload to verify the campaign action fires.

AI Agent Sales Operations Assistant

An AI agent integrated through Jentic can run an entire outreach loop — pause a campaign that's over its quota, create a new template variant from a sample email, and resume a different campaign — without holding the OmniPUSH credentials. Jentic stores the basic-auth pair and injects them at execution time.

Search Jentic for 'pause omnipush campaign', load PUT /campaign/start_stop, and execute it for campaign ID 712 with action=stop.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for omnipush api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/campaign

Create a campaign

PUT

/campaign/start_stop

Start or stop a campaign

POST

/message_template

Create a reusable message template

POST

/hook

Create a trigger hook

POST

/hook/test

Test a hook with a fake payload

GET

/user/api_key

Generate an API key for the current user

POST

/campaign

Create a campaign

PUT

/campaign/start_stop

Start or stop a campaign

POST

/message_template

Create a reusable message template

POST

/hook

Create a trigger hook

POST

/hook/test

Test a hook with a fake payload

GET

Why Jentic?

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

Credential isolation

OmniPUSH uses HTTP Basic with a per-user API key. Jentic stores the basic-auth pair encrypted in MAXsystem and injects it at execution. Agents never see the raw API key.

Intent-based discovery

Agents search Jentic for 'pause omnipush campaign' or 'create omnipush template' and Jentic returns the matching campaign or template operation with its input schema typed.

Time to first call

Direct integration: 1-2 days to model campaign-template-hook relationships and basic-auth setup. Through Jentic: under an hour — search, load, execute.

FAQs

Specific to using OmniPUSH API through Jentic.

Why is there no official OpenAPI spec for OmniPUSH API?

OmniPUSH does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call OmniPUSH API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the OmniPUSH API use?

OmniPUSH uses HTTP Basic authentication with the per-user API key obtained from GET /user/api_key. Jentic stores the basic-auth pair in its encrypted vault and injects it on each call so agents reference only a credential handle.

Can I pause and resume a campaign without deleting it?

Yes. PUT /campaign/start_stop with the campaign ID and an action of 'start' or 'stop' toggles run state without losing campaign config. This is the recommended pattern for daily quota or pause-while-investigating flows.

What are the rate limits for the OmniPUSH API?

Rate limits are not declared in the OpenAPI spec. The campaign list and message-template list endpoints are intended for periodic queries — use them sparingly when monitoring rather than polling on a per-second cadence.

How do I test a trigger hook before connecting it live through Jentic?

Search Jentic for 'test omnipush hook', and the SDK returns POST /hook/test. Pass a fake payload that mirrors your real CRM event, and inspect the campaign action that fires before connecting the live source.

Does OmniPUSH provide email or SMS sending directly?

The Hook and Campaign endpoints orchestrate outreach actions configured inside OmniPUSH; the API itself does not expose direct email or SMS send operations. Outbound channel delivery is handled by OmniPUSH's underlying integrations.

OmniPUSH API

Connect the OmniPUSH API to your agent

Capabilities

Start building with OmniPUSH API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs