canonical: https://jentic.com/apis/threema.ch/threema-ch

# Threema Ch Threema Broadcast API

API for managing Threema Broadcast identities, bots, distribution lists, feeds, groups, and messaging. The API exposes 77 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a bot, list all bots. Covers 77 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for social media only.

## Capabilities

- Create a bot
- List all bots
- Get bot details
- Update a bot
- Delete a bot

## Use cases

### Social Media Operations

Use the Threema Broadcast API to perform social media operations programmatically. The API provides 77 endpoints covering core functionality including create a bot, list all bots, get bot details.

Example prompt: Call POST `/identities/{broadcastUid}/bots` to create a bot

### Automated Bots Management

Automate bots operations by combining multiple Threema Broadcast API endpoints. Agents can list all bots and then get bot details in a single workflow.

Example prompt: Call GET `/identities/{broadcastUid}/bots` to list all bots, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Threema Broadcast 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 'create a bot', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/identities/{broadcastUid}/bots` | Create a bot |
| GET | `/identities/{broadcastUid}/bots` | List all bots |
| GET | `/identities/{broadcastUid}/bots/{botUid}` | Get bot details |
| PUT | `/identities/{broadcastUid}/bots/{botUid}` | Update a bot |
| DELETE | `/identities/{broadcastUid}/bots/{botUid}` | Delete a bot |
| PUT | `/identities/{broadcastUid}/bots/{botUid}/{botState}` | Update bot state |
| POST | `/identities/{broadcastUid}/bots/{botUid}/commands` | Create bot command |
| GET | `/identities/{broadcastUid}/bots/{botUid}/commands` | List bot commands |

## Key resources

- **Bots** — Operations related to Bots
- **Distribution Lists** — Operations related to Distribution Lists
- **Feeds** — Operations related to Feeds
- **Groups** — Operations related to Groups
- **Identities** — Operations related to Identities

## Why Jentic

- **Setup:** Wiring the Threema Broadcast API by hand means setting up its X-API-Key header and managing the bot and command calls under a broadcast identity yourself. Through Jentic you install once, import the Threema Broadcast API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Threema puts the broadcast identity and bot id in the URL path (`/identities/{broadcastUid}/bots/{botUid}`), so a rule can pin your agent to one bot under one broadcast identity: it can read that bot and send its commands and nothing else. You choose the operations it may call, so destructive ones like deleting a bot or changing its state are not included unless you add them.
- **Credential handling:** Your Threema Broadcast 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a broadcast bot' or 'send a bot command', and Jentic returns the matching Threema Broadcast API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Threema Broadcast API use?

The Threema Broadcast 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 create a bot with the Threema Broadcast API?

Yes. Use the POST `/identities/{broadcastUid}/bots` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Threema Broadcast 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 create a bot through Jentic?

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

### How many endpoints does the Threema Broadcast API have?

The Threema Broadcast API exposes 77 endpoints covering bots, distribution lists, feeds operations.

### Can I limit what my agent is allowed to do with the Threema Broadcast API?

Yes. Because you run Jentic One yourself and it is self-hosted, your own rules decide which Threema Broadcast API operations and credentials the agent may use. Since Threema puts the broadcast identity and bot ID in the URL path, such as `/identities/{broadcastUid}/bots/{botUid}`, you can pin the agent to a single bot under one broadcast identity so it only reads that bot and sends its commands. You choose the operations it may call, so destructive ones like deleting a bot or updating its state stay off limits unless you grant them.