Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zus Health FHIR API

General FHIR R4 resources.

Zus Health FHIR API is one of 5 APIs that Zus Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 5 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 2 base URLs: https://api.zusapi.com, https://api.sandbox.zusapi.com.

5 operations 3 paths 2 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.zusapi.com/fhir
Authentication
HTTP Bearer
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — OAuth2 Bearer access token obtained from the Zus token endpoint (auth.zusapi.com/oauth/token). Sent as Authorization: Bearer .

Paths & Operations 5

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

FHIR 5

General FHIR R4 resources.

GET
/fhir/{resourceType}
Search resources of a given FHIR R4 type.
searchResources 3 params → 200
POST
/fhir/{resourceType}
Create a resource of a given FHIR R4 type.
createResource 1 param body → 201
GET
/fhir/{resourceType}/{id}
Read a resource by type and id.
readResource 2 params → 200404
DELETE
/fhir/{resourceType}/{id}
Delete a resource by type and id.
deleteResource 2 params → 200
POST
/fhir
Submit a FHIR transaction or batch Bundle.
submitBundle body → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Bundle (4 properties), Resource (2 properties). Each schema is shown below with its type and property counts.

Resource
object
A generic FHIR R4 resource.
2 properties
Bundle
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zus-fhir-api-openapi.yml Raw ↑

Other APIs Zus Health publishes across the network.

Zus Health Auth API
Zus Health Documents API
Zus Health Patient API
Zus Health Patient History API