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.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Luma Health the way a machine reads it — 65 machine-readable artifacts across 1 API, 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 51.2/100 (developing), with a separate agent-readiness read of 29/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Luma Health's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/luma-health/"
title="Luma Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/luma-health.svg"
alt="Luma Health Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/luma-health/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/luma-health/"
title="Luma Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/luma-health/card.svg"
alt="Luma Health Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
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 58
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 Appointments API
Patient's appointments to see a doctor
Luma Health Appointment Types API
EHR appointment types
Luma Health Assistant Actions API
Audit log of individual tool calls made by the Navigator AI assistant during a conversation
Luma Health Assistant Instances API
Conversations between the Navigator AI assistant and a patient or staff member
Luma Health Assistant Transfer Rules API
Transfer rules for AI assistants (Navigator) to handle call routing
Luma Health Auth API
Luma Client Access
Luma Health Availabilities API
EHR provider scheduler availability
Luma Health Billing Charges API
Financial charges tracked against a patient, such as copays and patient balances
Luma Health Billing Copays API
Copay amounts configured per source (system, EHR, or manual) and referenced by patient form templates
Luma Health Broadcast Templates API
The Broadcast Templates API from Luma Health — 2 operation(s) for broadcast templates.
Luma Health Broadcast Events API
Broadcast event logs and history
Luma Health Broadcast Flows API
Broadcast flows for mass messaging campaigns
Luma Health Campaigns API
Contact preference campaigns that determine how and in what order a patient, facility, or user is contacted
Luma Health Chat Activities API
conversations with a patient
Luma Health Chat Activities Reasons API
reason why a chatActivity was closed
Luma Health Chat Audits API
Audits for message chat
Luma Health Checklists API
Per-appointment, per-patient instances of required pre-visit tasks generated from a checklist template
Luma Health Checklist Templates API
Reusable definitions of required pre-visit tasks used to build checklists
Luma Health Custom Web Styles API
custom styles, CSS, logo images for customers
Luma Health Engagement Events API
Append-only history of events that occurred during an engagement
Luma Health Engagements API
Conversation sessions between the system and a recipient, driven by one or more AI agents
Luma Health Engagement Settings API
Reusable voice and language presets that can be attached to an engagement
Luma Health Estimates API
Estimates
Luma Health Facilities API
Customer facilities
Luma Health Feedback Responses API
Patient responses to NPS feedback surveys and clicks on feedback links
Luma Health Feedback Responses External Review Replies API
AI-generated reply drafts for external reviews, with approve/reject workflow
Luma Health Feedback Responses External Reviews API
Scraped external reviews from Google Business Profile and Yelp
Luma Health Feedback Responses Promoter Histories API
Per-patient platform rotation history for NPS promoter review requests
Luma Health File Uploads API
File Uploads
Luma Health Groups API
Group of staff users
Luma Health Insurance Payors API
Insurance payors/carriers maintained in Luma's payor directory
Luma Health Insurances API
Patient insurance coverage records
Luma Health Knowledge Base Question Answers API
Question and answer entries for knowledge bases
Luma Health Lumabot Flows API
LumaBot Flows answered by patients
Luma Health Lumabot Flow Templates API
Templates for LumaBot flows
Luma Health Messages API
Messages (chat, sms, voice, email, whatsapp, fax, in-app)
Luma Health Message Template Partials API
Reusable partials that can be composed into message templates
Luma Health Offers API
Offers
Luma Health Outbound Referrals API
Outbound Referral
Luma Health Patient Credit Cards API
Luma Health patient credit cards
Luma Health Patient Forms API
Patient forms answered by patients
Luma Health Patient Form Templates API
Templates from patient forms
Luma Health Patient Message Templates API
Message templates used to compose patient communications
Luma Health Patients API
Customer patients
Luma Health Providers API
Luma Health providers
Luma Health Provider Scheduling Groups API
Groups of providers configured for shared scheduling behavior, such as round-robin or waterfall assignment
Luma Health Queue Manager Instances API
Instances of queue manager templates representing items in a queue
Luma Health Recalls API
Recalls
Luma Health Referrals API
Luma Patient referrals
Luma Health Reminders API
Luma Reminders
Luma Health Reports API
Luma Analytical Reports
Luma Health Schedulers API
Scheduler
Luma Health Settings API
Luma resource settings
Luma Health Specialties API
A Doctor's specialty
Luma Health Squigglies API
Messages Squigglies
Luma Health System Audits API
Audit logs for certain system events in a given account
Luma Health Users API
Staff users
Luma Health Waitlists API
Patients waiting for an appointment
Scroll within the panel for all 58 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Luma Health Rate Limits
RATE LIMITSSecurity Posture 4
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, ISO/IEC 42001 (AI management system, for Luma AI products), HIPAA, TX-RAMP Level 2, EU-US Data Privacy Framework (with UK and ...
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 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 2
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
This is an independent, third-party profile of Luma Health, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.