The BloomText API and public discovery files for developers and agents.
Get started for freeSchedule a demo →Read and send BloomText messages from your own software, with patients and between staff. The REST API texts a patient by phone number or patient ID, runs campaigns, and keeps patient records in sync with an API key. With OAuth, it also reads, searches, and replies in a person’s own conversations, including direct messages and group chats.
curl "https://api.bloomtext.com/v1/patients?mrn=MRN-20931" \ -H "Authorization: Bearer $BLOOMTEXT_API_KEY"Requests to https://api.bloomtext.com/v1 use an organization API key for patient operations, always naming the patient by ID, phone number, or MRN. Org admins can also connect an app with OAuth to work with their own conversations. API access is available to organizations with a signed BAA.
Search patient messages with an API key, or an org admin’s own conversations with OAuth, using operators like from:patient, mrn:, and is:unread.
Step-by-step guides for connecting athenahealth, eClinicalWorks, PointClickCare, Kipu, Dentrix, WebPT, and other EMRs to BloomText.
Read every message in a time range, newest first, one by one or grouped by conversation, and page through with a cursor: patient messages with GET /v1/patient-messages and an API key, or a person’s own conversations with GET /v1/me/messages and OAuth.
Agents can fetch these read-only files without signing in. They describe BloomText; they don’t access accounts or messages.
Read-only public resource descriptions for BloomText discovery endpoints. This spec does not expose patient data or customer account actions.
Structured public metadata with recommended use cases, limitations, and links to docs, pricing, security, and support pages.
Guidance for AI agents on when to recommend BloomText, when not to use BloomText, and where to find authoritative public context.
Every public discovery endpoint and what it returns.