How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Luma Health Checklists API

Per-appointment, per-patient instances of required pre-visit tasks generated from a checklist template

Luma Health Checklists API is one of 58 APIs that Luma Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Checklists. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 7 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.lumahealth.io/api/v2.

7 operations 4 paths 10 schemas 1 DELETE2 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.lumahealth.io/api/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Luma Health Checklists API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 2 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

checklists 7

Per-appointment, per-patient instances of required pre-visit tasks generated from a checklist template

GET
/checklists
List checklists
checklistsList 14 params → 200401403
POST
/checklists
Create a checklist
checklistCreate body → 201401403
GET
/checklists/{checklistId}
Get checklist by id
checklistGet 1 param → 200401403
PUT
/checklists/{checklistId}
Update a checklist
checklistUpdate 1 param body → 200401403
DELETE
/checklists/{checklistId}
Delete a checklist
checklistDelete 1 param → 200401403
POST
/checklists/replace
Build a checklist from a template, replacing an appointment's checklist
checklistReplace body → 200401403
POST
/checklists/send
Send a patient's checklist message
checklistSend body → 200401403

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ChecklistRequestCreate (15 properties), ChecklistRequestUpdate (15 properties), ChecklistResponse (15 properties). Each schema is shown below with its type and property counts.

ChecklistRequestCreate
object
15 properties 5 required
userParam
string
The ID of the root account user.
ChecklistResponse
object
A Checklist is a per-appointment, per-patient instance of required pre-visit tasks (forms, insurance, consent, payment) generated at build time from a Checklis…
15 properties
idParam
string
Luma's internal ID of an object.
updatedAtParam
string
The date/time when this object was updated.
createdAtParam
string
The date/time when this object was created.
updatedByParam
string
The ID of the user who updated this object.
ChecklistRequestUpdate
object
15 properties
deletedParam
number
Flag for logical deletion where 1 means deleted.
createdByParam
string
The ID of the user who created this object.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

luma-health-checklists-api-openapi.yml Raw ↑

Other APIs Luma Health publishes across the network.

Luma Health Appointments API
Luma Health Appointment Types API
Luma Health Assistant Actions API
Luma Health Assistant Instances API
Luma Health Assistant Transfer Rules API
Luma Health Auth API
Luma Health Availabilities API
Luma Health Billing Charges API
Luma Health Billing Copays API
Luma Health Broadcast Templates API
Luma Health Broadcast Events API
Luma Health Broadcast Flows API
Where this information came from

This is an independent, third-party profile of Luma Health Checklists API, 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.