Broadcast Threema Ch Threema Broadcast API

Name: Threema Broadcast API
Brand: Threema Broadcast API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat MessagingapiKey25 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Threema Broadcast API to your agent

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

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbroadcast.threema.ch%2Fthreema-broadcast" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbroadcast.threema.ch%2Fthreema-broadcast" | 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 Threema Broadcast API.

Create and configure chatbots under a broadcast identity, including their command catalogue

Manage distribution lists and add or remove recipients by Threema ID

Send chat messages to a distribution list and retrieve delivery status per recipient

GET STARTED

Start building with Threema Broadcast API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Threema Broadcast API, keeping it validated and agent-ready. Threema Broadcast is the business messaging service from Threema, the Swiss end-to-end encrypted messenger. The API lets organisations programmatically manage broadcast identities, distribution lists, recipients, feeds, and chatbots so they can send secure, automated alerts and notifications to staff or members. It is built around a model where each customer has a broadcast identity that owns multiple channels including bots, distribution lists, and feeds, with chat and delivery-status endpoints for each.

Use Cases

Patterns agents use Threema Broadcast API for, with concrete tasks.

★ Encrypted Emergency Alerts

Hospitals, police forces, and critical-infrastructure operators use Threema Broadcast to send end-to-end encrypted alerts to on-call staff. The agent maintains a distribution list of Threema IDs per shift and posts a chat message to the list when an incident triggers; delivery status per recipient is then read back via the chat delivery endpoint. Because messages are end-to-end encrypted under Swiss data protection law, this satisfies sectoral privacy requirements that public SMS gateways cannot meet.

POST /identities/{broadcastUid}/distribution_lists/{distributionListUid}/chat with body 'Code Blue ICU bed 4' and then GET the delivery status to confirm all on-call staff received it

Member Communications via Feed Channels

Associations, NGOs, and member-based organisations run a feed channel that members subscribe to in the Threema app to receive curated updates. The API lets staff post messages and files to the feed, manage which recipients can post, and retrieve the chat history. This replaces public social channels with a private, end-to-end encrypted alternative aligned with the organisation's privacy posture.

POST /identities/{broadcastUid}/feeds/{feedUid}/chat with the latest member newsletter text and attach the PDF file

Automated Chatbot for Internal Help Desk

IT teams configure a Threema chatbot under their broadcast identity to handle FAQ-style questions from staff. The API exposes endpoints to register bot commands and toggle the bot state, so the bot can be deployed, paused for maintenance, and updated without losing the underlying identity. This gives the help desk a chat-native first line of triage that runs over an end-to-end encrypted transport.

POST /identities/{broadcastUid}/bots/{botUid}/commands with command name 'reset-password' and a description, then PUT the bot state to active

AI Agent Secure Notification Workflow Through Jentic

An AI operations agent uses Jentic to dispatch encrypted notifications via Threema Broadcast without holding the raw API key. The agent searches for 'send a secure broadcast message', loads the chat-message schema, and executes the call against the right distribution list. This pattern is well suited to incident-response agents that need to escalate to humans while preserving end-to-end encryption.

Use Jentic to search 'send a Threema broadcast message', load the broadcast.threema.ch operation, and execute it against the on-call distribution list with an incident summary

Key Endpoints

25 endpoints — jentic publishes the only available openapi specification for threema broadcast api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/identities/{broadcastUid}/distribution_lists/{distributionListUid}/chat

Send a message to a distribution list

GET

/identities/{broadcastUid}/distribution_lists/{distributionListUid}/chat/{messageUid}/delivery

Retrieve per-recipient delivery status for a message

POST

/identities/{broadcastUid}/distribution_lists

Create a new distribution list

POST

/identities/{broadcastUid}/distribution_lists/{distributionListUid}/recipients

Add recipients to a distribution list

POST

/identities/{broadcastUid}/bots

Create a chatbot under a broadcast identity

POST

/identities/{broadcastUid}/bots/{botUid}/commands

PUT

/identities/{broadcastUid}/bots/{botUid}/{botState}

Toggle the bot's state (active or inactive)

POST

/identities/{broadcastUid}/distribution_lists/{distributionListUid}/chat

Send a message to a distribution list

GET

/identities/{broadcastUid}/distribution_lists/{distributionListUid}/chat/{messageUid}/delivery

Retrieve per-recipient delivery status for a message

POST

/identities/{broadcastUid}/distribution_lists

Create a new distribution list

POST

/identities/{broadcastUid}/distribution_lists/{distributionListUid}/recipients

Add recipients to a distribution list

POST

/identities/{broadcastUid}/bots

Create a chatbot under a broadcast identity

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Threema Broadcast API by hand means setting the X-API-Key header on every request and threading broadcast identities, distribution lists, and bot ids through nested paths yourself. Through Jentic you install once, import the Threema Broadcast API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Threema Broadcast puts the broadcast identity and distribution list ids in the URL path (/identities/{broadcastUid}/distribution_lists/{distributionListUid}/...), so a rule can pin your agent to one distribution list: it can send chat messages and check delivery for that list and nothing else. You choose the operations it may call, so creating bots or changing bot state is not included unless you add it.

Credential isolation

Your Threema Broadcast API key is stored once, encrypted, by your own Jentic One instance and injected as the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a broadcast message to a distribution list', and Jentic returns the matching Threema operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Threema Broadcast API through Jentic.

Why is there no official OpenAPI spec for Threema Broadcast API?

Threema does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Threema Broadcast API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Threema Broadcast API use?

Authentication is via an API key tied to your broadcast identity (the `apiKeyAuth` security scheme in the spec). Through Jentic, the key is stored encrypted in your Jentic One instance and the agent receives a scoped execution token instead of the raw value.

Can I send files through Threema Broadcast?

Yes. Each message in a distribution-list or feed chat can carry a file attachment, and the GET /identities/{broadcastUid}/distribution_lists/{distributionListUid}/chat/{messageUid}/file endpoint lets you retrieve the file back. Files inherit the same end-to-end encryption as text messages.

How do I check whether a broadcast was delivered through Jentic?

Search Jentic for 'check Threema broadcast delivery status', load the broadcast.threema.ch schema, and call GET /identities/{broadcastUid}/distribution_lists/{distributionListUid}/chat/{messageUid}/delivery. The response lists each recipient and their delivery state.

What are the rate limits for the Threema Broadcast API?

The OpenAPI spec does not declare explicit rate limits. Threema applies fair-use throttling per broadcast identity; if you plan to fan out to thousands of recipients, contact Threema support to confirm the appropriate plan tier.

Is Threema Broadcast suitable for emergency alerts?

Yes. Threema Broadcast is widely used in Swiss healthcare, public safety, and critical-infrastructure settings where end-to-end encryption and Swiss data residency are mandatory. Pair the chat endpoint with the delivery-status endpoint to confirm every recipient received the alert.

Broadcast Threema Ch Threema Broadcast API

Connect the Threema Broadcast API to your agent

Capabilities

Start building with Threema Broadcast API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs