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 StructureDefinition API

The StructureDefinition FHIR resource type

Documentation Provider Profile APIs.io OpenAPI GitHub

Devoted Health StructureDefinition 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 StructureDefinition. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 26 operations across 16 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.

26 operations 16 paths 2 schemas 1 DELETE12 GET1 PATCH11 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 26

Across 16 paths, the API surfaces 26 operations — 1 DELETE, 12 GET, 1 PATCH, 11 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

StructureDefinition 26

The StructureDefinition FHIR resource type

GET
/StructureDefinition/{id}
read-instance: Read StructureDefinition instance
getStructureDefinitionById 1 param → 200
PUT
/StructureDefinition/{id}
update-instance: Update an existing StructureDefinition instance, or create…
putStructureDefinitionById 1 param body → 200
DELETE
/StructureDefinition/{id}
instance-delete: Perform a logical delete on a resource instance
deleteStructureDefinitionById 1 param → 200
PATCH
/StructureDefinition/{id}
instance-patch: Patch a resource instance of type StructureDefinition by ID
patchStructureDefinitionById 1 param body → 200
GET
/StructureDefinition/{id}/_history/{version_id}
vread-instance: Read StructureDefinition instance with specific version
getStructureDefinitionByIdHistoryByVersionId 2 params → 200
GET
/StructureDefinition
search-type: Search for StructureDefinition instances
getStructureDefinition 36 params → 200
POST
/StructureDefinition
create-type: Create a new StructureDefinition instance
postStructureDefinition body → 200
GET
/StructureDefinition/_history
type-history: Fetch the resource change history for all resources of type…
getStructureDefinitionHistory → 200
GET
/StructureDefinition/{id}/_history
instance-history: Fetch the resource change history for all resources of type…
getStructureDefinitionByIdHistory 1 param → 200
GET
/StructureDefinition/_search
search-type: Search for StructureDefinition instances
getStructureDefinitionSearch 36 params → 200
GET
/StructureDefinition/$validate
Get structure definition $validate
getStructureDefinition$validate 1 param → 200
POST
/StructureDefinition/$validate
Create structure definition $validate
postStructureDefinition$validate body → 200
GET
/StructureDefinition/{id}/$validate
Get structure definition by id $validate
getStructureDefinitionById$validate 2 params → 200
POST
/StructureDefinition/{id}/$validate
Create structure definition by id $validate
postStructureDefinitionById$validate 1 param body → 200
POST
/StructureDefinition/{id}/$meta-delete
Create structure definition by id $meta delete
postStructureDefinitionById$metaDelete 1 param body → 200
POST
/StructureDefinition/{id}/$meta-add
Create structure definition by id $meta add
postStructureDefinitionById$metaAdd 1 param body → 200
GET
/StructureDefinition/$meta
Get structure definition $meta
getStructureDefinition$meta → 200
POST
/StructureDefinition/$meta
Create structure definition $meta
postStructureDefinition$meta body → 200
GET
/StructureDefinition/{id}/$meta
Get structure definition by id $meta
getStructureDefinitionById$meta 1 param → 200
POST
/StructureDefinition/{id}/$meta
Create structure definition by id $meta
postStructureDefinitionById$meta 1 param body → 200
POST
/StructureDefinition/$expunge
Create structure definition $expunge
postStructureDefinition$expunge body → 200
POST
/StructureDefinition/{id}/$expunge
Create structure definition by id $expunge
postStructureDefinitionById$expunge 1 param body → 200
GET
/StructureDefinition/$snapshot
Get structure definition $snapshot
getStructureDefinition$snapshot 1 param → 200
POST
/StructureDefinition/$snapshot
Create structure definition $snapshot
postStructureDefinition$snapshot body → 200
GET
/StructureDefinition/{id}/$snapshot
Get structure definition by id $snapshot
getStructureDefinitionById$snapshot 2 params → 200
POST
/StructureDefinition/{id}/$snapshot
Create structure definition by id $snapshot
postStructureDefinitionById$snapshot 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-structuredefinition-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
#StructureDefinition
← Back to D APIs
API Details
ID
devoted-health:devoted-health-structuredefinition-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-structuredefinition-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/devoted-health-structuredefinition-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 StructureDefinition 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.