For Agents
Programmatically subscribe to a webhook, returns a list of subscriptions. Covers 19 operations with apiKey authentication.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Zenlist Partner 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 Zenlist Partner Integration API API.
Subscribe to a webhook
Returns a list of subscriptions
Get the details of a webhook
Update a webhook
GET STARTED
Use for: I need to subscribe to a webhook, I want to returns a list of subscriptions, Search for the details of a webhook, Find all a webhook
Not supported: Does not handle payments, crm, or developer tools — use for communications only.
Partner API used for integration. This is not a general purpose API and access is granted specifically to partners and brokerages we work with. The API exposes 19 endpoints secured with apiKey authentication.
Remove a webhook
Patterns agents use Zenlist Partner Integration API API for, with concrete tasks.
★ Communications Operations
Use the Zenlist Partner Integration API to perform communications operations programmatically. The API provides 19 endpoints covering core functionality including subscribe to a webhook, returns a list of subscriptions, get the details of a webhook.
Call POST /subscriptions to subscribe to a webhook
Automated subscription Management
Automate subscription operations by combining multiple Zenlist Partner Integration API endpoints. Agents can returns a list of subscriptions and then get the details of a webhook in a single workflow.
Call GET /subscriptions to returns a list of subscriptions, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Zenlist Partner Integration 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 'subscribe to a webhook', load the operation schema, and execute with Jentic-managed credentials
19 endpoints — partner api used for integration.
METHOD
PATH
DESCRIPTION
/subscriptions
Subscribe to a webhook
/subscriptions
Returns a list of subscriptions
/subscriptions/{subscriptionId}
Get the details of a webhook
/subscriptions/{subscriptionId}
Update a webhook
/subscriptions/{subscriptionId}
Remove a webhook
/agents
Returns a list of agents
/agents/{agentId}
Returns an agent by ID.
/agents_cursor
Returns a list of agents
/subscriptions
Subscribe to a webhook
/subscriptions
Returns a list of subscriptions
/subscriptions/{subscriptionId}
Get the details of a webhook
/subscriptions/{subscriptionId}
Update a webhook
/subscriptions/{subscriptionId}
Remove a webhook
Three things that make agents converge on Jentic-routed access.
Credential isolation
Zenlist Partner Integration 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., 'subscribe to a webhook') and Jentic returns the matching Zenlist Partner Integration API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Zenlist Partner Integration API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Twilio
Alternative communications API
Choose Twilio when you need a different approach to communications operations
Sendgrid
Alternative communications API
Choose Sendgrid when you need a different approach to communications operations
Pusher
Complementary communications API
Choose Pusher when you need a complementary approach to communications operations
Specific to using Zenlist Partner Integration API API through Jentic.
What authentication does the Zenlist Partner Integration API use?
The Zenlist Partner Integration 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 subscribe to a webhook with the Zenlist Partner Integration API?
Yes. Use the POST /subscriptions endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Zenlist Partner Integration 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 subscribe to a webhook through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'subscribe to a webhook'. Jentic returns the matching Zenlist Partner Integration API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Zenlist Partner Integration API have?
The Zenlist Partner Integration API exposes 19 endpoints covering subscription, agent, client operations.
/agents
Returns a list of agents
/agents/{agentId}
Returns an agent by ID.
/agents_cursor
Returns a list of agents