Send and read messages in BloomText conversations from your EMR integration. Every request is authenticated with an organization-scoped API key.
Get started for freeSchedule a demo →Yes. Any EMR with an API can connect to BloomText: your app reads schedules or patients from the EMR and sends messages with the BloomText API. BloomText handles the messaging, and your EMR stays the system of record.
Your app reads patients and appointments through your EMR’s API.
It looks up each patient’s BloomText conversation in a simple mapping your app keeps.
It sends reminders and replies with the BloomText API, and hears back through webhooks.
Your EMR stays your system of record. BloomText handles the conversations, and nothing syncs until your app connects the two.
Start from the vendor’s own documentation or partner terms. On the BloomText side, read the API reference for resources, conversation membership, pagination, and signed webhooks. Then map vendor records to BloomText conversations in your app.
GET https://api.bloomtext.com/v1/conversations/{conversationId}/messages?page[limit]=50Authorization: Bearer bt_live_…POST https://api.bloomtext.com/v1/conversations/{conversationId}/messagesAuthorization: Bearer bt_live_…Idempotency-Key: <unique-request-key>Content-Type: application/json{"body":"Your appointment is confirmed for Tuesday at 10:00 AM."}Send your API key in the Authorization header on every request. POST requests also need Idempotency-Key and Content-Type headers.
Most EMR integrations follow the same shape: read a schedule or patient record from the EMR, find the matching BloomText conversation your app has stored, and post a message or react to one.
A nightly job reads tomorrow’s appointments from your EMR and posts a reminder into each patient’s BloomText conversation. Replies land in the same thread your front desk already works from.
Uses your EMR’s appointment and patient data
When a new patient is booked but their intake packet is still open in the EMR, send a short nudge with the link your practice already uses. Stop nudging once the EMR marks the forms complete.
Uses your EMR’s appointment status and forms status
Post into an internal BloomText group when something in the EMR needs a person: a same-day cancellation, a new referral, or an unsigned note. Staff discuss it where they already talk.
Uses your EMR’s schedule changes and task lists
Subscribe to the conversation.message.created webhook and route patient replies. A “C” reply to a reminder can confirm the appointment in the EMR, while anything else goes to a staff queue.
Uses your EMR’s appointment confirmation field
Export a conversation’s history on a schedule and attach the file to the patient’s chart, so the EMR holds a copy of what was said by text.
Uses your EMR’s document upload endpoint
A scheduled script that reminds every patient booked for tomorrow.
POST https://api.bloomtext.com/v1/conversations/{conversationId}/messagesAuthorization: Bearer bt_live_…Idempotency-Key: <unique-request-key>Content-Type: application/json{"body":"Reminder: you have an appointment tomorrow at 9:30 AM. Reply C to confirm."}A small HTTPS endpoint that turns patient replies into confirmations.
conversation.message.created and verify each signature.GET https://api.bloomtext.com/v1/conversations/{conversationId}/messages?page[limit]=5Authorization: Bearer bt_live_…POST https://api.bloomtext.com/v1/messages/{messageId}/reactionsAuthorization: Bearer bt_live_…Idempotency-Key: <unique-request-key>Content-Type: application/json{"emoji":"👍"}An AI agent with access to both systems can handle the routine back-and-forth for a front desk: answering scheduling questions, sending reminders, and handing anything clinical to a person.
Any MCP client, such as Claude, Cursor, or your own agent, can read and send BloomText messages with your API key.
{ "mcpServers": { "bloomtext": { "type": "http", "url": "https://mcp.bloomtext.com/mcp", "headers": { "Authorization": "Bearer bt_live_…" } } }}Give the agent a small tool that calls your EMR’s API with your approved credentials, such as “look up tomorrow’s appointments” or “mark appointment confirmed.” Keep those tools narrow and read-only where you can. The BloomText MCP server covers the messaging side.
conversation.message.created webhook.When a patient asks about their next appointment, look it up in the EMR and reply in their BloomText conversation with the date and time. If they ask anything clinical, don’t answer. Post “Needs staff reply” in the Front Desk group with a link to the conversation.Messages the agent sends appear under its app user’s name, and an organization admin can revoke its key at any time. Read the MCP docs.
Yes. You write a small integration that reads from your EMR’s API and calls the BloomText API. BloomText handles the messaging side: conversations, messages, reactions, participants, and webhooks. Your app stores which EMR patient maps to which BloomText conversation.
Many EMRs gate API access behind a partner program, an admin request, or a paid add-on. Ask your EMR vendor for its approved access process. You can still build the BloomText side first and plug in the EMR data once access is approved.
The API posts messages into existing BloomText conversations, which reach patients however they’re connected, including SMS. It doesn’t send one-off texts to arbitrary numbers, so every message lands in a thread your staff can see.
Yes. Add the BloomText MCP server to any MCP-compatible client and give the agent a tool that calls your EMR’s API. The agent sends messages as a named app user, so staff always know what came from it.
BloomText API keys are only issued to organizations with a signed BAA, and every message stays inside a BloomText conversation your staff can audit. Keep message content to what the patient needs, such as appointment times, and follow your own EMR vendor’s terms for the data you read.
Every EMR vendor controls its own API access. Some offer free certified APIs, and others require a partnership, a paid add-on, or an admin request.
API keys are issued to organizations with a signed BAA. Book a short call, tell us what you’re building, and we’ll set up your key. Don’t include PHI when you book.
Links last checked September 21, 2026.
