For Agents
Send and receive messages across iMessage, SMS, RCS, WhatsApp, and Apple Messages for Business: manage chats, contacts, groups, polls, reactions, webhooks, and a unified event feed.
Use for: Send a message to a customer over iMessage, Send a WhatsApp message on a specific channel, Find or create a chat with a contact, List the messages in a chat
Not supported: Does not run voice calls, email campaigns, or video conferencing. Use for multi-channel text messaging across iMessage, SMS, RCS, and WhatsApp only.
The Blooio v4 API sends and receives messages across iMessage, SMS, RCS, WhatsApp, and Apple Messages for Business from one interface. An agent finds or creates a chat, sends messages on a chosen channel, and reads message status, reactions, and polls. It manages channels, contacts and their identities, groups, and webhooks, and exposes a unified event feed so a single feed carries activity from every channel.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Blooio v4 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%2Fblooio.com%2Fblooio" | shStep 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%2Fblooio.com%2Fblooio" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Blooio v4 API.
Send messages across iMessage, SMS, RCS, WhatsApp, and Apple Messages for Business channels
Find or create a chat and list its messages
Create contacts and attach identities to them
Send polls and record reactions in a chat
Create groups and manage their members
Register webhooks and replay their deliveries
Look up a phone number's reachability and capabilities
Patterns agents use Blooio v4 API for, with concrete tasks.
★ Agent-run multi-channel messaging
An AI assistant reaches a customer on whatever channel works. Through Jentic the agent finds or creates a chat and sends a message over iMessage, SMS, RCS, or WhatsApp, letting the chat pick the channel or targeting a specific one. It then reads message status and reactions to confirm delivery, all through one interface instead of one SDK per channel.
Find or create a chat with a contact and send a message, then read its status to confirm it was delivered
Unified inbound handling
A support bot works one feed instead of many webhooks. Blooio exposes a unified event feed and webhooks that carry message events, reactions, and deliveries from every channel, so an agent subscribes once and handles inbound messages regardless of where they came from. Webhook deliveries can be replayed if a handler misses one.
Register a webhook for message events, then replay a missed delivery when a handler reports a gap
Contact and number intelligence
An agent checks who it can reach and how. The phone-number lookup reports a number's reachability and capabilities, and contacts carry identities across channels, so before sending the agent knows whether a number supports RCS or iMessage. This avoids a failed send on a channel the recipient cannot receive.
Look up a phone number's capabilities and send over the channel it supports, falling back to SMS when it does not
106 endpoints — the blooio v4 api sends and receives messages across imessage, sms, rcs, whatsapp, and apple messages for business from one interface.
METHOD
PATH
DESCRIPTION
/messages
Send a message
/chats
List chats
/chats
Find or create a chat
/chats/{chatId}/messages
Send a message to a chat
/channels/{channel}/messages
Send a message on a specific channel
/contacts
List contacts
/contacts
Create a contact
/webhooks
Create a webhook
/messages
Send a message
/chats
List chats
/chats
Find or create a chat
/chats/{chatId}/messages
Send a message to a chat
/channels/{channel}/messages
Send a message on a specific channel
/contacts
List contacts
/contacts
Create a contact
/webhooks
Create a webhook
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Blooio v4 API by hand means handling its bearer API key, choosing the right channel for each message across iMessage, SMS, RCS, and WhatsApp, and tracking webhook deliveries and the unified event feed yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Blooio v4 API puts the channel and chat ids in the URL path (/channels/{channel}, /chats/{chatId}), so a rule can pin your agent to one channel or chat: it can send and read messages there without reaching contact deletion or API-key management. You choose the operations it may call, so destructive ones like removing a channel or deprecating an API key are not included unless you add them.
Credential isolation
Your Blooio API key is held once, encrypted, by your own Jentic One instance and injected 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 message' or 'look up a phone number', and Jentic returns the matching Blooio operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Blooio v4 API through Jentic.
What authentication does the Blooio v4 API use?
The Blooio v4 API authenticates with an API key sent as a bearer token in the Authorization header per its OpenAPI spec. Through Jentic the key is injected at call time by your own Jentic One instance, so it never enters the agent's prompt or logs.
Can I send a WhatsApp message with the Blooio v4 API?
Yes. Blooio is multi-channel: the send-message operations deliver over iMessage, SMS, RCS, WhatsApp, and Apple Messages for Business, and you can send on a specific channel or let a chat pick one. Each channel's capabilities endpoint reports what that line supports.
What are the rate limits for the Blooio v4 API?
The OpenAPI spec does not specify rate limits. Check the Blooio documentation at https://blooio.com for current limits and per-channel throughput before sending at volume.
Is there a Blooio MCP server?
You don't need an MCP server to give your agent the Blooio v4 API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls it, so you skip installing and syncing a separate server.
Can I limit what my agent is allowed to do with the Blooio v4 API?
Yes. Write a rule that allows only the send-message and chat-read operations for one channel, so your agent can send and follow conversations there but cannot delete contacts or rotate webhook secrets. Every call it makes is logged.
How do I send a message with the Blooio v4 API through Jentic?
Search Jentic for 'send a message' and it returns the send operation with its input schema; the agent passes the recipient and body and Blooio routes it over the chosen channel. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED