Back to Platform API Guides
HealthcareLimited official API· workaround available

CoverMyMeds API

CoverMyMeds restricts its prior authorization API to approved EHR partners, leaving standalone PA automation tools and AI prior auth platforms without a direct integration path. Integuru can generate a production-ready HTTP API. Chat with us to get started.

Backed byY CombinatorFree sandbox trial before production

<3 sec

Response latency per call

99.9%+

Reliability rate on generated APIs

24/7

On-call maintenance on production plans

$0

Sandbox trial before production

What CoverMyMeds currently offers publicly

Limited official API

CoverMyMeds (a McKesson company) offers a prior authorization API, but access is limited to approved EHR partners. Development teams building standalone PA automation tools, AI prior authorization platforms, or clinical workflow products that are not part of an approved EHR's integration ecosystem have no sanctioned developer path. The EHR partner approval process is not self-serve, has no published timeline, and requires a formal integration partnership with McKesson rather than with CoverMyMeds directly.

CoverMyMeds official site

How Integuru fills the gap

Integuru generates a production-ready HTTP API for CoverMyMeds beyond what its limited official API covers. It maps the authenticated network requests the CoverMyMeds web app already makes, handles the login flow including 2FA, covers the branching states real accounts hit, and keeps the API running with 24/7 on-call maintenance on production plans.

Planned endpoints

Actions Integuru could expose

Final scope is confirmed when the integration is built
submit_prior_auth

Initiate a prior authorization request for a drug, procedure, or service through the CoverMyMeds network on behalf of a patient and prescriber

get_prior_auth_status

Retrieve the current status of a prior authorization request including payer decision, denial reason, and reference number

list_prior_auths

Return a paginated list of prior authorization requests filtered by patient, prescriber, drug, or authorization status

get_patient_detail

Retrieve patient demographic and coverage information associated with a prior authorization request

check_eligibility

Submit a real-time eligibility inquiry for a patient to determine active coverage and prior authorization requirements

get_eligibility_response

Retrieve the eligibility response for a patient including formulary status and prior authorization trigger flags

submit_clinical_criteria

Submit supporting clinical criteria and documentation required by the payer to adjudicate a prior authorization request

get_determination_status

Retrieve the payer determination on a prior authorization including approval, denial, or request for additional information

list_pending_auths

Return a list of prior authorization requests awaiting payer determination or additional clinical information

get_patient_balance

Retrieve cost estimate and patient responsibility information for a drug or service subject to prior authorization

...many more

These actions reflect what Integuru would generate based on the workflows CoverMyMeds exposes through its web interface.

Need a different CoverMyMeds action?

Tell us the workflows and accounts you need. Requested integrations are delivered to a sandbox you can test free before production.

Process

What happens after you book a call

  1. 1Tell us the CoverMyMeds workflows you need

    Book a call and list the actions, account types and call volume. There is no separate build fee to start.

  2. 2Integuru builds the API in days

    The team maps the authenticated requests CoverMyMeds makes into a direct HTTP API, covering the edge cases you named, and delivers it to a sandbox you test free.

  3. 3Move to production, maintained

    Call documented REST endpoints from your stack, and hand breakage to Integuru: production integrations are maintained around the clock, with auth auto-healing included.

Guide

CoverMyMeds integration guide

Overview

CoverMyMeds is the largest prior authorization network in the United States, processing PA requests across more than 75 payers and connecting prescribers, pharmacies, and health systems to payer adjudication systems. The platform handles prior authorization for both pharmacy and medical benefits, covering drug PA requests that flow through pharmacies and procedure PA requests that originate in clinical settings. CoverMyMeds is a McKesson company, and its network is embedded in a substantial share of the clinical workflows that manage drug access and procedure approval for patients across commercial insurance, Medicare Advantage, and Medicaid plans.

The API access barrier is a formal EHR partner approval process managed through McKesson. The CoverMyMeds API is available to approved EHR partners whose systems already have an established integration relationship with CoverMyMeds. A standalone PA automation tool, an AI prior authorization platform, or a clinical decision support product that is not embedded in an approved EHR's ecosystem has no self-serve path to the API. The approval process requires a formal partnership with McKesson rather than with CoverMyMeds directly, and the timeline is not published. For a healthtech company whose product sits above the EHR layer, this is a structural access gap rather than a technical one.

