canonical: https://jentic.com/apis/telegram.org/telegram

# Telegram Bot API

Auto-generated OpenAPI schema. The API exposes 74 endpoints.

## For AI agents

Programmatically access Telegram Bot API resources. Covers 74 operations.

## Scope

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

## Capabilities

- Access Telegram Bot API resources via REST API
- Manage developer tools data programmatically
- Integrate Telegram Bot API into automated workflows
- Query and filter Telegram Bot API records by parameters
- Monitor Telegram Bot API operational status and events

## Use cases

### Developer Tools Operations

The API provides 74 endpoints for developer tools operations.

Example prompt: Execute a primary operation against the Telegram Bot API

### Data Retrieval and Monitoring

Query Telegram Bot 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 Telegram Bot API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Telegram Bot 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 'telegram bot API', load the operation schema, and execute with Jentic-managed credentials

## Key resources

- **Addstickertoset** — Operations for addStickerToSet
- **Answercallbackquery** — Operations for answerCallbackQuery
- **Answerinlinequery** — Operations for answerInlineQuery
- **Answerprecheckoutquery** — Operations for answerPreCheckoutQuery
- **Answershippingquery** — Operations for answerShippingQuery

## Why Jentic

- **Setup:** Wiring the Telegram Bot API by hand means embedding your bot token into the base URL path, tracking update offsets, and writing the polling and retry handling across its many methods yourself. Through Jentic you install once, import the Telegram Bot API from the API Directory, store the bot token once, and your agent calls it.
- **Permission scoping:** The Telegram Bot API addresses chats and messages through the request body rather than the URL path, so limit the agent to the operations it needs, such as sending a message or answering a callback query. You choose that allowed set, and operations like kicking a chat member are not included unless you add them.
- **Credential handling:** Your Telegram bot 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.
- **Discovery method:** Agents search Jentic by intent such as 'send a message to a chat' or 'get incoming updates', and Jentic returns the matching Telegram Bot API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Telegram Bot API use?

The Telegram Bot 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.

### What are the rate limits for the Telegram Bot 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 use telegram bot API through Jentic?

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

### How many endpoints does the Telegram Bot API have?

The Telegram Bot API exposes 74 endpoints covering addstickertoset, answercallbackquery, answerinlinequery operations.

### Does the Telegram Bot API support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

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

Yes. Because you run Jentic One yourself, your own rules decide which Telegram Bot API operations and credentials the agent can use, so you can allow only what it needs, such as sending a message or answering a callback query. Since the API addresses chats and messages through the request body rather than the URL path, you scope access by choosing that allowed set of operations. Sensitive actions like kicking a chat member stay out of reach unless you explicitly add them, and your bot token is injected at execution time without entering the agent's context.