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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Luma Health

Luma Health Specialties API

A Doctor's specialty

Documentation Provider Profile APIs.io OpenAPI GitHub

Luma Health Specialties 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 specialties. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 14 operations across 8 paths, and defines 21 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.

14 operations 8 paths 21 schemas 4 DELETE5 GET4 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 Specialties API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

Paths & Operations 14

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

specialties 14

A Doctor's specialty

GET
/specialties
List specialties
specialtiesList 16 params → 200401403
POST
/specialties
Create specialty
specialtyCreate body → 201401403default
GET
/specialties/{specialtyId}
Get a specialty by id
specialtyGet 1 param → 200401403
PUT
/specialties/{specialtyId}
Update a specialty
specialtyUpdate 1 param body → 200401403
DELETE
/specialties/{specialtyId}
Delete a specialty
specialtyDelete 1 param → 200401403
GET
/specialties/{specialtyId}/appointmentTypes
List appointment types associated with a specialty
specialtyAppointmentTypesList 2 params → 200401403
GET
/specialties/{specialtyId}/facilities
List facilities associated with a specialty
specialtyFacilitiesList 2 params → 200401403
GET
/specialties/{specialtyId}/providers
List providers associated with a specialty
specialtyProvidersList 2 params → 200401403
POST
/specialties/{specialtyId}/appointmentTypes/{appointmentTypeId}
Associate an appointment type to a specialty
specialtyAddAppointmentType 2 params → 200401403
DELETE
/specialties/{specialtyId}/appointmentTypes/{appointmentTypeId}
Remove the association between an appointment type and a specialty
specialtyDeleteAppointmentType 2 params → 200401403
POST
/specialties/{specialtyId}/facilities/{facilityId}
Associate a facility to a specialty
specialtyAddFacility 2 params → 200401403
DELETE
/specialties/{specialtyId}/facilities/{facilityId}
Remove the association between a facility and a specialty
specialtyDeleteFacility 2 params → 200401403
POST
/specialties/{specialtyId}/providers/{providerId}
Associate a provider to a specialty
specialtyAddProvider 2 params → 200401403
DELETE
/specialties/{specialtyId}/providers/{providerId}
Remove the association between a provider and a specialty
specialtyDeleteProvider 2 params → 200401403

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are ProviderResponse (67 properties), SettingProperty (27 properties), FacilityResponse (25 properties), SalesforceData (20 properties). Each schema is shown below with its type and property counts.

userParam
string
The ID of the root account user.
SpecialtyRequestCreate
object
15 properties 1 required
SpecialtyResourceResponse
object
Represents an association between a specialty and a specific resource such as an appointment type, provider, or facility. It is used to determine which provide…
12 properties
Error
object
2 properties 2 required
AppointmentTypeResponse
object
An Appointment Type defines a category of visit that a provider or facility offers, such as a routine office visit or a telehealth consult, along with its defa…
14 properties
idParam
string
Luma's internal ID of an object.
deletedAtParam
string
The date/time when this object was deleted.
SpecialtyResponse
object
Represents a medical specialty, such as cardiology or dermatology, used to categorize providers, facilities, and appointment types within an account. It stores…
15 properties
RolesByUser
object
Object containing 2 keys, referringProvider and renderingProvider. The value for each key is an array. The content of the array should be the root account ids…
2 properties
createdAtParam
string
The date/time when this object was created.
updatedByParam
string
The ID of the user who updated this object.
updatedAtParam
string
The date/time when this object was updated.
SalesforceData
object
Salesforce internal meta data for this account.
20 properties 1 required
ExternalId
object
2 properties
SpecialtyRequestUpdate
object
15 properties
deletedParam
number
Flag for logical deletion where 1 means deleted.
FacilityResponse
object
Represents a physical facility or location belonging to a healthcare organization, including its name, alternative and phonetic names, address, phone, alternat…
25 properties
ProviderResponse
object
A Provider represents a doctor, clinician, or other care team member (including referring or rendering providers) within a Luma Health customer's practice. It…
67 properties 2 required
createdByParam
string
The ID of the user who created this object.
SettingProperty
object
27 properties
deletedByParam
string
The ID of the user who deleted this object.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Luma Health publishes across the network.

Luma Health Appointments API
AE Profile APIs.io
Luma Health Appointment Types API
AE Profile APIs.io
Luma Health Assistant Actions API
AE Profile APIs.io
Luma Health Assistant Instances API
AE Profile APIs.io
Luma Health Assistant Transfer Rules API
AE Profile APIs.io
Luma Health Auth API
AE Profile APIs.io
Luma Health Availabilities API
AE Profile APIs.io
Luma Health Billing Charges API
AE Profile APIs.io
Luma Health Billing Copays API
AE Profile APIs.io
Luma Health Broadcast Templates API
AE Profile APIs.io
Luma Health Broadcast Events API
AE Profile APIs.io
Luma Health Broadcast Flows API
AE Profile APIs.io
#specialties
← Back to L APIs
API Details
ID
luma-health:luma-health-specialties-api
Base URL
https://api.lumahealth.io/api/v2
Docs
https://apidocs.lumahealth.io/#tag/appointments
Provider
Luma Health
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=luma-health-specialties-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/luma-health-specialties-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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