iZooto API

Name: iZooto API
Brand: iZooto API
Availability: InStock

✓ Official Vendor SpecCommunicationsPush NotificationsapiKey2 EndpointsREST

For Agents

Send web push notifications to subscriber segments and retrieve subscriber lists from the iZooto platform.

Install Jentic One Beta

Connect the iZooto API to your agent

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

Send a web push notification to a single subscriber, a segment, or the full audience

Schedule a push for a future delivery time using the notification payload

Retrieve the current subscriber list for audience analysis and CRM sync

GET STARTED

Start building with iZooto API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use iZooto API for, with concrete tasks.

★ Breaking News Alerts

Online publishers send breaking news as web push notifications to readers who have opted in. The POST /notifications endpoint accepts a title, message, target URL, and segment filter, delivering to subscribers across Chrome, Firefox, and Edge within seconds. Editorial teams trigger sends directly from the CMS via this single call.

POST /notifications with the article title, summary, and target_url to the 'news' segment when an article is flagged as breaking

Re-Engagement Campaign

Marketing teams re-engage dormant readers with weekly digest pushes targeted by topic interest. The notifications endpoint accepts segment filters so a single send can be scoped to subscribers tagged with a category, and the subscribers endpoint provides the audience size needed to budget the campaign.

GET /subscribers to count the 'sports' segment, then POST /notifications with the weekly digest to that segment

Subscriber List Export to CRM

Publishers consolidate audience data across web push, email, and CRM. Pulling /subscribers on a schedule gives analytics teams a current snapshot of opted-in readers that can be joined with email and on-site behaviour for unified audience reporting.

Schedule GET /subscribers nightly and write the result to the audience warehouse table

AI Agent Notification Send

An AI assistant for an editorial desk monitors the news wire and triggers a push when a breaking story is published. Through Jentic the agent searches for 'send web push notification', loads the POST /notifications schema, and executes with the iZooto X-Auth-Key managed in the Jentic vault.

Search Jentic for 'send izooto push', execute POST /notifications with the article details, and confirm the dispatched notification id

Key Endpoints

2 endpoints — izooto is an audience marketing platform that lets publishers and content sites send web push notifications to their subscribers.

METHOD

PATH

DESCRIPTION

POST

/notifications

Send or schedule a web push notification

GET

/subscribers

Retrieve the subscriber audience list

POST

/notifications

Send or schedule a web push notification

GET

/subscribers

Retrieve the subscriber audience list

Why Jentic?

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

Credential isolation

iZooto X-Auth-Key values are stored encrypted in the Jentic vault. Agents receive scoped execution tokens — the header is injected at request time and never appears in agent context or logs.

Intent-based discovery

Agents search by intent (e.g. 'send web push notification' or 'list izooto subscribers') and Jentic returns matching iZooto operations with their input schemas, so the agent can call the right endpoint without consulting iZooto documentation.

Time to first call

Direct iZooto integration: half a day for key setup, payload modelling, and segment testing. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using iZooto API through Jentic.

What authentication does the iZooto API use?

iZooto uses an X-Auth-Key header issued in the iZooto console. The key is tied to a property and its subscriber audience. Through Jentic the key is stored in the credential vault and injected into the X-Auth-Key header at request time.

Can I send a push notification to a segment with the iZooto API?

Yes. POST /notifications accepts a segment filter on the payload so you can target subscribers tagged with a topic, geography, or behaviour. Without a segment filter the notification is delivered to the full opted-in audience.

What are the rate limits for the iZooto API?

iZooto does not publish numeric rate limits in the spec. Plan large sends as a single POST /notifications call rather than per-subscriber loops, since the platform fans out delivery internally and per-call sends will exhaust account quotas quickly.

Can I schedule notifications for a future time?

Yes. POST /notifications accepts a scheduled-send timestamp in the payload, so the notification is queued and dispatched at the scheduled time. Pass the timestamp in the iZooto-supported format and confirm with the response notification_id.

How do I send a push through Jentic?

Search Jentic for 'send web push notification', load the POST /notifications schema, and execute with the title, message, and target_url. Jentic injects the X-Auth-Key header so the agent only supplies the campaign payload.