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

Health Gorilla Patient API

Patient demographics and patient-scoped record retrieval.

Health Gorilla Patient API is one of 10 APIs that Health Gorilla publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against 2 base URLs: https://api.healthgorilla.com/fhir/R4, https://sandbox.healthgorilla.com/fhir/R4.

5 operations 3 paths 3 schemas 3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
R4
Base URL
https://api.healthgorilla.com/fhir/R4
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — OAuth 2.0 bearer access token. Obtain a token using the client credentials issued during onboarding via the Health Gorilla OAuth 2.0 token endpoint, then pass…

Paths & Operations 5

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

Patient 5

Patient demographics and patient-scoped record retrieval.

GET
/Patient
Search Patient resources.
searchPatients 5 params → 200
POST
/Patient
Create a Patient resource.
createPatient body → 201
GET
/Patient/{id}
Read a Patient resource by id.
readPatient 1 param → 200404
PUT
/Patient/{id}
Update a Patient resource.
updatePatient 1 param body → 200
GET
/Patient/{id}/$everything
Retrieve all records for a patient.
patientEverything 1 param → 200202

Schemas 3

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

Bundle
object
5 properties
Patient
object
8 properties
OperationOutcome
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

health-gorilla-patient-api-openapi.yml Raw ↑

Other APIs Health Gorilla publishes across the network.

Health Gorilla Binary API
Health Gorilla CapabilityStatement API
Health Gorilla Coverage API
Health Gorilla DiagnosticReport API
Health Gorilla DocumentReference API
Health Gorilla Observation API
Health Gorilla Practitioner API
Health Gorilla RequestGroup API
Health Gorilla ServiceRequest API
Where this information came from

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