Integuru generates a production-ready HTTP API for CoverMyMeds using direct HTTP requests against the same endpoints the CoverMyMeds web application uses internally. Prior authorization submission, determination tracking, clinical criteria workflows, and eligibility data are all reachable through Integuru's API without an EHR partner approval gating the build. The Production plan's 24/7 on-call maintenance team handles session management, re-authentication, and endpoint changes before they affect your production calls. Integuru can be deployed in HIPAA-compliant environments; discuss your compliance requirements when you chat with us.


Why Teams Need This Integration

Prior authorization is one of the highest-friction friction points in clinical care. The CoverMyMeds network handles the PA volume that matters, and access to it programmatically is the difference between a PA automation product that covers real workflows and one that requires manual portal entry for the cases it cannot reach.

AI prior authorization platforms. A growing category of healthtech products uses AI to pre-fill PA requests, predict payer approval criteria, and submit authorization requests with supporting clinical criteria. These tools need submit_prior_auth, get_determination_status, and list_pending_auths as live API calls against the CoverMyMeds network rather than robotic portal entry. For an AI PA platform whose customers rely on CoverMyMeds for their payer relationships, programmatic access to the PA workflow is the core product capability.

Pharmacy and specialty pharmacy automation. Specialty pharmacies and pharmacy benefit management tools track drug PA status for high-cost medications across payers. get_prior_auth_status and list_prior_auths give pharmacy automation platforms a live status feed for drug authorizations without requiring pharmacists to log into the CoverMyMeds portal to check each request. check_eligibility and get_eligibility_response surface formulary status and PA trigger flags before a prescription is sent, reducing the cycle time between prescription and dispensing.

Clinical workflow and EHR integration products. Products that sit between EHRs and payer systems to manage PA initiation need submit_clinical_criteria and get_determination_status to handle the back-and-forth of the adjudication process. Payers frequently request additional clinical documentation before rendering a determination, and a PA product that cannot programmatically submit supplemental criteria requires manual intervention at exactly the point in the workflow where automation provides the most value.

RCM and utilization review tools. Health system utilization review teams and revenue cycle management platforms track PA status across large patient populations to prevent claim denials attributable to missing authorizations. list_pending_auths and get_prior_auth_status give these teams a programmatic view of authorization status across providers and payers without requiring staff to check the CoverMyMeds portal patient by patient.


RCM Workflows This Integration Covers

The ten planned actions span the prior authorization lifecycle on the CoverMyMeds network:

  • PA submission and tracking: submit_prior_auth initiates a prior authorization request through CoverMyMeds for a drug or procedure. get_prior_auth_status retrieves the current status including payer decision and reference number. list_prior_auths returns paginated authorization records filtered by patient, prescriber, or status. list_pending_auths surfaces requests awaiting determination or additional information.
  • Clinical criteria and determination: submit_clinical_criteria sends supporting clinical documentation to the payer as part of the adjudication process. get_determination_status retrieves the payer decision including approval, denial, or request for additional information.
  • Eligibility and coverage: check_eligibility submits a real-time eligibility inquiry to surface coverage status and PA trigger flags before a prescription or procedure is initiated. get_eligibility_response returns formulary status and authorization requirements for a patient's active plan.
  • Patient data and financial information: get_patient_detail retrieves patient demographic and coverage information associated with a PA request. get_patient_balance provides cost estimate and patient responsibility data for a drug or service subject to authorization.

Adjacent Integrations

Integuru already covers several of the EHR platforms that CoverMyMeds is embedded within, providing an entry point for the broader clinical data layer that PA automation tools depend on. The athenahealth integration guide covers the MDP partner program barrier for one of the most common EHR platforms connected to CoverMyMeds workflows, with eleven planned actions including clinical notes and insurance policy data. The AdvancedMD integration guide addresses the partner enrollment gap for practices on that platform. The DrChrono integration provides 4 live actions in production including patient creation, patient listing, medication records, and allergy data.

Live in Healthcare

Integuru already supports these platforms in the same vertical

Live, production-ready integrations, not requests

Good to know

Before you book a call

How long does this take?
Most managed-service integration requests are built within a few days, including the workflows and edge cases you ask for.
What if CoverMyMeds changes or breaks?
Every managed integration includes 24/7 on-call maintenance, so your team is never pulled into patching target-platform changes.
What does it cost?
You test the CoverMyMeds integration free in a sandbox before paying anything. Production pricing follows the standard Production plan (starts at $499/month, including 24/7 on-call maintenance), scoped to the platforms, workflows and call volume you need.

FAQ

Frequently asked questions