Threema Broadcast API

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

✓ Official Vendor SpecSocial MediaSocial PublishingapiKey77 EndpointsREST

For Agents

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

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 API.

Create a bot

List all bots

Get bot details

Update a bot

Delete a bot

GET STARTED

Start building with Threema Broadcast API API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ 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.

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.

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.

Search Jentic for 'create a bot', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

77 endpoints — api for managing threema broadcast identities, bots, distribution lists, feeds, groups, and messaging.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Threema Broadcast API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a bot') and Jentic returns the matching Threema Broadcast API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Threema Broadcast API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Facebook

Alternative social media API

Choose Facebook when you need a different approach to social media operations

Alternative

Twitter

Alternative social media API

Choose Twitter when you need a different approach to social media operations

Complementary

Complementary social media API

Choose Linkedin when you need a complementary approach to social media operations

FAQs

Specific to using Threema Broadcast API API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.