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

Verifiable Facilities API

Endpoints related to managing and retrieving Facility data. These APIs allow you to create, update, and retrieve facilities and their associated metadata. Each facility record includes key identifiers such as address, group tax ID, contact information, Medicaid number, and Medicare number. This data can be used for lookups, verification, and detecting inconsistencies in facility records or affiliations. In addition to core facility management, these endpoints support retrieving reference data related to facilities, such as license types, accreditations, Medicare enrollment types, and taxonomies.

Verifiable Facilities API is one of 33 APIs that Verifiable publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 8 operations across 6 paths, and defines 13 schemas. It is described by OpenAPI 3.0.1, at version 26.12.1.962.

Requests are made against 2 base URLs: https://discovery.verifiable.com/api, https://discovery-staging.verifiable.com/api.

8 operations 6 paths 13 schemas 6 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
26.12.1.962
Base URL
https://discovery.verifiable.com/api
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Verifiable Facilities API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (custom) (Bearer).

  • Bearer — Enter your bearer token in the format: Bearer {your token}

Paths & Operations 8

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

Facilities 8

Endpoints related to managing and retrieving Facility data. These APIs allow you to create, update, and retrieve facilities and their associated metadata. Each facility record inc…

POST
/facilities
Create a new facility
CreateFacility body → 201400401403500
GET
/facilities
List facilities
ListFacilities 9 params → 200400401403404500
GET
/facilities/{facilityId}
Get an existing facility
GetFacility 1 param → 200400401403404500
PATCH
/facilities/{facilityId}
Patch an existing facility
PatchFacility 1 param body → 200400401403404500
GET
/facilities/license-types
List facility license types
ListFacilityLicenseTypes 7 params → 200400401403500
GET
/facilities/accreditations
List facility accreditations
ListFacilityAccreditations 7 params → 200400401403500
GET
/facilities/medicare-enrollment-types
List facility medicare enrollment types
ListFacilityMedicareEnrollmentTypes 7 params → 200400401403500
GET
/facilities/taxonomies
List facility taxonomies
ListFacilityTaxonomies 8 params → 200400401403500

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are FacilityModel (20 properties), FacilityPatchModel (18 properties), FacilityRequestModel (17 properties), FacilityPageModel (10 properties). Each schema is shown below with its type and property counts.

FacilityLicenseTypeModel
object
2 properties
MedicareEnrollmentTypeModel
object
3 properties
FacilityTaxonomyModel
object
3 properties
FacilityRequestModel
object
17 properties 5 required
FacilityPageModel
object
10 properties
MedicareEnrollmentTypePageModel
object
10 properties
FacilityAccreditationAgencyPageModel
object
10 properties
FacilityAccreditationAgencyModel
object
3 properties
FacilityPatchModel
object
18 properties
FacilityModel
object
20 properties
FacilityTaxonomyPageModel
object
10 properties
FacilityLicenseTypePageModel
object
10 properties
FacilityAccreditationProgramModel
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

verifiable-facilities-api-openapi.yml Raw ↑

Other APIs Verifiable publishes across the network.

Verifiable Alerts API
Verifiable Audit API
Verifiable Authentication API
Verifiable BoardCertifications API
Verifiable CognitoFormsWebhook API
Verifiable CreateOAuthCredentialsClientSecret API
Verifiable CredentialingRequests API
Verifiable Datasets API
Verifiable DEA API
Verifiable Definitions API
Verifiable DeleteOAuthCredentialsClientSecret API
Verifiable FacilitiesInfo API
Where this information came from

This is an independent, third-party profile of Verifiable Facilities 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.