canonical: https://jentic.com/apis/tamtam.chat/tamtam-chat

# Tamtam Chat TamTam Bot API

Bot API to interact with TamTam messenger. Send and receive messages, manage chats, handle subscriptions and webhooks. The API exposes 16 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get bot info, edit bot info. Covers 16 operations with apiKey authentication.

## Scope

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

## Capabilities

- Get bot info
- Edit bot info
- Send message
- Query and filter TamTam Bot API records by parameters
- Monitor TamTam Bot API operational status and events

## Use cases

### Communications Operations

Use the TamTam Bot API to perform communications operations programmatically. The API provides 16 endpoints covering core functionality including get bot info, edit bot info, get all chats.

Example prompt: Call GET /me to get bot info

### Automated Bots Management

Automate bots operations by combining multiple TamTam Bot API endpoints. Agents can edit bot info and then get all chats in a single workflow.

Example prompt: Call PATCH /me to edit bot info, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TamTam 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 apiKey tokens manually.

Example prompt: Search Jentic for 'get bot info', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/me` | Get bot info |
| PATCH | `/me` | Edit bot info |
| GET | `/chats` | Get all chats |
| GET | `/chats/{chatId}` | Get chat |
| PATCH | `/chats/{chatId}` | Edit chat |
| GET | `/chats/{chatId}/members` | Get chat members |
| POST | `/messages` | Send message |
| GET | `/messages` | Get messages |

## Key resources

- **Bots** — Bot info management
- **Chats** — Chat management
- **Messages** — Message operations
- **Subscriptions** — Webhook subscriptions and updates
- **Uploads** — File uploads

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 45 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 64 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 42 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/tamtam.chat/tamtam-chat/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the TamTam Bot API by hand means passing its access_token as a query parameter on every call, tracking the botapi.tamtam.chat host, and building your own retry handling. Through Jentic you install once, import the TamTam Bot API from the API Directory, store the bot access token once, and your agent calls it.
- **Permission scoping:** The TamTam Bot API puts the chat id in the URL path (`/chats/{chatId}/...`), so a rule can pin your agent to one chat: it can read that chat and its members and nothing else. You choose the operations it may call, so an edit like patching chat settings is not included unless you add it.
- **Credential handling:** Your TamTam bot access 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 'get bot info' or 'send a message to a chat', and Jentic returns the matching TamTam Bot 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 TamTam Bot API use?

The TamTam Bot API uses an API key passed in the `access_token` query. 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 get bot info with the TamTam Bot API?

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

### What are the rate limits for the TamTam 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 get bot info through Jentic?

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

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

The TamTam Bot API exposes 16 endpoints covering bots, chats, messages operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which TamTam Bot API operations and credentials the agent may use. Because the chat id sits in the URL path, such as `/chats/{chatId}` and `/chats/{chatId}/members`, you can pin the agent to a single chat and let it read only that chat and its members. You choose the operations it may call, so a write like PATCH `/chats/{chatId}` or POST /messages stays out of reach unless you add it.