Feedyou Bot Telephony API

Name: Feedyou Bot Telephony API API
Brand: Feedyou Bot Telephony API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail Deliverynone8 EndpointsREST

For Agents

Programmatically notify bot about new incoming call, pass text recognized by stt to the bot. Covers 8 operations.

Connect the Feedyou Bot Telephony API to your agent

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

Notify bot about new incoming call

Pass text recognized by STT to the bot

Listen timeout has been reached

Play message using TTS engine to pending call, optionally switching call to requ

GET STARTED

Start building with Feedyou Bot Telephony API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Feedyou Bot Telephony API, keeping it validated and agent-ready.

This API allows to use Feedyou bot with telephony PBX which implements TTS/STT voice processing on its own. - When user calls PBX, `call_start` event is sent to the bot - Bot loads set of intro messages and sends them one by one using `queue_tts` to the PBX (endpoint where PBX is listening for events from bot should be defined in `callback_endpoint` property) - PBX should transform them to the voi. The API exposes 8 endpoints.

Use Cases

Patterns agents use Feedyou Bot Telephony API API for, with concrete tasks.

★ Communications Operations

Use the Feedyou Bot Telephony API to perform communications operations programmatically. The API provides 8 endpoints covering core functionality including notify bot about new incoming call, pass text recognized by stt to the bot, listen timeout has been reached.

Call POST /call_start to notify bot about new incoming call

Automated Call_End Management

Automate call_end operations by combining multiple Feedyou Bot Telephony API endpoints. Agents can pass text recognized by stt to the bot and then listen timeout has been reached in a single workflow.

Call POST /recognized_text to pass text recognized by stt to the bot, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Feedyou Bot Telephony 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 none tokens manually.

Search Jentic for 'notify bot about new incoming call', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — this api allows to use feedyou bot with telephony pbx which implements tts/stt voice processing on its own.

METHOD

PATH

DESCRIPTION

POST

/call_start

Notify bot about new incoming call

POST

/recognized_text

Pass text recognized by STT to the bot

POST

/listen_timeout_reached

Listen timeout has been reached

POST

/queue_tts

Play message using TTS engine to pending call, optionally switching call to requ

POST

/call_end

Notify bot about finished call

GET

/get_calls_overview

Get list of calls for specified period of time

GET

/get_rec_file

Download recording file

POST

/get_call_debug

Get call debug log

POST

/call_start

Notify bot about new incoming call

POST

/recognized_text

Pass text recognized by STT to the bot

POST

/listen_timeout_reached

Listen timeout has been reached

POST

/queue_tts

Play message using TTS engine to pending call, optionally switching call to requ

POST

/call_end

Notify bot about finished call

Why though Jentic?

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

Credential isolation

Feedyou Bot Telephony API none 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., 'notify bot about new incoming call') and Jentic returns the matching Feedyou Bot Telephony API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Feedyou Bot Telephony 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 Feedyou Bot Telephony API API through Jentic.

What authentication does the Feedyou Bot Telephony API use?

The Feedyou Bot Telephony API uses no authentication. 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 notify bot about new incoming call with the Feedyou Bot Telephony API?

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

What are the rate limits for the Feedyou Bot Telephony 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 notify bot about new incoming call through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'notify bot about new incoming call'. Jentic returns the matching Feedyou Bot Telephony API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Feedyou Bot Telephony API have?

The Feedyou Bot Telephony API exposes 8 endpoints covering call_end, call_start, get_call_debug operations.