WebPT stays your clinical and scheduling system. The BloomText API sends and reads the patient messages around it.
Get started for freeSchedule a demo →WebPT doesn't offer a public API, but it connects to other systems through HL7 interfaces it sets up with you. Pair those feeds with the BloomText API to message patients and staff, or simply run WebPT and BloomText side by side.
Your app receives the HL7 registration and documentation feeds WebPT sets up for your account.
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.
WebPT stays your system of record. BloomText handles the conversations, and nothing syncs until your app connects the two.
Build the BloomText side first with the read and post calls below, then connect the HL7 feed WebPT sets up for your account.
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 therapy session moved to Wednesday at 4:00 PM."}Send your API key in the Authorization header on every request. POST requests also need Idempotency-Key and Content-Type headers.
WebPT doesn’t offer a public REST API. It connects to other systems through HL7 interfaces its integration team sets up per clinic: inbound patient registration, outbound billing, outbound documentation, inbound documentation, and custom work. These ideas start from those feeds, received by your own interface engine or listener.
When a hospital or physician group sends a registration (ADT) message that creates the patient in WebPT, your listener sees the same message. It posts a welcome in the patient’s BloomText conversation with what to bring to the first visit and how to finish intake.
Uses the inbound HL7 ADT patient registration feed
WebPT sends an MDM or ORU message whenever a document is completed. Your app turns that into a one-line post in the internal team conversation so the front desk knows to fax the progress note or plan of care to the referring provider.
Uses WebPT outbound documentation (HL7 MDM/ORU)
When the discharge summary comes through the documentation feed, schedule a check-in two weeks later asking how the home program is going. Replies go to the treating therapist’s inbox in BloomText instead of a voicemail box.
Uses WebPT outbound documentation (HL7 MDM/ORU)
WebPT’s outbound billing interface sends ADT, BAR, and DFT transactions to your billing system. Mirror a count of the day’s charge batches into the billing team’s conversation so someone notices when a clinic hasn’t sent any.
Uses WebPT outbound billing (HL7 ADT/BAR/DFT)
A plan of care often calls for two or three visits a week, and one missed visit can stall progress. Scheduling data isn’t in WebPT’s standard interface list, so ask WebPT about a custom integration before you build outreach for cancellations and no-shows.
Uses a custom WebPT interface, if WebPT agrees to build one
A small HL7 listener that posts to the front office conversation each time a therapist signs a note in WebPT.
POST https://api.bloomtext.com/v1/conversations/{frontOfficeConversationId}/messagesAuthorization: Bearer bt_live_…Idempotency-Key: <unique-request-key>Content-Type: application/json{"body":"Progress note signed for chart 48213. Ready to send to the referring provider."}Send a first-visit welcome as soon as a referring system registers the patient.
POST https://api.bloomtext.com/v1/conversations/{conversationId}/messagesAuthorization: Bearer bt_live_…Idempotency-Key: <unique-request-key>Content-Type: application/json{"body":"Welcome to Desert Ridge Physical Therapy. Wear comfortable clothes to your first visit and arrive 15 minutes early to finish your forms."}GET https://api.bloomtext.com/v1/conversations/{conversationId}/messages?page[limit]=10Authorization: Bearer bt_live_…For a rehab clinic, an agent that sees WebPT interface events and your BloomText conversations can draft patient check-ins, route replies to the right therapist, and keep the front office posted on paperwork.
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_…" } } }}WebPT doesn’t document an MCP server or a public API an agent could call. The practical path is to store the HL7 events your interfaces receive in your own database and give the agent a small read-only tool over that store, such as “list documents completed today.”
Look at yesterday’s WebPT discharge summaries in our interface store. For each patient discharged exactly 14 days ago who has a BloomText conversation, send a short check-in asking how their home exercises are going. List any patient without a conversation in the front office thread.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.
Not a public one. WebPT doesn’t publish a developer portal or self-serve API keys. It integrates through HL7 interfaces that its team sets up and monitors: inbound patient registration, outbound billing, outbound documentation, inbound documentation, and custom integrations.
Contact WebPT through its integrations or partners page. For a clinic’s own project, WebPT assigns a point of contact for the interface build. For a product you want to offer to many clinics, use the partner inquiry on the partners page.
Yes. WebPT’s scheduling product sends automated text, phone, and email reminders to scheduled patients. Clinics use BloomText for the conversations around that: two-way patient messaging and HIPAA-compliant team chat, driven from their own software through the BloomText API.
Scheduling isn’t one of WebPT’s standard interface types. Ask WebPT whether a custom integration can cover it for your clinic before you plan reminders around it.
WebPT doesn’t document a connector for AI agents. You can give an agent access to the events your HL7 interfaces receive through a tool you write, and connect it to BloomText through the BloomText MCP server.
It can be when each system is covered. BloomText issues API keys only to organizations with a signed BAA, and your interface listener and database need the same safeguards. Keep texts to logistics like visit times and paperwork, not diagnoses or progress details.
WebPT integrates through HL7 interfaces, such as registration, billing, and documentation feeds, that WebPT configures and monitors. There's no self-serve developer signup.
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.
