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
Devoted Health

Devoted Health Healthcare Service API

The HealthcareService FHIR resource type

Documentation Provider Profile APIs.io OpenAPI GitHub

Devoted Health Healthcare Service API is one of 23 APIs that Devoted Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include HealthcareService. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 22 operations across 14 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 6.6.0.

Requests are made against a single base URL, https://fhir.devoted.com/fhir.

22 operations 14 paths 2 schemas 1 DELETE10 GET1 PATCH9 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
6.6.0
Base URL
https://api.prod.devoted.com/fhir
Resource Areas
1

Paths & Operations 22

Across 14 paths, the API surfaces 22 operations — 1 DELETE, 10 GET, 1 PATCH, 9 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Healthcare Service 22

The HealthcareService FHIR resource type

GET
/HealthcareService/{id}
read-instance: Read HealthcareService instance
getHealthcareServiceById 1 param → 200
PUT
/HealthcareService/{id}
update-instance: Update an existing HealthcareService instance, or create using…
putHealthcareServiceById 1 param body → 200
DELETE
/HealthcareService/{id}
instance-delete: Perform a logical delete on a resource instance
deleteHealthcareServiceById 1 param → 200
PATCH
/HealthcareService/{id}
instance-patch: Patch a resource instance of type HealthcareService by ID
patchHealthcareServiceById 1 param body → 200
GET
/HealthcareService/{id}/_history/{version_id}
vread-instance: Read HealthcareService instance with specific version
getHealthcareServiceByIdHistoryByVersionId 2 params → 200
GET
/HealthcareService
search-type: Search for HealthcareService instances
getHealthcareService 22 params → 200
POST
/HealthcareService
create-type: Create a new HealthcareService instance
postHealthcareService body → 200
GET
/HealthcareService/_history
type-history: Fetch the resource change history for all resources of type…
getHealthcareServiceHistory → 200
GET
/HealthcareService/{id}/_history
instance-history: Fetch the resource change history for all resources of type…
getHealthcareServiceByIdHistory 1 param → 200
GET
/HealthcareService/_search
search-type: Search for HealthcareService instances
getHealthcareServiceSearch 22 params → 200
GET
/HealthcareService/$validate
Get healthcare service $validate
getHealthcareService$validate 1 param → 200
POST
/HealthcareService/$validate
Create healthcare service $validate
postHealthcareService$validate body → 200
GET
/HealthcareService/{id}/$validate
Get healthcare service by id $validate
getHealthcareServiceById$validate 2 params → 200
POST
/HealthcareService/{id}/$validate
Create healthcare service by id $validate
postHealthcareServiceById$validate 1 param body → 200
POST
/HealthcareService/{id}/$meta-delete
Create healthcare service by id $meta delete
postHealthcareServiceById$metaDelete 1 param body → 200
POST
/HealthcareService/{id}/$meta-add
Create healthcare service by id $meta add
postHealthcareServiceById$metaAdd 1 param body → 200
GET
/HealthcareService/$meta
Get healthcare service $meta
getHealthcareService$meta → 200
POST
/HealthcareService/$meta
Create healthcare service $meta
postHealthcareService$meta body → 200
GET
/HealthcareService/{id}/$meta
Get healthcare service by id $meta
getHealthcareServiceById$meta 1 param → 200
POST
/HealthcareService/{id}/$meta
Create healthcare service by id $meta
postHealthcareServiceById$meta 1 param body → 200
POST
/HealthcareService/$expunge
Create healthcare service $expunge
postHealthcareService$expunge body → 200
POST
/HealthcareService/{id}/$expunge
Create healthcare service by id $expunge
postHealthcareServiceById$expunge 1 param body → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

FHIR-XML-RESOURCE
object
A FHIR resource
FHIR-JSON-RESOURCE
object
A FHIR resource

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

devoted-health-healthcare-service-api-openapi.yml Raw ↑

Other APIs Devoted Health publishes across the network.

Devoted Health CodeSystem API
AE Profile APIs.io
Devoted Health Condition API
AE Profile APIs.io
Devoted Health Encounter API
AE Profile APIs.io
Devoted Health ExplanationOfBenefit API
AE Profile APIs.io
Devoted Health List API
AE Profile APIs.io
Devoted Health Location API
AE Profile APIs.io
Devoted Health Medication API
AE Profile APIs.io
Devoted Health MedicationKnowledge API
AE Profile APIs.io
Devoted Health OperationDefinition API
AE Profile APIs.io
Devoted Health Organization API
AE Profile APIs.io
Devoted Health OrganizationAffiliation API
AE Profile APIs.io
Devoted Health Patient API
AE Profile APIs.io
#HealthcareService
← Back to D APIs
API Details
ID
devoted-health:devoted-health-healthcare-service-api
Base URL
https://api.prod.devoted.com/fhir
Docs
https://www.devoted.com/developers/
Provider
Devoted 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=devoted-health-healthcare-service-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/devoted-health-healthcare-service-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 Devoted Health Healthcare Service 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.