canonical: https://jentic.com/apis/zenlist.com/zenlist-partner-integration-api

# Zenlist Partner Integration API

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.

## For AI agents

Programmatically subscribe to a webhook, returns a list of subscriptions. Covers 19 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Subscribe to a webhook
- Returns a list of subscriptions
- Get the details of a webhook
- Update a webhook
- Remove a webhook

## Use cases

### 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.

Example prompt: Call POST /subscriptions to subscribe to a webhook

### Automated agent Management

Automate agent 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.

Example prompt: 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.

Example prompt: Search Jentic for 'subscribe to a webhook', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/subscriptions` | Subscribe to a webhook |
| GET | `/subscriptions` | Returns a list of subscriptions |
| GET | `/subscriptions/{subscriptionId}` | Get the details of a webhook |
| PUT | `/subscriptions/{subscriptionId}` | Update a webhook |
| DELETE | `/subscriptions/{subscriptionId}` | Remove a webhook |
| GET | `/agents` | Returns a list of agents |
| GET | `/agents/{agentId}` | Returns an agent by ID |
| GET | `/agents_cursor` | Returns a list of agents with cursor pagination |

## Key resources

- **agent** — Operations related to agent
- **chat** — Operations related to chat
- **client** — Operations related to client
- **client_invitation** — Operations related to client_invitation
- **event** — Operations related to event

## Why Jentic

- **Setup:** Wiring the Zenlist Partner Integration API by hand means setting its x-api-key header on every request, working through subscription and agent paths on openapi.zenlist.com/v2, and coding cursor paging yourself. Through Jentic you install once, import Zenlist Partner Integration from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Zenlist puts the subscription and agent ids in the URL path (`/subscriptions/{subscriptionId}` and `/agents/{agentId}`), so a rule can pin your agent to one subscription or one agent record. You choose the operations it may call, so deleting a subscription is not included unless you add it.
- **Credential handling:** Your Zenlist key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a webhook subscription' or 'look up an agent', and Jentic returns the matching Zenlist Partner Integration operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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 agent, chat, client operations.

### Can I limit what my agent is allowed to do with the Zenlist Partner Integration API?

Yes. Because you run Jentic One yourself, your own rules decide which Zenlist operations and credentials the agent may use, so you can allow read calls like GET /subscriptions and GET /agents while withholding writes such as POST /subscriptions or DELETE `/subscriptions/{subscriptionId}.` Since Zenlist puts the subscription and agent IDs in the URL path, a rule can pin the agent to a single subscription or a single agent record. Deleting a subscription is only possible if you explicitly grant that operation.