Read patients from athenahealth and message them in BloomText conversations from your own software.
Get started for freeSchedule a demo →Yes. Your app reads patients and appointments from athenahealth's API and sends messages with the BloomText API. There's nothing to install: a small app of yours joins the two, and athenahealth reviews each app before it goes live.
Your app reads patients and appointments through athenahealth’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.
athenahealth stays your system of record. BloomText handles the conversations, and nothing syncs until your app connects the two.
Read the patient from athenahealth, look up the matching BloomText conversation in your app’s own mapping, then post the message. Your app owns the mapping from an athenahealth patient ID to a BloomText conversation ID; nothing maps automatically.
GET https://<approved-athena-fhir-base>/fhir/Patient/<approved-patient-id>?_format=jsonAuthorization: Bearer <approved-access-token>Accept: application/fhir+jsonUse the base URL, access token, and IDs from your approved vendor environment.
See athenahealth Patient resource profile for the full request.
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.
athenaOne runs the front desk, schedule, and billing for outpatient practices, and its APIs expose the events a front desk cares about: bookings, cancellations, check-ins, and the waitlist. Most of these ideas use athenaOne APIs, which need a signed contract with athenahealth before they reach production.
athenaOne keeps a waitlist of patients who want an earlier visit, with the provider, department, days, and hours they prefer. When a Cancel Appointment event comes through, your app reads the waitlist entries for that provider and texts the first match that an earlier time opened up. Staff still book the slot in athenaOne.
Uses athenaOne appointment changed feed and Appointment Waitlist
Subscribe to the Check In event and post a short note to the care team’s conversation when a patient arrives, using initials and the visit time. Medical assistants see it on their phones without watching the athenaOne schedule.
Uses athenaOne appointment changed feed (Check In event)
athenaOne stores follow-up reminders, called appointment ticklers, with an approximate date for the next visit. A weekly job reads the ticklers coming due and texts each patient that it’s time to book their follow-up.
Uses athenaOne Appointment Reminders (ticklers)
For native athenaTelehealth visits, athenahealth asks practices to share its device-check link in patient messaging. Send it the day before so patients test their camera and microphone before the visit starts.
Uses athenaOne Appointment data for telehealth visits
When the front desk moves a visit, the changed feed reports the update. Your app texts the patient the new date and time in the same conversation they already use, so there is one thread per patient instead of scattered notices.
Uses athenaOne appointment changed feed
Poll the appointments changed feed every minute. When a visit is cancelled, offer the opening to the first waitlisted patient for that provider.
POST https://api.platform.athenahealth.com/v1/<approved-practice-id>/appointments/changed/subscriptionAuthorization: Bearer <approved-access-token>GET https://api.platform.athenahealth.com/v1/<approved-practice-id>/appointments/changedAuthorization: Bearer <approved-access-token>Accept: application/jsonGET https://api.platform.athenahealth.com/v1/<approved-practice-id>/appointments/waitlist?providerid=<approved-provider-id>Authorization: Bearer <approved-access-token>Accept: application/jsonPOST https://api.bloomtext.com/v1/conversations/{conversationId}/messagesAuthorization: Bearer bt_live_…Idempotency-Key: <unique-request-key>Content-Type: application/json{"body":"An earlier opening came up on Thursday at 3:40 PM. Reply YES and our front desk will move your visit."}Tell the medical assistants when a patient checks in, without anyone refreshing the schedule.
GET https://api.platform.athenahealth.com/v1/<approved-practice-id>/appointments/changedAuthorization: Bearer <approved-access-token>Accept: application/jsonPOST https://api.bloomtext.com/v1/conversations/{careTeamConversationId}/messagesAuthorization: Bearer bt_live_…Idempotency-Key: <unique-request-key>Content-Type: application/json{"body":"K.L. checked in for 2:15 PM with Dr. Rao."}Turn follow-up ticklers into a friendly nudge to book.
GET https://api.platform.athenahealth.com/v1/<approved-practice-id>/appointments/appointmentremindersAuthorization: Bearer <approved-access-token>Accept: application/jsonPOST https://api.bloomtext.com/v1/conversations/{conversationId}/messagesAuthorization: Bearer bt_live_…Idempotency-Key: <unique-request-key>Content-Type: application/json{"body":"It’s time to book your follow-up visit. Reply with a day that works and we’ll find a time."}A front-desk agent that can see the athenaOne schedule and write in BloomText can work the waitlist, answer "when is my visit?" replies, and flag same-day cancellations, while staff approve anything that changes the schedule.
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 few small tools that call athenaOne APIs with your approved credentials, such as "get changed appointments" and "get waitlist for provider". Keep booking and cancelling out of the toolset until you trust it. athenahealth has said it is building an MCP server for athenaOne and AI platforms like Claude; until that appears in its developer documentation, your own tools are the way in.
Every 10 minutes, check athenaOne for cancelled appointments today and tomorrow. For each one, find the highest-priority waitlist entry for the same provider and text that patient the open time. If they reply yes, post "Move <initials> to <time>" in the Front Desk conversation. Never book or cancel anything yourself.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. athenahealth offers three kinds: athenaOne APIs, its own REST endpoints with write access across scheduling, clinical, and billing work; FHIR APIs for USCDI clinical data; and Certified APIs, the FHIR R4 endpoints required for ONC certification. Production calls go to api.platform.athenahealth.com and testing calls to api.preview.platform.athenahealth.com.
Create an app in the athenahealth Developer Console. It gets sandbox access to Preview practice 195900 right away, with test patients. Apps that use only Certified APIs can self-onboard, and a practice turns them on from an admin page. athenaOne APIs need a contract through athenahealth Platform Services, then a technical spec, a solution validation demo, and a go-live form before you get production keys. athenaPractice and athenaFlow use a separate developer portal with Microsoft sign-in.
Yes. athenaOne sells patient engagement tools that include Patient Conversations, which offers two-way texting and secure chat, plus outreach messaging and waitlist notifications. If a practice already sends reminders from athenaOne, build around them instead of duplicating them. BloomText is useful for the conversations your own software drives and for staff chat.
Two ways. Changed Data Subscriptions are a polling feed: you subscribe once and call the changed endpoint, at least hourly, because unread events expire after 24 hours and unused subscriptions are removed after 7 days. Event Notifications push events such as Appointment.cancel and Appointment.check-in to your webhook in seconds, but they carry only IDs and require an updated API contract.
Yes, through tools you write. Wrap the athenaOne endpoints your contract allows as agent tools, and add the BloomText MCP server so the same agent can read and send messages. athenahealth has written that it is building an MCP server for athenaOne, but it is not in the public developer documentation yet.
It can be, if every party handling PHI is covered. BloomText issues API keys only to organizations with a signed BAA, and your use of athenahealth data runs under your contract with athenahealth and the practice. Keep messages to what the patient needs, like a time or a link, and leave clinical detail in athenaOne.
athenahealth has free certified FHIR APIs that practices can switch on themselves, and commercial athenaOne APIs that need a contract and an app review.
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.
