Platform / Developers
Developer Platform
Real APIs, a sandbox, and services that run 24/7.
Care Daily is an open AI and IoT platform, not a closed appliance. Two documented REST APIs, a WebSocket for live subscriptions, event streaming into your own infrastructure, MQTT for your own hardware, and a Python framework for building services that run continuously on top of it all.
How you build on it
Two APIs
One for the application, one for the operator.
The Application API is what a product talks to: devices, locations, measurements, rules, subscriptions. The Admin API is what an organization runs on: its hierarchy, its people, reports, billing, firmware, and EHR connections. Both are at version 62 and both are published.
Application API, by group
OpenAPI specifications are published for both, so you can generate a client in your own language rather than hand-rolling one. Note what the group list tells you about the platform: professional monitoring, energy management, weather and a rules engine are first-class parts of the API surface, not bolt-ons.
https://app.peoplepowerco.com/https://eu.caredaily.ai/https://sboxall.peoplepowerco.com/Four ways data moves
Pick the transport that suits what you are building.
Most platforms give you REST and stop. Which transport you need depends on whether you are rendering a screen, reacting in real time, feeding a data warehouse, or bringing your own hardware.
REST
The documented Application and Admin APIs. Standard verbs, JSON responses, ISO 8601 timestamps and consistent result codes. This is where you start.
WebSocket
A persistent connection for live subscriptions. Authenticate with an API key from the Login API, then subscribe to narrative updates, location state variables from Synthetic APIs, device parameter changes and SIM attributes, each filtered by a create, update and delete bitmask.
Event streaming
Push events straight into your own infrastructure through AWS SQS, AWS EventBridge, Kafka and others. Available streams include location and organization narratives, location and time-series state, paid service lifecycle events, bot errors and location events.
MQTT over AWS IoT
Bring your own hardware. Devices publish and subscribe through the broker using X.509 certificates and a topic prefix scoped to the device, with optional custom authorization that generates an IoT policy per connection.
# Live subscriptions: connect, authenticate, then subscribe. # Connection settings come from the Get Server Instance API with type=wsapi. { "id": 1, "goal": 1, "key": "<API key from the Login API>" } { "id": 2, "goal": 2, "type": 3, "operation": 3 } # location state, create + update # The server then pushes data messages as things change. { "goal": 6, "state": { "..." }, "operation": 2 } # Heartbeat is deliberately tiny: send "?", receive "!".
Extend the platform itself
Synthetic APIs: add endpoints we never wrote.
Most platforms let you consume their API. Care Daily lets you add to it. A bot declares which data stream messages it accepts as input, and publishes state variables containing arbitrary JSON as output. Your application then reads those state variables back over REST or WebSocket exactly as if they had always been part of the platform.
The result is an asynchronous API of your own design, running inside the platform, with the platform's auth, hierarchy and role-based access already applied to it. Published Synthetic API libraries already cover things like dashboard composition, messaging and specific device integrations.
Because the platform has first-class Subscriptions endpoints and emits paid service lifecycle events, a service you build this way can sit behind a paid subscription and be activated per location rather than shipped to everyone.
Why this matters
It is the difference between building on someone's product and building on someone's platform. If the capability you need does not exist, you are not waiting on our roadmap. You write the bot, expose the state, and your application consumes it through the same API surface as everything else.
BotLab
Services that run 24/7, not scripts you have to babysit.
BotLab is our Python microservices framework. A bot is a background service that runs continuously against real-time and historical data from connected devices, and coordinates events from partner services, manufacturers and other platforms.
The BotEngine framework
Microservices in a language your team already has. Analyze time-series data, react to real-time events, and run local executions for continuous monitoring.
No servers of your own
The platform hosts your bots, so there is no infrastructure to stand up. During development they can also run live on your own machine through the CLI.
Public and inspectable
BotLab is on GitHub. You can read exactly how the services that run our own products are built, and start from them rather than from a blank file.
The framing we like: a bot makes products do things the manufacturer never imagined. The same relationship a mobile developer has to a phone, a bot developer has to a home.
Getting started
What actually happens when you ask.
Sandbox credentials
You get access to the sandbox environment and the published specifications, so you can generate a client and make real calls the same day.
A technical conversation
Not a sales call. Someone who has built on this platform walks through your architecture and tells you which transport fits and where the sharp edges are.
A path to production
US or EU hosting, or your own infrastructure under an enterprise license, with the same APIs either way.
Application and Admin API reference
The full published documentation, including the OpenAPI specifications for both APIs and the device-side reference.
Open the API docs → Guides · GitHubPlatform guides and BotLab
WebSockets, event streaming, MQTT and Synthetic APIs, plus the BotLab framework and example bots.
Browse on GitHub →Get access to the APIs.
Tell us what you are building and we will get you documentation, credentials, and someone technical to talk to.
- Open APIs, events and MQTT
- Build services that run 24/7
- A real engineer on the other end
Thank you, that is with us.
Care Daily reads what comes in and routes it to whoever is best placed to answer.