TCDial API

Name: TCDial API
Brand: TCDial API
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail DeliveryapiKey21 EndpointsREST

For Agents

Programmatically initiate call, list calls. Covers 21 operations with apiKey authentication.

Use for: I need to initiate call, I want to calls, Search for call details, Find all end active call

Install Jentic One Beta

Connect the TCDial API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TCDial 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%2Ftcdial.com%2Ftcdial" | sh

Step 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%2Ftcdial.com%2Ftcdial" | 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 TCDial API.

Initiate call

List calls

Get call details

End active call

GET STARTED

Start building with TCDial API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use TCDial API for, with concrete tasks.

★ Communications Operations

Use the TCDial API to perform communications operations programmatically. The API provides 21 endpoints covering core functionality including initiate call, list calls, get call details.

Call POST /calls to initiate call

Automated calls Management

Automate calls operations by combining multiple TCDial API endpoints. Agents can list calls and then get call details in a single workflow.

Call GET /calls to list calls, then verify the result

AI Agent Integration via Jentic

AI agents discover and call TCDial 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 'initiate call', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

21 endpoints — cloud telephony and call center api.

METHOD

PATH

DESCRIPTION

POST

/calls

Initiate call

GET

/calls

List calls

GET

/calls/{id}

Get call details

POST

/calls/{id}/end

End active call

POST

/contacts

Create contact

GET

/contacts

List contacts

GET

/contacts/{id}

Get contact by ID

PUT

/contacts/{id}

Update contact

POST

/calls

Initiate call

GET

/calls

List calls

GET

/calls/{id}

Get call details

POST

/calls/{id}/end

End active call

POST

/contacts

Create contact

GET

/contacts

List contacts

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the TCDial API by hand means sending its X-API-Key header on every request, targeting the api.tcdial.com/v1 host, and building your own retry handling across call and contact endpoints. Through Jentic you install once, import the TCDial API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The TCDial API puts the call and contact ids in the URL path (/calls/{id}, /contacts/{id}), so a rule can pin your agent to one call or contact: it can read and update those records. You choose the operations it may call, so actions like ending a call are not included unless you add them.

Credential isolation

Your TCDial API key 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 'initiate a call' or 'update a contact', and Jentic returns the matching TCDial API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using TCDial API through Jentic.

What authentication does the TCDial API use?

The TCDial API uses an API key passed in the `X-API-Key` header. 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 initiate call with the TCDial API?

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

What are the rate limits for the TCDial 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 initiate call through Jentic?

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

How many endpoints does the TCDial API have?

The TCDial API exposes 21 endpoints covering calls, contacts, campaigns operations.

TCDial API

Connect the TCDial API to your agent

Capabilities

Start building with TCDial API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs