canonical: https://jentic.com/apis/izooto.com/izooto # iZooto API iZooto is an audience marketing platform that lets publishers and content sites send web push notifications to their subscribers. The 1.0.0 API exposes two operations: a push-send endpoint for delivering notifications to one, many, or all subscribers and a subscriber list endpoint for retrieving the audience. Authentication is by X-Auth-Key header issued in the iZooto console. ## For AI agents Send web push notifications to subscriber segments and retrieve subscriber lists from the iZooto platform. ## Scope Does not handle SMS, mobile push, or email - use for web push notification delivery and subscriber lookup only. ## Capabilities - 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 - Authenticate via the X-Auth-Key header for server-to-server calls ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance. Example prompt: Search Jentic for 'send izooto push', execute POST /notifications with the article details, and confirm the dispatched notification id ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/notifications` | Send or schedule a web push notification | | GET | `/subscribers` | Retrieve the subscriber audience list | ## Key resources - **Notifications** — Send and schedule web push notifications to subscribers - **Subscribers** — Retrieve the audience list for segmentation and reporting ## Why Jentic - **Setup:** Wiring the iZooto API by hand means handling its X-Auth-Key header and the notification and subscriber endpoints yourself. Through Jentic you install once, import iZooto from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** iZooto takes the notification payload in the request body, so scope by operation: limit the agent to the operations it needs, such as sending a web push notification or listing subscribers. You pick the allowed set, so it stays within web push delivery and subscriber lookup. - **Credential handling:** Your iZooto API key is stored once, encrypted, by your own Jentic One instance and injected into the request header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a web push notification' or 'list iZooto subscribers', and Jentic returns the matching iZooto operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **OneSignal API** — Cross-platform push notification service covering web, mobile, and email - **Pushwoosh API** — Multi-channel customer engagement and push delivery - **Pusher API** — Realtime channels for in-page updates that pair with push for off-site reach - **SendGrid API** — Transactional email channel that complements web push for off-site reach ## FAQ ### 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. ### Can I limit what my agent is allowed to do with the iZooto API? Yes. Because you self-host Jentic One, your own rules decide which iZooto operations the agent may call and which credentials it may use. The iZooto API exposes just two operations, sending a web push notification through POST /notifications and listing the audience through GET /subscribers, so you can grant one without the other, for example allowing read-only subscriber lookup while blocking sends. The X-Auth-Key is held by your Jentic One instance and injected at request time, so the agent operates only within the operation set you approve.