Understanding the Provider Directory API: Requirements, deadlines, benefits and trends

Updated February 4, 2026

Keeping provider network information accurate and accessible was a challenge for many payers, leading to inefficiencies, frustrated members, and strained provider relationships. 

The Provider Directory API, part of CMS’s Interoperability and Patient Access Final Rule, was designed to address this by automating updates and making provider details publicly accessible. This API not only ensures compliance but also opens new opportunities to boost membership numbers, streamline operations, and strengthen provider partnerships. 

Let’s dive into what this API entails, exploring its requirements, benefits, and current trends in the industry. 

What is the Provider Directory API?

The Provider Directory API is a publicly accessible, FHIR-based interface that allows impacted payers to share information about their contracted provider networks. CMS expects this information to be accessible to current and prospective enrollees—and the public—without requiring user authentication or authorization.

In plain language: it’s a standards-based directory endpoint that external apps and websites can query so members can find in-network providers more easily, and so provider information stays consistent across channels.

Who does this impact?

CMS requires the Provider Directory API for the payer types impacted by the 2020 Interoperability and Patient Access final rule (CMS‑9115‑F), including:

• Medicare Advantage (MA) organizations
• State Medicaid agencies (including Medicaid fee‑for‑service (FFS) programs)
• Medicaid managed care plans
• State Children’s Health Insurance Program (CHIP) agencies (including CHIP FFS programs)
• CHIP managed care entities

Qualified Health Plan (QHP) issuers on the Federally Facilitated Exchanges (FFEs) are not required to provide provider directory information through an API, because they already have separate requirements to make provider directory information available in a specified machine‑readable format.

What types of data are required?

Impacted payers must create a FHIR API-based Provider Directory that includes data on a payer’s network of contracted providers, including:

• Provider name
• Address
• Phone number
• Specialty

Medicare Advantage (MA) plans with prescription drug coverage (MA-PD) must also provide pharmacy directory data, including:

• Pharmacy name
• Address
• Phone number
• Type of pharmacy
• Number of pharmacies in the network

This API must be publicly accessible on a payer’s website. “Publicly accessible” means end users shouldn’t need to log in to see the directory information, and the API should not use authentication/authorization protocols that restrict availability to specific people or organizations. When a payer receives new provider directory information or an update, the Provider Directory API must reflect that change within 30 calendar days. Operationally, this is where directory programs often break: you need a reliable intake process, validation, and a repeatable publishing pipeline. 

When does this come into effect? 

As part of the Interoperability and Patient Access Final Rule (2020), the Centers for Medicare & Medicaid Services (CMS) mandated that impacted payers implement and maintain a publicly accessible FHIR-based Provider Directory API since July 1, 2021. CMS‑0057‑F (the Interoperability and Prior Authorization Final Rule) builds on that broader interoperability foundation, but the Provider Directory API itself remains a standing requirement for the payer types above.

5 key benefits of the Provider Directory API for payers

1. Improved member acquisition: Prospective members often compare health plans based on their provider networks. A Provider Directory API ensures that your network details are accurate, accessible, and easy to understand, giving your health plan a competitive edge in attracting new members. 
2. Reduced admin burden: With data readily available, the API eliminates manual processes like responding to provider inquiries about network details. This efficiency frees up payer resources and strengthens relationships with providers, who rely on quick access to accurate network information for referrals and care coordination. 
3. Cost savings through automation: Automating directory updates via APIs minimizes manual data entry and reduces the risk of errors, boosting operational efficiency and lowering costs for payers. 
4. Consistency and compliance: Using a standardized FHIR-based approach ensures that data is consistent across platforms, reducing inconsistencies and building trust among stakeholders. The 30-day update requirement guarantees that information remains current and reliable. 
5. Support for value-based care models: Accurate, easily accessible provider information is crucial for supporting value-based care arrangements. The API helps facilitate care coordination, streamline referrals, and reduce gaps in care—important in improving outcomes and controlling costs. 

3 2026 trends and implications for payers

The introduction of the Provider Directory API is bringing some exciting trends for payers, showing how it can redefine how health plans work, connect with members, and team up with providers, such as: 

1. Putting members first: The API supports the shift toward consumer-focused healthcare, making it easier for members to search for and compare providers. This allows payers to keep up with growing expectations for convenience and transparency, especially from younger, tech-savvy individuals.
2. Greater provider network competition: With provider network details now more accessible, members and providers are paying closer attention to the quality and variety of options. This is pushing payers to invest in stronger, more diverse networks to remain competitive. 
3. Push for digital innovation: The API enables third-party developers to create innovative apps using public directory data, helping members better navigate networks and compare options while offering payers a chance to integrate or promote digital solutions that add real value for members. 

Take the next step

The Provider Directory API is more than a compliance requirement—it’s an opportunity for payers to lead in transparency, efficiency, and innovation. By implementing this API, payers can gain new members, strengthen provider relationships, and streamline operations.

At Firely, we specialize in helping payers navigate FHIR implementation and API development. From aligning with CMS regulations to leveraging the Provider Directory API for strategic advantage, we’re here to help.

If you’re ready to take the next step in implementing the Provider Directory API, Firely Server offers the tools and support you need to get started. For more detailed instructions, visit our CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) documentation, or reach out to our team to explore how Firely can support your journey to interoperability.