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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Centene

Centene FHIR Provider Directory API

The Centene FHIR Provider Directory API exposes in-network provider information for Centene members and the public via HL7 FHIR PDEX Provider Directory resources.

Documentation Provider Profile APIs.io OpenAPI GitHub

Centene FHIR Provider Directory API is one of 12 APIs that Centene publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include FHIR, Provider Directory, and CMS Interoperability. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, a getting-started guide, and an API reference.

This API exposes 17 operations across 17 paths, organized into 9 resource areas, and defines 18 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against a single base URL, https://dev-int-api-gw.centene.com/fhir/v4/providerdirectory.

17 operations 17 paths 18 schemas 17 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://iopc-pd.api.centene.com/iopc/pd/fhir/providerdirectory
Authentication
HTTP Basic
Resource Areas
9

Authentication & Security 1

Centene FHIR Provider Directory API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (Basic).

Paths & Operations 17

Across 17 paths, the API surfaces 17 operations — 17 GET. They span 9 resource areas: metadata, InsurancePlan, Endpoint, HealthcareService, OrganizationAffiliation, Organization, PractitionerRole, Practitioner, Location. Each is listed below with its method, path, parameters, and response codes.

metadata 1
GET
/metadata
CapailityStatement
getMetadata → 200
InsurancePlan 2
GET
/InsurancePlan
Search all resources of type InsurancePlan based on a set of criteria
searchInsurancePlan 18 params → 200400401403404500429501
GET
/InsurancePlan/{id}
Read the current state of the resource
readInsurancePlan 1 param → 200400401403404500429501
Endpoint 2
GET
/Endpoint/{id}
Read the current state of the resource
readEndpoint 1 param → 200400401403404500429501
GET
/Endpoint
Search all resources of type Endpoint based on a set of criteria
searchEndpoint 4 params → 200400401403404500429501
HealthcareService 2
GET
/HealthcareService
Search all resources of type HealthcareService based on a set of criteria
searchHealthcareService 20 params → 200400401403404500429501
GET
/HealthcareService/{id}
Read the current state of the resource
readHealthcareService 1 param → 200400401403404500429501
OrganizationAffiliation 2
GET
/OrganizationAffiliation
Search all resources of type OrganizationAffiliation based on a set of criteria
searchOrganizationAffiliation 14 params → 200400401403404500429501
GET
/OrganizationAffiliation/{id}
Read the current state of the resource
readOrganizationAffiliation 1 param → 200400401403404500429501
Organization 2
GET
/Organization
Search all resources of type Organization based on a set of criteria
searchOrganization 18 params → 200400401403404500429501
GET
/Organization/{id}
Read the current state of the resource
readOrganization 1 param → 200400401403404500429501
PractitionerRole 2
GET
/PractitionerRole
Search all resources of type PractitionerRole based on a set of criteria
searchPractitionerRole 14 params → 200400401403404500429501
GET
/PractitionerRole/{id}
Read the current state of the resource
readPractitionerRole 1 param → 200400401403404500429501
Practitioner 2
GET
/Practitioner
Search all resources of type Practitioner based on a set of criteria
searchPractitioner 15 params → 200400401403404500429501
GET
/Practitioner/{id}
Read the current state of the resource
readPractitioner 1 param → 200400401403404500429501
Location 2
GET
/Location
Search all resources of type Location based on a set of criteria
searchLocation 24 params → 200400401403404500429501
GET
/Location/{id}
Read the current state of the resource
readLocation 1 param → 200400401403404500429501

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are Location (14 properties), InsurancePlan (13 properties), OrganizationAffiliation (12 properties), PractitionerRole (12 properties). Each schema is shown below with its type and property counts.

GeneralError
object
2 properties 2 required
OperationOutcome
object
InsurancePlan
object
13 properties 13 required
InsurancePlan-search
object
7 properties 7 required
HealthcareService
object
11 properties 11 required
HealthcareService-search
object
7 properties 7 required
OrganizationAffiliation
object
12 properties 12 required
OrganizationAffiliation-search
object
7 properties 7 required
Organization
object
11 properties 11 required
Organization-search
object
7 properties 7 required
PractitionerRole
object
12 properties 12 required
PractitionerRole-search
object
7 properties 7 required
Practitioner
object
11 properties 11 required
Practitioner-search
object
7 properties 7 required
Location
object
14 properties 14 required
Location-search
object
7 properties 7 required
Endpoint
object
11 properties 11 required
Endpoint-search
object
7 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

centene-fhir-provider-directory-openapi.json Raw ↑

Other APIs Centene publishes across the network.

Centene FHIR Patient Access API
AE Profile APIs.io
Centene Provider RTR - FHIR PDEX Directory API
AE Profile APIs.io
Centene Provider RTR Demographics API
AE Profile APIs.io
Centene Provider Carrier Entity Search (PCES) API
AE Profile APIs.io
Centene Provider Carrier Entity Search (PCES) Extract API
AE Profile APIs.io
Centene Provider Search Suggest API
AE Profile APIs.io
Centene Product Mapping V2 API
AE Profile APIs.io
Centene LWC EDI CORE Real Time Service
AE Profile APIs.io
Centene CCM Communication API
AE Profile APIs.io
Centene CCM SMS User Response Webhook
AE Profile APIs.io
Centene Healow Health API
AE Profile APIs.io
#FHIR#Provider Directory#CMS Interoperability
← Back to C APIs
API Details
ID
centene:centene-fhir-provider-directory
Base URL
https://iopc-pd.api.centene.com/iopc/pd/fhir/providerdirectory
Docs
https://partners.centene.com/apiDetail/8122bc9c-43d6-4a2a-b6be-2272df8b8566
Provider
Centene
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=centene-fhir-provider-directory&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/centene-fhir-provider-directory"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Centene FHIR Provider Directory 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.