Contact Center AI Platform API

✓ Official Vendor SpecCommunicationsVoice Telephonyoauth29 EndpointsREST

For Agents

Create, list, and tear down Google Contact Center AI Platform tenants so an agent can stand up a fully managed cloud contact centre and confirm its provisioning state.

Quickstart

Get started with Contact Center AI Platform API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"provision a google contact center ai platform tenant"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Contact Center AI Platform API API.

Provision a new CCAI Platform tenant under a project and location

List active contactCenter instances and their lifecycle state

Retrieve the configuration and admin URL of a specific contactCenter

Track long-running provisioning operations and cancel ones that have stalled

GET STARTED

Start building with Contact Center AI Platform API API

Explore with Jentic

View OpenAPI Document

Use for: I need to provision a new CCAI Platform tenant for a customer, List all contact centers in our europe-west1 location, Retrieve the admin URL of a provisioned contactCenter, Check whether a contactCenter creation operation finished successfully

Not supported: Does not configure IVR flows, route calls, or analyse conversations — use only to create and manage CCAI Platform tenant resources.

Google Contact Center AI Platform (CCAI Platform) API lets administrators provision and manage tenant-level contact centre instances on Google Cloud. It exposes a small surface for creating contactCenter resources, listing them per project and location, querying validation state, and tracking long-running provisioning operations. CCAI Platform itself bundles cloud telephony, agent desktop, IVR, routing, and reporting; this API handles the platform-level lifecycle. It is currently published as v1alpha1.

Use Cases

Patterns agents use Contact Center AI Platform API API for, with concrete tasks.

★ Multi-Tenant Contact Center Provisioning

A BPO or SaaS reseller stands up an isolated CCAI Platform tenant per end customer. The Contact Center AI Platform API creates the contactCenter resource, returns the long-running operation, and surfaces the admin URL once provisioning completes. Each tenant gets its own telephony numbers, agent desktop, and reporting separate from siblings.

Create a contactCenter named 'acme-support' in europe-west1, poll the returned operation until done, and return the admin console URL.

Contact Center Decommissioning

When a customer churns, automation deletes the CCAI Platform tenant and confirms that telephony and storage have been released. The API exposes contactCenter delete plus operation polling so a script can guarantee clean teardown before billing stops. This avoids manual console work that often misses orphaned resources.

Delete the contactCenter 'former-customer-x' and confirm the long-running delete operation reaches a done state.

Provisioning Health Monitoring

An ops dashboard polls the CCAI Platform API to display the provisioning state of every tenant, surface failed operations, and alert when a contactCenter has been stuck creating for more than 30 minutes. The contactCenters list and operations endpoints provide everything needed without scraping the Cloud Console.

List all contactCenters in project 'support-cluster', then for each fetch its latest operation and flag any whose state is not DONE after 30 minutes.

Agent-Driven Tenant Onboarding

An onboarding agent receives a new customer signup, asks Jentic for the create-contactcenter operation, supplies the customer's preferred region and admin email, and waits on the operation. The agent then hands the admin URL back to the human onboarder. Jentic isolates the Google service-account credentials so the agent never sees them.

Provision a contactCenter for tenant 'newco-2026' in us-east4, attach the admin user newco-admin@example.com, and return the admin URL once the operation completes.

Key Endpoints

9 endpoints — google contact center ai platform (ccai platform) api lets administrators provision and manage tenant-level contact centre instances on google cloud.

METHOD

PATH

DESCRIPTION

POST

/v1alpha1/{+parent}/contactCenters

Create a new contactCenter tenant

GET

/v1alpha1/{+parent}/contactCenters

List contactCenters in a project and location

GET

/v1alpha1/{+name}

Get a specific contactCenter or location resource

GET

/v1alpha1/{+name}/operations

List long-running operations

POST

/v1alpha1/{+name}:cancel

Cancel a long-running operation

POST

/v1alpha1/{+parent}/contactCenters

Create a new contactCenter tenant

GET

/v1alpha1/{+parent}/contactCenters

List contactCenters in a project and location

GET

/v1alpha1/{+name}

Get a specific contactCenter or location resource

GET

/v1alpha1/{+name}/operations

List long-running operations

POST

/v1alpha1/{+name}:cancel

Cancel a long-running operation

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google service account JSON keys are stored encrypted in the Jentic vault. Agents call contactcenteraiplatform.googleapis.com with scoped, short-lived access tokens minted per request.

Intent-based discovery

Agents search Jentic for 'create google contact center' and Jentic returns the contactCenters.create operation with its parent, displayName, and admin user input schema.

Time to first call

Direct integration: 1-2 days to handle OAuth, region discovery, and long-running operation polling. Through Jentic: under 30 minutes by composing search, load, and execute on the contactCenters collection.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Contact Center AI Insights API

Analyse the calls a CCAI Platform tenant produces for sentiment and topics

Use Insights once a contactCenter is producing transcripts; use Platform API only for tenant lifecycle

Complementary

Dialogflow API

Power the IVR and virtual agent inside a CCAI Platform tenant

Choose Dialogflow when designing the conversational flows; the Platform API only provisions the container that runs them

Alternative

Amazon Connect API

Managed cloud contact centre on AWS as an alternative to CCAI Platform

Choose Amazon Connect when the rest of the stack is on AWS; choose CCAI Platform when Google AI features and Workspace integration are needed

FAQs

Specific to using Contact Center AI Platform API API through Jentic.

What authentication does the Contact Center AI Platform API use?

The CCAI Platform API uses Google OAuth 2.0 with the cloud-platform scope. Through Jentic the service account credentials are kept in the Jentic vault and the agent receives scoped access tokens per call rather than the raw key.

Can I create a contactCenter tenant in any region with the CCAI Platform API?

No. The contactCenters create endpoint accepts only the regions where CCAI Platform is generally available; call the locations list under the parent project first to see which regions are valid before attempting creation.

What are the rate limits for the CCAI Platform API?

The CCAI Platform API inherits standard Google Cloud per-project request quotas, with stricter limits on contactCenter create and delete because each triggers a long-running provisioning workflow. Check the Cloud Console Quotas page for your project's specific limits.

How do I provision a new contactCenter through Jentic?

Run pip install jentic, search Jentic for 'create ccai platform contact center', load the schema for the contactCenters.create operation on contactcenteraiplatform.googleapis.com, and execute it with the parent location and admin user payload.

Does the CCAI Platform API let me edit IVR flows or agent skills?

No. This API only handles tenant lifecycle. IVR flow design, agent skill assignment, and call routing are configured inside the CCAI Platform admin console at the URL returned after provisioning.