Toky API

Name: Toky API API
Brand: Toky API
Availability: InStock

✓ Official Vendor SpecCommunicationsVoice TelephonyapiKey36 EndpointsREST

For Agents

Programmatically list agents, add extra data to agents. Covers 36 operations with apiKey authentication.

Use for: I need to agents, I want to add extra data to agents, Search for new agent, Find all agent groups

Connect the Toky API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Toky 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Toky API API.

List agents

Add extra data to agents

Create new agent

Update agent group

Delete agent group

GET STARTED

Start building with Toky API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Toky API API for, with concrete tasks.

★ Communications Operations

Use the Toky API to perform communications operations programmatically. The API provides 36 endpoints covering core functionality including list agents, add extra data to agents, create new agent.

Call GET /agents to list agents

Automated Agent Management

Automate agent operations by combining multiple Toky API endpoints. Agents can add extra data to agents and then create new agent in a single workflow.

Call POST /agents/extra_data to add extra data to agents, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Toky 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.

Search Jentic for 'list agents', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

36 endpoints — cloud phone system api for managing agents, contacts, calls, sms, voicemail, webhooks, ivr and phone numbers.

METHOD

PATH

DESCRIPTION

GET

/agents

List agents

POST

/agents/extra_data

Add extra data to agents

POST

/agent/create

Create new agent

GET

/agents_groups

List agent groups

POST

/agents/groups

Create agent group

PUT

/agents/groups/{id}

Update agent group

DELETE

/agents/groups/{id}

Delete agent group

GET

/cdrs

List call data records

GET

/agents

List agents

POST

/agents/extra_data

Add extra data to agents

POST

/agent/create

Create new agent

GET

/agents_groups

List agent groups

POST

/agents/groups

Create agent group

PUT

/agents/groups/{id}

Why though Jentic?

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

Credential isolation

Toky API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'list agents') and Jentic returns the matching Toky API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Toky API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio

Alternative communications API

Choose Twilio when you need a different approach to communications operations

Alternative

Sendgrid

Alternative communications API

Choose Sendgrid when you need a different approach to communications operations

Complementary

Pusher

Complementary communications API

Choose Pusher when you need a complementary approach to communications operations

FAQs

Specific to using Toky API API through Jentic.

What authentication does the Toky API use?

The Toky API uses an API key passed in the `X-Toky-Key` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I list agents with the Toky API?

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

What are the rate limits for the Toky 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 agents through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list agents'. Jentic returns the matching Toky API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Toky API have?

The Toky API exposes 36 endpoints covering agent, agents, agents_groups operations.