canonical: https://jentic.com/apis/swaggerhub.feedyou/feedyou-bot-messaging-api

# Feedyou Bot Messaging API

This API allows to use Feedyou bot with omnichannel solution which allows sending and receiving text messages to the user using various channeks. - When user starts conversation and routing rule tells that bot should handle this conversation, `beginIntroDialog` event is sent to the bot - Bot loads set of intro messages and sends them one by one to the endpoind specified by `serviceUrl` in incoming. The API exposes 2 endpoints.

## For AI agents

Programmatically send message from user to the bot's custom channel, send message or event from the bot to user. Covers 2 operations.

## Scope

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

## Capabilities

- Send message from user to the bot's custom channel
- Manage communications data programmatically
- Integrate Feedyou Bot Messaging API into automated workflows
- Query and filter Feedyou Bot Messaging API records by parameters
- Monitor Feedyou Bot Messaging API operational status and events

## Use cases

### Communications Operations

Use the Feedyou Bot Messaging API to perform communications operations programmatically. The API provides 2 endpoints covering core functionality including send message from user to the bot's custom channel, send message or event from the bot to user.

Example prompt: Call POST /custom to send message from user to the bot's custom channel

### Data Retrieval and Monitoring

Query Feedyou Bot Messaging API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Feedyou Bot Messaging API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Feedyou Bot Messaging 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.

Example prompt: Search Jentic for 'send message from user to the bot's custom channel', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/custom` | Send message from user to the bot's custom channel |
| POST | `/` | Send message or event from the bot to user |

## Key resources

- **Custom** — Operations for custom

## Why Jentic

- **Setup:** Wiring the Feedyou Bot Messaging API by hand means resolving your per-bot Azure host, formatting the message payload, and posting to the default and custom channels yourself. Through Jentic you install once, import Feedyou Bot Messaging API from the API Directory, store the connection once, and your agent calls it.
- **Permission scoping:** This API sends the channel and message in the request body, so scope the agent to the operations it needs, such as posting a message to the bot. You choose the operations it may call, so the custom channel post is not included unless you add it.
- **Credential handling:** This API declares no authentication, so there is no secret to hand around; any connection settings are held once by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a message to the bot' or 'post to the custom channel', and Jentic returns the matching Feedyou Bot Messaging API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Feedyou Bot Messaging API use?

The Feedyou Bot Messaging API uses no 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 send message from user to the bot's custom channel with the Feedyou Bot Messaging API?

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

### What are the rate limits for the Feedyou Bot Messaging 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 send message from user to the bot's custom channel through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send message from user to the bot's custom channel'. Jentic returns the matching Feedyou Bot Messaging API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Feedyou Bot Messaging API have?

The Feedyou Bot Messaging API exposes 2 endpoints covering custom operations.

### Can I limit what my agent is allowed to do with the Feedyou Bot Messaging API?

Yes. Because Jentic One is self-hosted, your own rules decide which of the two operations your agent may call and which connection settings it may use. This API passes the channel and message in the request body, so you can allow the bot-to-user message post (POST /) while withholding the custom channel post (POST /custom), which is never included unless you add it. The agent can only run the operations you grant, so it cannot reach a channel you have not authorized.