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 PDEX Plan Net API

The FHIR-PDEX-Plan-Net-API API from Centene — 16 operation(s) for fhir-pdex-plan-net-api.

Documentation Provider Profile APIs.io OpenAPI GitHub

Centene FHIR PDEX Plan Net API is one of 58 APIs that Centene publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include FHIR-PDEX-Plan-Net-API. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and an API reference.

This API exposes 16 operations across 16 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, 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/.

16 operations 16 paths 28 schemas 16 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2
Base URL
https://iopc-pa.api.centene.com/iopc/pa
Authentication
OAuth 2.0
Contact
Provider_RTR_Support@centene.com
Resource Areas
1

Authentication & Security 1

Centene FHIR PDEX Plan Net 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 16

Across 16 paths, the API surfaces 16 operations — 16 GET. Each is listed below with its method, path, parameters, and response codes.

FHIR-PDEX-Plan-Net-API 16
GET
/Endpoint
Endpoint search
EndpointSearch 8 params → 200403500504
GET
/Endpoint/{_id}
Endpoint by id
EndpointById 1 param → 200403500504
GET
/HealthcareService
Healthcare service search
HealthcareServiceSearch 30 params → 200403500504
GET
/HealthcareService/{_id}
Healthcare service by id
HealthcareServiceById 1 param → 200403500504
GET
/InsurancePlan
Insurance plan search
InsurancePlanSearch 21 params → 200403500504
GET
/InsurancePlan/{_id}
Insurance plan by id
InsurancePlanById 1 param → 200403500504
GET
/Location
Location search
LocationSearch 35 params → 200403500504
GET
/Location/{_id}
Location by id
LocationById 1 param → 200403500504
GET
/Organization
Organization search
OrganizationSearch 23 params → 200403500504
GET
/Organization/{_id}
Organization by id
OrganizationById 1 param → 200403500504
GET
/OrganizationAffiliation
Organization affiliation search
OrganizationAffiliationSearch 24 params → 200403500504
GET
/OrganizationAffiliation/{_id}
Organization affiliation by id
OrganizationAffiliationById 1 param → 200403500504
GET
/Practitioner
Practitioner search
PractitionerSearch 20 params → 200403500504
GET
/Practitioner/{_id}
Practitioner by id
PractitionerById 1 param → 200403500504
GET
/PractitionerRole
Practitioner role search
practitionerRoleSearch 21 params → 200403500504
GET
/PractitionerRole/{_id}
Practitioner role by id
practitionerRoleById 1 param → 200403500504

Schemas 28

The contract defines 28 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.

Attachment
object
8 properties
Address
object
12 properties
Meta
object
5 properties
OrganizationAPIResponse
object
17 properties
NotAvailable
object
2 properties
Contact
object
5 properties
Coding
object
3 properties
Link
object
2 properties
Code
object
4 properties
InsurancePlanAPIResponse
object
19 properties
Text
object
2 properties
Quantity
object
5 properties
Qualifiers
object
2 properties
CodeableConcept
object
2 properties
Telecom
object
7 properties
HumanName
object
7 properties
Period
object
2 properties
LocationAPIResponse
object
22 properties
PractitionerAPIResponse
object
14 properties
apiResponse
object
6 properties
Reference
object
2 properties
Identifier
object
7 properties
PractitionerRoleAPIResponse
object
20 properties
EndpointAPIResponse
object
17 properties
OrganizationAffiliationAPIResponse
object
17 properties
Extension
object
13 properties
AvailableTime
object
4 properties
HealthcareServiceAPIResponse
object
29 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

centene-fhir-pdex-plan-net-api-api-openapi.yml Raw ↑

Other APIs Centene publishes across the network.

Centene Batch Results Ack Submit Transaction API
AE Profile APIs.io
Centene Batch Results Retrieval Transaction API
AE Profile APIs.io
Centene Batch Submit Ack Retrieval Transaction API
AE Profile APIs.io
Centene Batch Submit Transaction API
AE Profile APIs.io
Centene Care Team API
AE Profile APIs.io
Centene Communication API
AE Profile APIs.io
Centene Condition API
AE Profile APIs.io
Centene Coverage API
AE Profile APIs.io
Centene Custom Mapping API
AE Profile APIs.io
Centene Custom Query Validator API
AE Profile APIs.io
Centene Device API
AE Profile APIs.io
Centene Diagnostic Report API
AE Profile APIs.io
#FHIR-PDEX-Plan-Net-API
← Back to C APIs
API Details
ID
centene:centene-fhir-pdex-plan-net-api-api
Base URL
https://iopc-pa.api.centene.com/iopc/pa
Docs
https://partners.centene.com/apiDetail/2718669d-6e2e-42b5-8c90-0a82f13a30ba
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-pdex-plan-net-api-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/centene-fhir-pdex-plan-net-api-api"

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 PDEX Plan Net 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.