Make Getwello part of your house.
Most family apps make you live inside their app. We give you a quiet way to make Getwello part of the rest of your home, so when Mum checks in at 8:14, your kitchen speaker can softly say so, your watch can buzz when a day goes quiet, and your AI assistant can answer “how is she doing this week?” without you opening anything.
Public REST API, an open-source MCP server for Claude and any MCP-compatible AI, and outbound webhooks for Home Assistant. All three live. No extra cost. Cancel anything any time.
What this is, without the jargon.
Getwello already does the quiet daily check-in well, on its own. The Developer API is an extra door, off to the side, that you can choose to open if you want Getwello to talk to the rest of your house.
You do not need to be a developer to benefit. You do need either a technically minded family member, or a no-code tool like Home Assistant or n8n, to wire it up. Once it is wired up, it sits quietly in the background forever.
The kind of thing it can do: announce on your kitchen speaker when today's check-in lands; turn on Mum's porch light at 10am if she hasn't checked in yet; let Claude answer a question about the week without you opening the app; mirror the Family Room into your normal family WhatsApp for the sibling who refuses to download another app.
And because you bring your own AI (if you use one), you never pay us a penny extra. The Developer API is included in the £4.99 family plan, full stop.
A small thing that quietly changes your day.
Here is a real Tuesday morning at the O'Meara house, with the Developer API set up to pipe the check-in through a kitchen speaker and an Apple Watch.
- 08:14
Mum taps her check-in.
Same thing she has done every morning for nine months. One big button. She does not see, hear, or know about any of the technology underneath.
- 08:14
The speaker in the kitchen says it.
Sarah is making the school lunches. The kitchen Sonos quietly says “Mum has just checked in.” No phone in hand, no notification, no friction. She breathes out.
- 13:30
Sarah asks Claude on her phone.
During a meeting break, she asks Claude “anything from Mum today?” Claude has the Getwello MCP server installed, so it tells her: checked in at 8:14, mood fine, brother visiting Thursday afternoon. No app to open.
- 20:42
The watch buzzes for a different reason.
At 11pm yesterday the brother posted in the Family Room about the GP appointment. The same integration that announced the check-in also mirrored the room message to Sarah's watch. She reads it on her wrist while putting the kettle on, no scrolling, no double-checking.
None of this is dramatic. That is the point. It is the kind of quiet support a phone notification cannot offer.
Four parts. Three of them are yours.
The whole thing is intentionally a thin layer. We do not try to own your AI, your speakers, or your home network. We just give you a clean way to read and act on your Circle's data from wherever you already build things.
The bit that lets your AI talk to Getwello.
MCP stands for Model Context Protocol. It is a standard way for AI assistants (Claude, ChatGPT, Gemini, local models you run yourself) to take actions in your tools.
Think of it like USB-C for AI assistants. Any AI that speaks MCP can plug into any app that speaks MCP. The AI does the thinking; the app provides the data.
We are building a Getwello MCP server right now. Once it ships, you install it once on your laptop or home server, and Claude (or whichever AI you prefer) can answer real questions like:
- “Has Mum checked in today?”
- “Who is visiting her this week?”
- “What did my brother say in the Family Room yesterday?”
- “Post a message in the Family Room saying I am picking up the prescription.”
The MCP server is live and open-source. Install it with npx @getwello-app/mcp-server, drop the snippet below into your Claude Desktop config along with an API key minted from Settings → Developer API, restart Claude. That's it.
Six concrete examples.
You do not need any of these. They are here to give you a sense of what the API supports. Each one is a small everyday thing, not a Big Idea.
The kitchen speaker softly announces the check-in.
A two-line Home Assistant automation polls the API every minute or two. When today's check-in lands, the Sonos in the kitchen says it. Volume is set low. Nobody is jolted. Sarah is just making lunches and hears 'Mum's just checked in,' and that is the whole morning's worry solved.
Mum's porch light reminds her to tap.
If no check-in by 10am, an automation turns on her porch light to a soft amber for ten minutes. She walks past it on the way to the kettle, sees the gentle nudge, taps the app. No phone alarm, no anxiety. The lights are something she already trusts.
The watch buzzes the moment a day goes quiet.
When status flips to 'missed' on a check-in, an n8n workflow fires a Pushover notification to the Coordinator's Apple Watch with the Critical priority. Bypasses Do Not Disturb. The thing the family worries about, surfaced in the system they already trust.
Ask Claude how the week is going.
On the laptop after dinner, the Coordinator types 'how's Mum's week been?' into Claude. Claude (via the Getwello MCP server) pulls the last seven days of check-ins, mood ratings and visits. Reads the answer out conversationally. No app to open, no spreadsheet to read.
Family Room mirrored to your existing chat.
Two siblings refuse to download another app, and the family chat lives in WhatsApp anyway. A webhook on family_room.message_posted mirrors every Family Room message into a private channel the family already uses. Everyone sees, nobody has to switch tools.
A daily summary, generated locally, never leaves the house.
A Coordinator running a local Ollama model on a NAS pulls the day's check-ins and visits, has the model summarise them in plain language, and emails the summary to the siblings. The most privacy-conscious option: even Mum's first name never crosses the WAN.
We've already documented 26 integrations.
Before you write code, check whether your platform is already covered. We maintain step-by-step setup guides across 8 categories: AI assistants, smart speakers, smart home, team chat, automation, notifications, productivity and calendar. Each one is opinionated, includes working code, and gets you from API key to live in well under an hour.
Fourteen endpoints across reads, writes and aggregates.
v1 covers the everyday surface a Coordinator's integration actually needs: the data, the aggregates an AI can answer broad questions from, and a small set of carefully-scoped writes. The MCP server and webhooks are also live, so everything below has both polling and push paths available.
Discovery
/api/v1/circlesList your Circles
Returns the Circles your API key can touch, with member counts and a Companion-mode flag.
/api/v1/circles/{id}/membersMembers of a Circle
Display name, role, avatar, and Companion-mode flag. Emails and phone numbers are deliberately not exposed.
Check-ins and calendar
/api/v1/circles/{id}/check-insRecent check-ins
Today's check-in, or the last week's, or whatever window you pass. Includes mood when Companion mode is on.
/api/v1/circles/{id}/visitsVisit calendar
Who is visiting, when, what they said in the note. From and to timestamps for any window you want.
/api/v1/circles/{id}/visitsSchedule a visit
One-off only. Visitor is always the API key's owner; integrations cannot schedule on behalf of others. Max 12h duration, max 1 year ahead.
/api/v1/circles/{id}/visits/{visit_id}Cancel a visit
Only the original scheduler can cancel via API. Completed visits are protected. Full audit trail preserved.
Family Room
/api/v1/circles/{id}/family-roomRead messages
The thread, newest first. Deleted messages come through with their body nulled out, never the original text.
/api/v1/circles/{id}/family-roomPost a message
Submit a message as the key's owner. Always tagged 'via integration' in the in-app feed so the family can tell it came from an automation.
/api/v1/circles/{id}/family-room/{message_id}Retract a message
Soft-delete a message posted by the same integration key. Cannot delete human-typed messages or messages posted by a different key.
Aggregates, status, and Family Map
/api/v1/circles/{id}/statsCircle stats
Adherence percentages, mood trend, upcoming visit counts, gap-day count, current well-streak. The one-shot snapshot an AI uses to answer 'how is the week going?' in a single call.
/api/v1/circles/{id}/gapsGap days
Days in the next N (default 14) with no scheduled visit. Each returned with its day-of-week so a model can suggest filling them.
/api/v1/circles/{id}/notificationsYour notifications
What you've been notified about in this Circle. Scoped to the key's owner; never exposes another user's feed.
/api/v1/circles/{id}/placesFamily Map places
Saved Circle-wide places: Home, GP, the gym, etc. Personal places of other users stay private.
/api/v1/circles/{id}/subscriptionSubscription status
State, renewal date, days remaining, cancel-at-period-end flag. Lets an integration proactively warn before access lapses.
Three commands to your first answer.
If the rest of this page looked unfamiliar, you can skip this section. The non-technical Coordinator working with a family member or a no-code tool does not need to read any code.
- Step 1
Mint a key in the app.
Sign in as a Coordinator. Open Settings, then Developer API. Give the key a name (something like “Home Assistant on the home server”), and copy the token. You will only see it once.
gw_live_abcd1234ef567890abcd1234ef567890 - Step 2
List your Circles.
The first call. Confirms the key works, and tells you which Circle IDs to use in the calls below.
curl https://getwello.co.uk/api/v1/circles \ -H "Authorization: Bearer gw_live_..." # { # "circles": [ # { # "id": "9d3...", # "name": "The O'Meara Family", # "member_count": 4, # "companion_mode_active": true, # "family_map_enabled": false, # "created_at": "2026-03-01T08:00:00Z" # } # ] # } - Step 3
Read today's check-ins.
The single most useful call. Returns recent check-ins, newest first. Pair it with a polling loop or a no-code automation and you have your kitchen speaker announcement.
curl "https://getwello.co.uk/api/v1/circles/$CIRCLE/check-ins?limit=5" \ -H "Authorization: Bearer gw_live_..." # { # "check_ins": [ # { # "id": "5a2...", # "status": "well", # "mood": "fine", # "for_local_date": "2026-06-08", # "checkin_member_user_id": "a1b...", # "created_at": "2026-06-08T08:14:32Z" # } # ] # }
What an integration can do, and what it cannot.
A short list, written deliberately on both sides. The “cannot” side is shorter but more important.
- Read check-ins, visits, members and Family Room messages for Circles the key owner Coordinates.
- Post messages in the Family Room (tagged 'via integration' so the family can tell).
- Be revoked instantly from /app/settings/developer.
- Be replaced. You can mint a new key, swap it in, and revoke the old one without any downtime.
- Tap 'I'm well' on behalf of a Check-in Member. The daily check-in is a human act, by design.
- Send voice replies, photos or hellos as the Check-in Member.
- Read any data outside Circles the key owner Coordinates.
- Survive a subscription lapse or a role demotion. Both stop access the same day.
subscription_required. The key itself is not deleted. Resubscribing restores access without you needing to mint a new one.MCP server and webhooks, ready to use.
The two pieces that turn polling into a proper integration. Both are included in the £4.99 plan, both work with the same API key, both go live the same day you mint it.
MCP server
@getwello-app/mcp-server. Wraps the REST API in the Model Context Protocol so Claude Desktop, Cursor and any MCP-compatible agent can query Getwello directly. Add the snippet below to your Claude Desktop config, drop in your API key, restart Claude. You're live.{
"mcpServers": {
"getwello": {
"command": "npx",
"args": ["-y", "@getwello-app/mcp-server"],
"env": {
"GETWELLO_API_KEY": "gw_live_..."
}
}
}
}Outbound webhooks
POST https://your-receiver.example.com/webhook
X-Getwello-Event: check_in.created
X-Getwello-Timestamp: 1717840923
X-Getwello-Signature: t=1717840923,v1=8f7d...
{
"event": "check_in.created",
"occurred_at": "2026-06-08T08:14:32Z",
"circle_id": "9d3...",
"data": {
"check_in_id": "5a2...",
"checkin_member_user_id": "a1b...",
"status": "well",
"for_local_date": "2026-06-08"
}
}Full setup guide for the MCP server lives on the npm package page. Webhook receiver examples (Home Assistant, n8n, Cloudflare Worker) are in the roadmap queue.
Frequently asked questions
Do I have to be a developer to use this?
No. The feature is for anyone who wants Getwello to fit into the rest of their home, whether that is a smart speaker, a Home Assistant setup or simply a phone notification on a specific person's watch. You will need either a technically minded family member, or a no-code tool like Home Assistant or n8n, to wire it up. The setup is short and we have step-by-step examples below.
What is MCP, in plain English?
MCP stands for Model Context Protocol. It is a standard way for AI assistants like Claude or ChatGPT to talk to apps. Think of it like USB-C for AI assistants: any AI that speaks MCP can plug into any app that speaks MCP. We publish an open-source Getwello MCP server so that Claude, on your laptop or phone, can answer questions like 'how is Mum doing this week?' without you having to open the Getwello app yourself. Install it with one npx command, drop your API key into your Claude Desktop config, restart Claude. Done.
Does the Developer API cost extra?
No. It is included in the £4.99 a month family plan. You bring your own AI subscription if you use one (Claude, ChatGPT, a local Ollama model) and we do not pay for any of those tokens. We only charge you for being a Getwello customer.
Who can create API keys?
Only Coordinators. Support Members and Check-in Members do not see the developer settings page. If you are a Support Member who wants integration access, ask the Coordinator in your Circle to mint a key for you.
What happens to my API key when my subscription ends?
API access stops the same day your subscription lapses. The key itself is not deleted. When you resubscribe, the same key works again, no need to mint a new one or update your integrations.
Can an integration check in on behalf of a Check-in Member?
No, by design. The check-in is a human emotional act and automating it would defeat the entire point of the product. Integrations can read check-ins, post in the Family Room (clearly tagged 'via integration'), and read the visit calendar. They cannot impersonate a Check-in Member, send voice replies as them, or generate fake check-ins.
Where is my data when an integration uses the API?
Your Circle data stays on our UK and EU servers. The API returns it to your integration; what your integration does with it (running locally, sending to Claude or ChatGPT, displaying it on a kitchen speaker) is entirely your choice. If you use a local AI model via Ollama, your loved one's data never leaves your house.
Why do this, when no other family app does?
Because we think family software should not be a closed box. Tunstall, Careline and Lottie do not let you connect their systems to anything else. We believe the families who would set up a smart-speaker check-in announcement are exactly the ones who get the most value from the product, so we make it possible at the standard price.
Open the door.
Make Getwello part of your house.
Sign in as a Coordinator and mint your first API key in two minutes. Included in the £4.99 family plan.
