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

Centene Provider RTR - FHIR PDEX Directory API

The Provider RTR FHIR Payer Data Exchange (PDEX) Directory API delivers provider directory data between payers and authorized external partners using HL7 FHIR PDEX profiles.

Centene Provider RTR - FHIR PDEX 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, PDEX, and Payer Data Exchange. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 18 operations across 18 paths, organized into 2 resource areas, and defines 33 schemas. It is described by OpenAPI 3.0.3, at version 1.2.

Requests are made against 2 base URLs: https://prod.api.centene.com/tst/prtc/external/fhir-pdex-plan-net/v1/, https://prod.api.centene.com/prtc/external/fhir-pdex-plan-net/v1/.

18 operations 18 paths 33 schemas 18 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.2
Base URL
https://prod.api.centene.com/prtc/external/fhir-pdex-plan-net/v1/
Authentication
OAuth 2.0
Resource Areas
2

Authentication & Security 1

Centene Provider RTR - FHIR PDEX Directory API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

Paths & Operations 18

Across 18 paths, the API surfaces 18 operations — 18 GET. They span 2 resource areas: FHIR-PDEX-Plan-Net-API, Utilities. Each is listed below with its method, path, parameters, and response codes.

FHIR-PDEX-Plan-Net-API 16
GET
/Endpoint
EndpointSearch 8 params → 200403500504
GET
/Endpoint/{_id}
EndpointById 1 param → 200403500504
GET
/HealthcareService
For further information about parameters please visit https://hl7.org/fhir/R4/healthcareservice.htmlsearch
HealthcareServiceSearch 30 params → 200403500504
GET
/HealthcareService/{_id}
For further information about parameters please visit https://hl7.org/fhir/R4/healthcareservice.htmlsearch
HealthcareServiceById 1 param → 200403500504
GET
/InsurancePlan
InsurancePlanSearch 21 params → 200403500504
GET
/InsurancePlan/{_id}
InsurancePlanById 1 param → 200403500504
GET
/Location
LocationSearch 35 params → 200403500504
GET
/Location/{_id}
LocationById 1 param → 200403500504
GET
/Organization
OrganizationSearch 23 params → 200403500504
GET
/Organization/{_id}
OrganizationById 1 param → 200403500504
GET
/OrganizationAffiliation
OrganizationAffiliationSearch 24 params → 200403500504
GET
/OrganizationAffiliation/{_id}
OrganizationAffiliationById 1 param → 200403500504
GET
/Practitioner
PractitionerSearch 20 params → 200403500504
GET
/Practitioner/{_id}
PractitionerById 1 param → 200403500504
GET
/PractitionerRole
practitionerRoleSearch 21 params → 200403500504
GET
/PractitionerRole/{_id}
practitionerRoleById 1 param → 200403500504
Utilities 2
GET
/health
Health Check
Health → 200403424500504
GET
/version
Version Information
Version → 200403500504

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are HealthcareServiceAPIResponse (29 properties), LocationAPIResponse (22 properties), PractitionerRoleAPIResponse (20 properties), InsurancePlanAPIResponse (19 properties). Each schema is shown below with its type and property counts.

APIErrorResponse
object
4 properties
Address
object
12 properties
Attachment
object
8 properties
AvailableTime
object
4 properties
Code
object
4 properties
CodeableConcept
object
2 properties
Coding
object
3 properties
Contact
object
5 properties
EndpointAPIResponse
object
17 properties
Extension
object
13 properties
HealthcareServiceAPIResponse
object
29 properties
HumanName
object
7 properties
Identifier
object
7 properties
InsurancePlanAPIResponse
object
19 properties
Link
object
2 properties
LocationAPIResponse
object
22 properties
Meta
object
5 properties
Metadata
object
3 properties
NotAvailable
object
2 properties
OrganizationAPIResponse
object
17 properties
OrganizationAffiliationAPIResponse
object
17 properties
Period
object
2 properties
PractitionerAPIResponse
object
14 properties
PractitionerRoleAPIResponse
object
20 properties
Qualifiers
object
2 properties
Quantity
object
5 properties
Reference
object
2 properties
Response
object
2 properties
Telecom
object
7 properties
Text
object
2 properties
apiResponse
object
6 properties
healthResponse
object
Health response containing the status of the mongo database
4 properties
versionResponse
object
Version response containing build information of the current api
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

centene-provider-rtr-fhir-pdex-openapi.json Raw ↑

Other APIs Centene publishes across the network.

Centene FHIR Patient Access API
Centene FHIR Provider Directory API
Centene Provider RTR Demographics API
Centene Provider Carrier Entity Search (PCES) API
Centene Provider Carrier Entity Search (PCES) Extract API
Centene Provider Search Suggest API
Centene Product Mapping V2 API
Centene LWC EDI CORE Real Time Service
Centene CCM Communication API
Centene CCM SMS User Response Webhook
Centene Healow Health API
Where this information came from

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