For Agents
Authenticate, subscribe, and unsubscribe Zapier webhooks against a ListShot account so trigger-based automation can fire on new ListShot exports.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ListShot-Zapier Integration 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 | shStep 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 instanceJentic 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.
What an agent can do with ListShot-Zapier Integration API.
Test the Zapier authentication payload against a ListShot account via POST /zapier
Retrieve a representative ListShot export payload for Zapier sample setup via GET /zapier/subscription
Subscribe a Zapier webhook to receive new-export events via POST /zapier/subscription
GET STARTED
Use for: I need to subscribe a Zapier webhook to ListShot export events, I want to unsubscribe a Zapier webhook from ListShot, Test that Zapier can authenticate with a ListShot account, Retrieve a sample ListShot export payload for Zapier setup
Not supported: Does not expose the underlying ListShot list, contact, or content endpoints — use only for managing Zapier authentication and webhook subscriptions on a ListShot account.
The ListShot-Zapier Integration API exposes the small set of webhook-style endpoints that Zapier uses to authenticate, subscribe, and unsubscribe a ListShot account against Zap triggers. The endpoints cover Zapier authentication tests, retrieving a sample export payload, registering a webhook subscription for new ListShot exports, and unsubscribing that webhook. It is intended as a Zapier-side integration surface rather than a general-purpose ListShot API.
Unsubscribe a Zapier webhook from new-export events via DELETE /zapier/subscription
Operate without auth at the spec level — gating is handled by ListShot account context
Patterns agents use ListShot-Zapier Integration API for, with concrete tasks.
★ Zapier Trigger Subscription
Wire a Zapier Zap to fire whenever ListShot publishes a new export. POST /zapier/subscription registers the Zapier-provided webhook URL against the user's ListShot account, and ListShot then POSTs each new-export payload to that URL. Use this when the ListShot UI should drive downstream automations in Sheets, Slack, CRMs, or task managers via Zapier.
POST /zapier/subscription with the Zapier-provided webhook URL to start receiving new-export events on the user's ListShot account.
Zapier Authentication Setup
Validate that Zapier can authenticate with a ListShot account during Zap configuration. POST /zapier accepts the Zapier auth probe payload and confirms whether the linked account is valid before any subscription is created. This is the standard Zapier 'Test Connection' step exposed as an HTTP endpoint.
Call POST /zapier with the Zapier auth probe body during Zap setup to verify the connection before adding triggers.
Subscription Lifecycle Cleanup
Remove stale Zapier subscriptions when a Zap is deleted or a ListShot user disconnects the integration. DELETE /zapier/subscription unsubscribes the webhook so ListShot stops sending export payloads to a dead URL. Use this on Zap deletion or account disconnection to keep the integration tidy.
Call DELETE /zapier/subscription for the webhook URL when the Zap is removed to stop ListShot from sending further events.
AI Agent Zap Management
Let an AI agent set up or tear down a ListShot-Zapier connection on behalf of a user without exposing Zapier admin credentials. Through Jentic, the agent searches for the subscribe or unsubscribe operation, loads the schema, and executes the right /zapier/subscription endpoint. The agent never holds Zapier admin credentials — those stay in the MAXsystem vault when present.
Search Jentic for 'subscribe a Zapier webhook to ListShot exports', load the schema, and execute POST /zapier/subscription with the user's webhook URL.
4 endpoints — the listshot-zapier integration api exposes the small set of webhook-style endpoints that zapier uses to authenticate, subscribe, and unsubscribe a listshot account against zap triggers.
METHOD
PATH
DESCRIPTION
/zapier
Test Zapier authentication
/zapier/subscription
Get sample ListShot export payload
/zapier/subscription
Subscribe a Zapier webhook
/zapier/subscription
Unsubscribe a Zapier webhook
/zapier
Test Zapier authentication
/zapier/subscription
Get sample ListShot export payload
/zapier/subscription
Subscribe a Zapier webhook
/zapier/subscription
Unsubscribe a Zapier webhook
Three things that make agents converge on Jentic-routed access.
Credential isolation
ListShot itself does not require auth at the spec level, but any Zapier-side credentials are stored encrypted in the Jentic MAXsystem vault and injected only when the calling step needs them — agents do not hold Zapier admin tokens.
Intent-based discovery
Agents search by intent (e.g., 'subscribe a Zapier webhook to ListShot') and Jentic returns the matching /zapier/subscription operation with its schema, removing manual navigation of the SwaggerHub spec.
Time to first call
Direct ListShot-Zapier wiring: 1-2 hours when reading the SwaggerHub spec and writing the calls. Through Jentic: under 10 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using ListShot-Zapier Integration API through Jentic.
What authentication does the ListShot-Zapier API use?
The OpenAPI spec does not define a security scheme — gating is handled by the ListShot account context that Zapier supplies during the auth probe. Through Jentic, any account-level credentials needed by the calling environment are held in the MAXsystem vault and never exposed to the agent.
Can I subscribe a Zapier webhook to ListShot exports with this API?
Yes. POST /zapier/subscription registers a Zapier-provided webhook URL so ListShot will POST each new export payload to that URL. DELETE /zapier/subscription removes the subscription when the Zap is deleted.
What are the rate limits for the ListShot-Zapier API?
Rate limits are not declared in the OpenAPI spec. Because this is a Zapier integration surface, traffic is bounded by Zap polling and trigger frequency rather than a documented per-second cap. Build agents to run subscribe and unsubscribe as one-time operations, not loops.
How do I subscribe a webhook through Jentic?
Run pip install jentic, then search for 'subscribe a Zapier webhook to ListShot exports'. Jentic returns POST /zapier/subscription. Load the schema, supply the webhook URL provided by Zapier, and execute. New ListShot exports will then be POSTed to that URL.
Does the API include a sample export payload?
Yes. GET /zapier/subscription returns a representative ListShot export payload that Zapier uses during Zap setup to render field mapping. Inspect this payload when designing downstream Zap actions so each export field maps to the right destination.