canonical: https://jentic.com/apis/zoom.us/contact-center

# Zoom Contact Center

The Contact Center APIs allow developers to interface with [Contact Center](https://developers.zoom.us/docs/contact-center/) features programmatically. The API exposes 225 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically create an address book, list address books. Covers 225 operations with apiKey, oauth2 authentication.

## Scope

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

## Capabilities

- Create an address book
- List address books
- Get an address book unit
- Update an address book unit
- Delete an address book unit

## Use cases

### CRM Operations

Use the Contact Center to perform crm operations programmatically. The API provides 225 endpoints covering core functionality including create an address book, list address books, create an address book unit.

Example prompt: Call POST /contact_center/address_books to create an address book

### Automated Contact_Center Management

Automate contact_center operations by combining multiple Contact Center endpoints. Agents can list address books and then create an address book unit in a single workflow.

Example prompt: Call GET /contact_center/address_books to list address books, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Contact Center 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, oauth2 tokens manually.

Example prompt: Search Jentic for 'create an address book', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /contact_center/address_books | Create an address book |
| GET | /contact_center/address_books | List address books |
| POST | /contact_center/address_books/units | Create an address book unit |
| GET | /contact_center/address_books/units | List address book units |
| GET | /contact_center/address_books/units/{unitId} | Get an address book unit |
| PATCH | /contact_center/address_books/units/{unitId} | Update an address book unit |
| DELETE | /contact_center/address_books/units/{unitId} | Delete an address book unit |
| GET | /contact_center/address_books/{addressBookId} | Get an address book |

## Key resources

- **Contact_Center** — Operations for contact_center

## Why Jentic

- **Setup:** Wiring Zoom Contact Center by hand means running its OAuth 2.0 flow or setting the Authorization header, refreshing tokens, and mapping address book and unit shapes against the api.zoom.us host yourself. Through Jentic you install once, import Zoom Contact Center from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** Zoom Contact Center puts ids like the address book and unit in the URL path (/contact_center/address_books/{addressBookId}, /units/{unitId}), so a rule can pin your agent to one address book: it can read and update that book's units and nothing else. You choose the operations it may call, so destructive ones like unit deletion are not included unless you add them.
- **Credential handling:** Your Zoom OAuth credential 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 an address book' or 'list address book units', and Jentic returns the matching Zoom Contact Center operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Contact Center use?

The Contact Center uses apiKey, oauth2 authentication. 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 create an address book with the Contact Center?

Yes. Use the POST /contact_center/address_books endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Contact Center?

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 create an address book through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an address book'. Jentic returns the matching Contact Center operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Contact Center have?

The Contact Center exposes 225 endpoints covering contact_center operations.

### Can I limit what my agent is allowed to do with the Zoom Contact Center API?

Yes. Because you run Jentic One yourself, your own rules decide which Zoom Contact Center operations and credentials the agent may use. Since ids like the address book and unit sit in the URL path (/contact_center/address_books/{addressBookId}, /units/{unitId}), a rule can pin your agent to a single address book so it only reads and updates that book's units and nothing else. You also choose the operations it may call, so destructive ones such as DELETE /contact_center/address_books/units/{unitId} stay out of reach unless you add them.