For Agents
Programmatically list users, list deleted users. Covers 24 operations with apiKey, bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Voiso Contact Center 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fvoiso.com%2Fvoiso" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fvoiso.com%2Fvoiso" | 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 Voiso Contact Center API.
List users
Initiate outbound call
Stop outbound call
Schedule callback
GET STARTED
Use for: I need to users, I want to deleted users, Search for teams, Find all initiate outbound call
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Voiso API for contact center operations including voice, messaging, campaigns, and monitoring. The API exposes 24 endpoints secured with apiKey, bearer authentication.
Send SMS message
Patterns agents use Voiso Contact Center API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'list users', load the operation schema, and execute with Jentic-managed credentials
24 endpoints — voiso api for contact center operations including voice, messaging, campaigns, and monitoring.
METHOD
PATH
DESCRIPTION
/users
List users
/users/deleted
List deleted users
/teams
List teams
/click2call/start
Initiate outbound call
/click2call/stop
Stop outbound call
/callback/schedule
Schedule callback
/sms/send
Send SMS message
/sms/templates
Retrieve SMS templates
/users
List users
/users/deleted
List deleted users
/teams
List teams
/click2call/start
Initiate outbound call
/click2call/stop
Stop outbound call
/callback/schedule
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Voiso Contact Center API through Jentic.
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.
Schedule callback
/sms/send
Send SMS message
/sms/templates
Retrieve SMS templates