Read patient data from WellSky and coordinate care in BloomText conversations from your own software.
Get started for freeSchedule a demo →Yes. WellSky's personal care and hospice products offer APIs for shifts, clients, and care teams, and the BloomText API messages clients and families in BloomText conversations. Each WellSky product has its own access process.
Your app reads shifts, clients, and care teams through WellSky’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 reads new patient replies by time range.
WellSky stays your system of record. BloomText handles the conversations, and nothing syncs until your app connects the two.
Read Patient or DocumentReference data through the approved WellSky FHIR app, then message the matching BloomText patient and read their replies. Treat the FHIR and Connect products as separate integrations.
GET https://api.bloomtext.com/v1/patient-messages?patient_id={patientId}&q=from:patient&page[limit]=50Authorization: Bearer <api-key>POST https://api.bloomtext.com/v1/patient-messagesAuthorization: Bearer <api-key>Idempotency-Key: <unique-request-key>Content-Type: application/json{"to":{"patient_id":"{patientId}"},"body":"Visit schedule updated for next week. Reply with any questions."}Send your organization’s BloomText API key in the Authorization header on every request. POST requests also need Idempotency-Key and Content-Type headers.
WellSky’s APIs differ by product. The Personal Care Connect API covers home care shifts, clients, caregivers, and webhooks. The WellSky FHIR APIs, including the one for Hospice and Palliative, are read-only clinical data. These ideas are built for agencies whose caregivers and clinicians spend the day in the field.
Every evening, search each caregiver’s shifts for the next day and post the start times to the conversation they share with the scheduler. A caregiver who can’t make it replies in the thread, and the scheduler sees it before the morning scramble.
Uses WellSky Personal Care Appointment (shift) search
Families want to know who is coming and when. Search a client’s shifts by week number and post the visit times to the family conversation every Sunday. Leave caregiver phone numbers and care details out of the message.
Uses WellSky Personal Care Appointment (shift) search
Subscribe to the Connect API’s clock-out event. When a caregiver clocks out, your app posts a short “today’s visit wrapped up” note to that client’s family conversation, so the daughter at work doesn’t have to call the office.
Uses WellSky Personal Care Subscription (encounter.clockout.changed)
The practitioner.deactivated.changed event fires when a caregiver is deactivated. Your app removes that person from every client conversation they were in and tells the scheduler which clients need a new caregiver.
Uses WellSky Personal Care Subscription and Practitioner data
A hospice patient’s nurse, aide, social worker, and chaplain all need the same thread. Read the patient’s CareTeam from the Hospice and Palliative FHIR API and flag any differences from the BloomText conversation’s participants so staff can update it.
Uses WellSky Hospice and Palliative FHIR CareTeam and Practitioner reads
Patient requests use your organization’s BloomText API key. Posts to a staff team conversation use an org admin’s OAuth token instead, and only reach conversations that admin is part of.
A 6 PM job that sends each caregiver their shifts for tomorrow.
POST https://connect.clearcareonline.com/oauth/accesstokenContent-Type: application/json{"client_id":"<approved-client-id>","client_secret":"<approved-client-secret>","grant_type":"client_credentials"}GET https://connect.clearcareonline.com/v1/appointment/?caregiverId=<approved-caregiver-id>&startDate=<tomorrow-yyyymmdd>Authorization: Bearer <approved-access-token>POST https://api.bloomtext.com/v1/me/conversations/{caregiverConversationId}/messagesAuthorization: Bearer <org-admin-oauth-token>Idempotency-Key: <unique-request-key>Content-Type: application/json{"body":"Your shifts tomorrow: 8:00 AM and 2:30 PM. Reply here if anything changes."}A webhook listener that turns WellSky clock-out events into a one-line update in the family conversation.
POST https://connect.clearcareonline.com/v1/subscriptions/Authorization: Bearer <approved-access-token>Content-Type: application/json{"resourceType":"Subscription","status":"active","criteria":"encounter.clockout.changed","channel":{"type":"rest-hook","endpoint":"https://<your-app>/wellsky/clockout","payload":"application/fhir+json","header":["Authorization: Bearer <your-webhook-secret>"]},"meta":{"tag":[{"code":"agencyId","display":"<approved-agency-id>"}]}}POST https://api.bloomtext.com/v1/patient-messagesAuthorization: Bearer <api-key>Idempotency-Key: <unique-request-key>Content-Type: application/json{"to":{"patient_id":"{familyPatientId}"},"body":"Today’s visit wrapped up at 4:05 PM."}When WellSky reports a caregiver deactivated, give the scheduler a list of their clients who need coverage.
POST https://api.bloomtext.com/v1/me/conversations/{schedulingConversationId}/messagesAuthorization: Bearer <org-admin-oauth-token>Idempotency-Key: <unique-request-key>Content-Type: application/json{"body":"A caregiver was deactivated in WellSky. 3 clients need coverage starting Monday. Reply here for the list."}For a home care or hospice office, an agent with WellSky data and BloomText can answer “who is covering Mrs. Lee tomorrow?”, find shifts with no caregiver reply, and keep field staff in the right conversations.
An org admin creates an API key in BloomText. Your agent’s tools use it to message patients and read their replies, always naming the patient by ID, phone number, or MRN. The key can’t reach staff conversations; for those, the agent uses an org admin’s OAuth token, which reaches only the conversations that admin is part of.
GET https://api.bloomtext.com/v1/organizationAuthorization: Bearer <api-key>You give the agent WellSky data through a small tool you write, for example one that calls the Personal Care Connect API’s shift search with your agency’s client credentials, or a read-only WellSky FHIR app that your EHR vendor admin registered. WellSky promotes its SkySense AI features inside its own products, but it does not document an MCP server or a way to connect outside agents like Claude or ChatGPT.
Get tomorrow’s shifts from WellSky for all active caregivers. For each caregiver, read their BloomText conversation and check whether they replied to tonight’s shift reminder. Post a list of unconfirmed shifts, with times and client first initials only, to the scheduling conversation.Messages the agent sends with the key show the key’s name to staff, and patients see your clinic. An org admin can delete the key at any time. Read the AI agent docs.
Yes, and which one you use depends on the WellSky product. WellSky Personal Care has the Connect API, a public REST reference covering shifts, clients, caregivers, documents, and webhook subscriptions. WellSky also publishes read-only SMART on FHIR APIs, including one for WellSky Hospice and Palliative aimed at EHR partners.
For the Personal Care Connect API, the agency licenses it under WellSky’s Connect API Agreement and uses its client ID and secret to get tokens; anyone who isn’t the agency’s employee must sign Connect Access Terms first. For the WellSky FHIR API, only the EHR’s vendor admins can add your client app. For Hospice and Palliative, WellSky provides a registration form and the consolo.support@wellsky.com contact.
Yes. The Personal Care Connect API lets you create Subscription records that post to your rest-hook endpoint. Documented events include patient.created, encounter.clockout.changed, practitioner.deactivated.changed, and changes to client or caregiver names, addresses, and phone numbers.
WellSky Personal Care gives families the Family Room portal with the care calendar and shift notes, and WellSky Hospice and Palliative has a patient portal with Beacon chat. None of the WellSky API references we reviewed has an endpoint for sending text messages. BloomText holds the conversation, and your app decides what to post based on WellSky data.
Yes, with tools you build. Your agent uses BloomText through the BloomText API, with an organization API key. For WellSky, the agent calls your own tool that uses your licensed Connect API credentials or an approved FHIR app, because WellSky does not document an MCP server for outside agents.
It can be when every system that handles the data is covered. BloomText turns on API access only for organizations with a signed BAA. WellSky’s Connect API Agreement also limits who can use the data, so confirm your setup with WellSky. Keep messages to shift times and visit logistics, not care details.
WellSky's APIs differ by product. Personal Care has the Connect API, with shift data and webhooks behind a license key. Hospice and other products offer read-only FHIR APIs that an admin registers.
API access is available to organizations with a signed BAA. Book a short call, tell us what you’re building, and we’ll turn on API access so an org admin can create your key. Don’t include PHI when you book.
Links last checked September 21, 2026.
