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

Clover Health fhir-r4-formulary-api API

The fhir-r4-formulary-api API from Clover Health — 5 operation(s) for fhir-r4-formulary-api.

Clover Health fhir-r4-formulary-api API is one of 2 APIs that Clover Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include fhir-r4-formulary-api. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

Requests are made against a single base URL, https://public-api.cloverhealth.com.

5 operations 5 paths 44 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://public-api.cloverhealth.com
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

Clover Health fhir-r4-formulary-api API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). An API key is passed in the cookie as sessionid (cookieAuth).

Paths & Operations 5

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

fhir-r4-formulary-api 5
GET
/formulary/api/List
This interaction searches a set of resources based on some filter criteria.
list_formulary 6 params → 200
GET
/formulary/api/List/{id}
The read interaction accesses the current contents of a resource.
list_formulary_item 1 param → 200
GET
/formulary/api/MedicationKnowledge
This interaction searches a set of resources based on some filter criteria.
search_medication_knowledge 7 params → 200
GET
/formulary/api/MedicationKnowledge/{id}
The read interaction accesses the current contents of a resource.
get_medication_knowledge 1 param → 200
GET
/formulary/api/metadata
Get the capability statement of the formulary API
get_formulary_api_metadata → 200

Schemas 44

The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are FormularyMedicationKnowledgeResponse (12 properties), FormularyListResponse (12 properties), FHIRCapabilityStatement (11 properties), FormularyListItemResponse (10 properties). Each schema is shown below with its type and property counts.

FormularyListItemExtensionExtensionValueString
object
2 properties 2 required
FormularyListEntry
object
3 properties 3 required
SearchModeEnum
string
match - match include - include outcome - outcome
FormularyMedicationKnowledgeResponse
object
12 properties 7 required
FormularyListItemEntry
object
1 property 1 required
FormularyMedicationKnowledgeEntry
object
3 properties 3 required
FormularyMedicationKnowledgeItemExtensionValue
FormularyMedicationKnowledgeItemText
object
2 properties 2 required
FHIRCapabilityStatementRestModeEnum
string
client - client server - server
FHIRCapabilityStatementRestResource
object
5 properties 3 required
FormularyListItemExtensionExtensionValueCodeableConcept
object
2 properties 2 required
FormularyListResponse
object
12 properties 7 required
ResponseModeEnum
string
working - working snapshot - snapshot changes - changes
FormularyListItemExtensionExtensionvalueCodeableConceptCoding
object
3 properties 3 required
FormularyListItemResponse
object
10 properties 10 required
FormularyListItemIdentifier
object
2 properties 1 required
FormularyMedicationKnowledgeItemResponse
object
6 properties 6 required
FormularyListItemMeta
object
2 properties 2 required
FormularyListItemExtension
object
2 properties 2 required
FormularyMedicationKnowledgeItemExtensionValueBoolean
object
2 properties 2 required
FormularyMedicationKnowledgeItemMeta
object
2 properties 1 required
FormularyListEntrySearch
object
1 property 1 required
BaseBundleMeta
object
1 property 1 required
FHIRCapabilityStatementInteractionCode
object
1 property 1 required
BaseBundleSignature
object
7 properties 3 required
FHIRCapabilityStatement
object
11 properties 6 required
FHIRCapabilityStatementRest
object
2 properties 2 required
FormularyListItemEntryItem
object
1 property 1 required
FormularyMedicationKnowledgeEntrySearch
object
1 property 1 required
FormularyMedicationKnowledgeItemExtensionvalueCodeableConcept
object
1 property 1 required
FormularyListItemExtensionExtensionvalueCodeableConcept
object
1 property 1 required
KindEnum
string
instance - instance capability - capability requirements - requirements
BaseBundleLink
object
2 properties 2 required
FormularyListItemResponseStatusEnum
string
current - current retired - retired entered-in-error - entered-in-error
FormularyListItemExtensionValue
BaseResourceMeta
object
4 properties 1 required
FHIRCapabilityStatementSoftware
object
3 properties
FormularyMedicationKnowledgeItemExtensionValueString
object
2 properties 2 required
CodeEnum
string
read - read vread - vread update - update patch - patch delete - delete history-instance - history-instance history-type - history-type create - create search-…
PublicationStatusEnum
string
draft - draft active - active retired - retired unknown - unknown
FormularyListItemExtensionExtensionValueBoolean
object
2 properties 2 required
FormularyMedicationKnowledgeItemExtensionValueCodeableConcept
object
2 properties 2 required
FormularyMedicationKnowledgeItemExtensionvalueCodeableConceptCoding
object
3 properties 3 required
TypeF76Enum
string
document - document message - message transaction - transaction transaction - response - transaction - response batch - batch batch - response - batch - respon…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clover-health-fhir-r4-formulary-api-api-openapi.yml Raw ↑

Other APIs Clover Health publishes across the network.

Clover Health FHIR R4 ProviderDirectory API API
Where this information came from

This is an independent, third-party profile of Clover Health fhir-r4-formulary-api 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.