Luma Health
Luma Health is a United States patient-engagement (Patient Success) platform for healthcare provider organizations, headquartered in San Francisco, California. Its operational AI platform automates the patient journey - self-service scheduling and appointment management, referral and waitlist management, intake and digital forms, omnichannel two-way messaging and broadcast, appointment reminders and recalls, insurance eligibility verification, payments and billing, and a conversational AI assistant (Navigator / lumabot) - and integrates bidirectionally with the major EHRs (Epic, Oracle Health/Cerner, MEDITECH, eClinicalWorks, athenahealth, NextGen, Greenway, Nextech). Luma exposes a documented public REST API (Rest-Service v2.0.0, OpenAPI 3.0.0) at https://api.lumahealth.io/api/v2, secured with OAuth2 client-credentials that issue JWT bearer tokens. The developer-facing surface is a REST API rather than an HL7 FHIR server; FHIR/HL7 interoperability with EHRs happens inside Luma's integration layer, not as a public FHIR endpoint.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Luma Health the way a machine reads it — 17 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Luma Health scores 44.8/100 (thin), with a separate agent-readiness read of 65/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Luma Health
Each block below is one kind of artifact we hold for Luma Health. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Luma Health Scheduling & Appointments API
Self-service scheduling, appointment lifecycle, appointment types, provider availabilities, schedulers, offers, recalls, and waitlist management.
Luma Health Patients API
Patient demographics and records, patient forms and form templates, and patient stored credit cards.
Luma Health Providers & Facilities API
Providers, provider scheduling groups, facilities, specialties, groups, and platform users.
Luma Health Messaging & Engagement API
Two-way patient messaging, engagements and engagement events/settings, appointment reminders, and patient message templates.
Luma Health Broadcast & Campaigns API
Broadcast events, broadcast flows and templates, and outreach campaigns for population-level patient messaging.
Luma Health Intake & Forms API
Digital intake via checklists and checklist templates, patient forms and form templates, and file uploads.
Luma Health Billing & Payments API
Billing charges and copays, cost estimates, and patient credit-card payment instruments.
Luma Health Eligibility & Insurance API
Insurance records with real-time eligibility verification and the insurance payors directory.
Luma Health Referrals API
Inbound and outbound referral management across the care network.
Luma Health Conversational AI Assistant API
Conversational AI assistant surfaces - assistant instances and actions, lumabot flows and templates, knowledge-base question/answers, chat activities, and queue-manager routing.
Luma Health Reporting & Audits API
Operational reports plus system and chat audit trails.
Luma Health Authentication API
OAuth2 client-credentials authentication - generate and rotate client id/secret and exchange them for JWT access tokens (including subaccount tokens).
Scroll within the panel for all 12 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
luma-health-mcp.yml
MCP SERVERSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Luma Health Trust Center
HITRUST CSF r2, SOC 2 Type II, ISO/IEC 27001:2022, HIPAA, TX-RAMP Level 2
SECURITYAgentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Luma Health — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/luma-health · machine-readable index on apis.io