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

H1 Reference Endpoints API

The Reference Endpoints API from H1 — 13 operation(s) for reference endpoints.

H1 Reference Endpoints API is one of 12 APIs that H1 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Reference Endpoints. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 23 operations across 13 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.ribbonhealth.com/v1.

23 operations 13 paths 0 schemas 4 DELETE11 GET4 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.ribbonhealth.com/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

H1 Reference Endpoints API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

Paths & Operations 23

Across 13 paths, the API surfaces 23 operations — 4 DELETE, 11 GET, 4 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Reference Endpoints 23
GET
/custom/insurances
Search Insurances
getInsurances 1 param → 200400
POST
/custom/insurances
Create Insurance
postCustomInsurance body → 201400409
GET
/custom/insurances/{insurance_uuid}
Get Insurance
getCustomInsurance 1 param → 200404
PUT
/custom/insurances/{insurance_uuid}
Edit Insurance Fields
putCustomInsurance 1 param body → 200400404409
DELETE
/custom/insurances/{insurance_uuid}
Delete Insurance
deleteCustomInsurance 1 param → 204404
GET
/custom/specialties
Search Specialties
getSpecialties 1 param → 200403
POST
/custom/specialties
Create Specialty
postCustomSpecialty body → 201400409
GET
/custom/specialties/{specialty_uuid}
Get Specialty
getCustomSpecialty 1 param → 200404
PUT
/custom/specialties/{specialty_uuid}
Edit Specialty Fields
putCustomSpecialty 1 param body → 200400404409
DELETE
/custom/specialties/{specialty_uuid}
Delete Specialty
deleteCustomSpecialty 1 param → 204404
GET
/provider_types
Search Provider Types
getCustomProviderTypes 1 param → 200
POST
/custom/provider_types
Create Provider Type
postCustomProviderType body → 201400409
GET
/custom/provider_types/{provider_type_uuid}
Get Provider Type
getCustomProviderType 1 param → 200404
PUT
/custom/provider_types/{provider_type_uuid}
Edit Provider Type Fields
putCustomProviderType 1 param body → 200400403404409
DELETE
/custom/provider_types/{provider_type_uuid}
Delete Provider Type
deleteCustomProviderType 1 param → 204403404
GET
/location_types
Search Location Types
getCustomLocationTypes 1 param → 200
POST
/custom/location_types
Create Location Type
postCustomLocationType body → 201400409
GET
/custom/location_types/{location_type_uuid}
Get Location Type
getCustomLocationType 1 param → 200404
PUT
/custom/location_types/{location_type_uuid}
Edit Location Type Fields
putCustomLocationType 1 param body → 200400403404409
DELETE
/custom/location_types/{location_type_uuid}
Delete Location Type
deleteCustomLocationType 1 param → 204403404
GET
/procedures
Search Procedures
getProcedures 4 params → 200
GET
/procedures/{procedure_uuid}
Get Procedure
getProcedure 1 param → 200404
GET
/languages
Search Languages
getLanguages 1 param → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

h1-reference-endpoints-api-openapi.yml Raw ↑

Other APIs H1 publishes across the network.

H1 Cost Estimates API
H1 Filters API
H1 Focus Area Endpoints API
H1 Locations API
H1 Networks API
H1 Organizations API
H1 Price Transparency API
H1 Providers API
H1 TI Ns API
H1 Virtual Care Platforms API
H1 Price Transparency v2 API
Where this information came from

This is an independent, third-party profile of H1 Reference Endpoints 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.