canonical: https://jentic.com/apis/voiso.com/voiso

# Voiso Contact Center API

Voiso API for contact center operations including voice, messaging, campaigns, and monitoring. The API exposes 24 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically list users, list deleted users. Covers 24 operations with apiKey, bearer authentication.

## Scope

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

## Capabilities

- List users
- Initiate outbound call
- Stop outbound call
- Schedule callback
- Send SMS message

## Use cases

### CRM Operations

Use the Voiso Contact Center API to perform crm operations programmatically. The API provides 24 endpoints covering core functionality including list users, list deleted users, list teams.

Example prompt: Call GET /users to list users

### Automated Campaigns Management

Automate campaigns operations by combining multiple Voiso Contact Center API endpoints. Agents can list deleted users and then list teams in a single workflow.

Example prompt: Call GET `/users/deleted` to list deleted users, then verify the result

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'list users', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/users` | List users |
| GET | `/users/deleted` | List deleted users |
| GET | `/teams` | List teams |
| POST | `/click2call/start` | Initiate outbound call |
| POST | `/click2call/stop` | Stop outbound call |
| POST | `/callback/schedule` | Schedule callback |
| POST | `/sms/send` | Send SMS message |
| GET | `/sms/templates` | Retrieve SMS templates |

## Key resources

- **Campaigns** — Operations related to Campaigns
- **Contact Center Operations** — Operations related to Contact Center Operations
- **Messaging** — Operations related to Messaging
- **Monitoring** — Operations related to Monitoring
- **User Management** — Operations related to User Management

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 80 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 65 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/voiso.com/voiso/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Voiso by hand means choosing the right per-cluster host ({cluster_id}.voiso.com), setting its X-API-Key or JWT bearer token, and managing the calls yourself. Through Jentic you install once, import Voiso Contact Center from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Voiso carries its targets in request parameters and bodies rather than the URL path, so limit the agent to the operations it needs, such as listing users or sending an SMS. You choose the allowed set, so operations like stopping a click-to-call are not included unless you add them.
- **Credential handling:** Your Voiso API key or bearer token 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 'list users' or 'send an SMS', and Jentic returns the matching Voiso 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 Voiso Contact Center API use?

The Voiso Contact Center API uses apiKey, bearer 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 list users with the Voiso Contact Center API?

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

### What are the rate limits for the Voiso Contact Center 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 list users through Jentic?

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

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

The Voiso Contact Center API exposes 24 endpoints covering campaigns, contact center operations, messaging operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Voiso operations and credentials the agent may use. Because Voiso carries its targets in request parameters and bodies rather than the URL path, you scope the agent to just the operations it needs, such as listing users or sending an SMS. Operations like initiating or stopping a click-to-call outbound call are not available to the agent unless you add them to the allowed set.