The API Report CardAPI Index
PDX Pharmacy

PDX Pharmacy API

Retail pharmacy management · pdxinc.com

A partner-gated API surface exists, but the PDX developer portal is unreachable from the public internet and there is no self-serve onboarding. Production integration runs through NCPDP D.0 claims, SCRIPT e-prescribing, HL7 v2 EHR interfaces, flat files, and PDX Professional Services builds.

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

SCORECARD

ExistenceGOODA partner API surface with generated docs and an interactive console exists, alongside NCPDP and HL7 v2 interfaces.
AccessFAILThe developer portal is unreachable publicly; access is provisioned through PDX Professional Services and partner channels.
CoveragePOORClaims, e-prescribing, and EHR flows run over NCPDP and HL7 v2; chain data leaves via proprietary flat-file exports.
AuthFAILNo public OAuth flow; REST endpoints are unreachable without partner credentials.
Docs & DXFAILAPI docs sit behind the unreachable partner portal; nothing developer-facing is published on pdxinc.com.
StabilityMIXED
Supergood: PDX Pharmacy has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

PDX Pharmacy scores F on the API Report Card. A partner-gated API surface exists, but the PDX developer portal is unreachable from the public internet and there is no self-serve onboarding. Production integration runs through NCPDP D.0 claims, SCRIPT e-prescribing, HL7 v2 EHR interfaces, flat files, and PDX Professional Services builds.

Tried to integrate with PDX Pharmacy?
SOURCES
The PDX developer portal (portal-exploredx-apims01.pdxinc.com) is not publicly reachable, blocking discovery and self-serve onboarding for would-be integration partners portal-exploredx-apims01.pdxinc.com
No public OAuth flow, REST/GraphQL reference, or SDK on pdxinc.com, integration requires going through PDX Professional Services or partner-gated channels pdxinc.com
Industry integration vendors (Starlight API, PilotFish, Redix) exist precisely because NCPDP D.0 and proprietary PMS exports are hard to consume directly from systems like PDX EPS starlightapi.com
Third-party (TP) claim exception handling that requires programmatic access is one of the most-complained-about workflows in EPS, suggesting partner APIs do not cleanly cover the rebill/COB path g2.com
Workflow-automation listings (airSlate, signNow) for 'PDX Enterprise Pharmacy System' market connector-style integrations rather than first-party API workflows, indicating customers default to UI-scraping and RPA when programmatic access is gated airslate.com
HL7 v2 / NCPDP interfaces to PDX historically require per-customer engineering with PDX Professional Services rather than a published interface catalog pdxinc.com
Acquisition churn (Change Healthcare 2020, Optum 2022) and the broader Change Healthcare ransomware incident in 2024 created additional uncertainty around API roadmap, security review timelines, and partner program continuity fiercehealthcare.com
PDX-MS (manufacturer data services) productizes the dispensing event stream as a B2B data feed to pharma, but the underlying API is not exposed to chain customers as a self-serve dispensing-event API pdxinc.com
EPS is reported as 'insanely slow' with massive delays between screens and random unrecoverable errors requiring close, clean install, and restart g2.com
Users describe EPS as 'the system of a thousand clicks', multiple screens required to accomplish simple tasks g2.com
Third-party (TP) exception handling has degraded, workflows that used to take seconds now take minutes g2.com
Rebilling option cannot always be used; when it fails, the workaround is time-consuming and troubleshooting is hard g2.com
Reviewers characterize the underlying architecture as legacy DOS-era technology with a GUI overlay, limiting modernization g2.com
Industry coverage groups PDX with HBS, McKesson Pharmaserv, and Cerner Retail in the wave of legacy pharmacy software vendors under pressure datascanpharmacy.com
Constant patches and updates required; features don't always work as designed, frustrating pharmacy staff g2.com
Capterra reviewers note slow customer support response on production issues at the counter capterra.com
Acquisition churn, PDX moved from independent to Change Healthcare (2020) to Optum/UnitedHealth (2022), has created roadmap uncertainty for chain customers fiercehealthcare.com
Capterra/SoftwareSuggest customers report the UI is dated compared to PioneerRx and PrimeRx and that training new techs is harder than on modern competitors softwaresuggest.com