The API Report CardAPI Index
CoverMyMeds

CoverMyMeds API

Prior Authorization · covermymeds.com

APIs for pharmacy, provider, and EHR integration exist, built on the NCPDP ePA standard and split into Pharmacy and Provider APIs. Access is gated behind a partnership and integration request process rather than self-serve signup. The public Ruby client on GitHub is unmaintained.

Last verified: July 2026Healthcare
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceFAILNo self-serve public API. Pharmacy and Provider APIs built on the NCPDP ePA standard exist, gated behind partnership approval.
AccessFAILGetting keys means contacting the team and clearing a partnership and integration review; nothing is self-serve.
CoveragePOOR
AuthFAIL
Docs & DXFAILDocumentation sits behind the partnership process; the public Ruby client on GitHub is unmaintained with thin docs.
StabilityMIXED
MORE FROM THE REPORT CARD
Supergood: CoverMyMeds isn't going to ship an API, so we did: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

CoverMyMeds scores F on the API Report Card. APIs for pharmacy, provider, and EHR integration exist, built on the NCPDP ePA standard and split into Pharmacy and Provider APIs. Access is gated behind a partnership and integration request process rather than self-serve signup. The public Ruby client on GitHub is unmaintained.

Tried to integrate with CoverMyMeds?
SOURCES
API access is gated and requires partnership approval, not self-service covermymeds.com
Ruby client library on GitHub appears unmaintained with limited documentation github.com
Physicians complain CMM registration is cumbersome and feels like an unnecessary middleman in the PA process reddit.com
Error-prone PA submissions with vague error messages frustrate users reddit.com
McKesson/CoverMyMeds employee reviews cite culture issues post-acquisition indeed.com