BloomText API

The BloomText API lets your software take part in BloomText conversations. Read messages as they arrive, reply in threads, react, manage who’s in a conversation, check broadcast delivery, and export conversation history, all over a REST API with JSON bodies.

Your integration acts as an app user: a named, non-human member of your organization. Your team sees it in conversations like any other participant, and it can only reach the conversations it has been added to.

What you can build

• Reminders and notifications: post appointment reminders or intake nudges into a patient’s conversation from your EMR or scheduling system. See Send appointment reminders.
• Two-way workflows: turn patient replies into actions in your own system, like confirming an appointment. See Handle patient replies.
• AI assistants: let an agent answer routine questions and hand anything clinical to your staff. See Build an AI agent.
• Records and compliance: export a conversation’s history on a schedule and file it with the patient’s chart. See Export conversation history.

How it works

1. An organization admin creates an app user for your integration and issues it an API key.
2. Admins add the app user to the conversations it should work in.
3. Your app reads and writes those conversations with the API, and listens for changes with webhooks.

Access

API keys are issued to organizations with a signed BAA. Request API access and we’ll set up your app user and first key.