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 Provider Carrier Entity Search (PCES) API

A search-index query API over Centene carrier entities, shaped like Elasticsearch — aggregations, buckets, bounding boxes and geo coordinates across 85 schemas. Carries query and custom-query validator operations that lint a query shape before execution. OAuth client credentials with audience ewsext.

Documentation Provider Profile APIs.io OpenAPI GitHub

Centene Provider Carrier Entity Search (PCES) API is one of 12 APIs that Centene publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Provider Search, Search, and Provider. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 4 operations across 4 paths, organized into 4 resource areas, and defines 85 schemas. It is described by OpenAPI 3.1.0, at version 0.0.6.

Requests are made against 6 base URLs: https://dev-int-api-gw.centene.com/pces, https://prod.api.centene.com/incoming/dev/pces, https://test-int-api-gw.centene.com/pces, https://prod.api.centene.com/incoming/test/pces, https://api-gateway-01.centene.com/pces, https://prod.api.centene.com/incoming/pces.

4 operations 4 paths 85 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.0.6
Base URL
https://external-api.search.my.centene.com/pces
Authentication
API Key
Contact
provider_search_support@centene.com
Resource Areas
4

Authentication & Security 1

Centene Provider Carrier Entity Search (PCES) API declares 1 security scheme for authenticating requests. An API key is passed in the header as api_key (api_key).

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. They span 4 resource areas: query, custom-mapping, custom-query-validator, query-validator. Each is listed below with its method, path, parameters, and response codes.

query 1

query elasticsearch

POST
/query
Send a query to Elasticsearch
query 1 param body → 200400500
custom-mapping 1

check local mapping

GET
/custom-mapping
local mapping file for PCES validations
custom-mapping → 200400500
custom-query-validator 1
POST
/custom-query-validator
providerCarrierEntitySearchCustomQueryValidator
providerCarrierEntitySearchCustomQueryValidatorUsingPOST body → 200201401403404
query-validator 1
POST
/query-validator
providerCarrierEntitySearchQueryValidator
providerCarrierEntitySearchQueryValidatorUsingPOST body → 200201401403404

Schemas 85

The contract defines 85 schemas that model the data the API accepts and returns. The most detailed are Affiliation (53 properties), CarrierEntity (39 properties), Location (25 properties), Specialty (19 properties). Each schema is shown below with its type and property counts.

customQuery
object
The Custom Query object is where a user can define the query they want to run on the data. There are "building block" queries outlined in the DSL to allow a us…
1 property
aggs
object
The Aggregations object is where a user can request aggregate data about the query results. For example, a user could ask for an aggregation on locations.addre…
3 properties 2 required
aggType
object
The aggType object contains the actual type of aggregation which will be like valuesAgg or filter or nested.
ValuesAggregation
object
Value Aggregations are used to get aggregate values about the results of a query. And example would be the top 500 unique specialties.
1 property
MinAggregation
object
A single-value metrics aggregation that keeps track and returns the minimum value among numeric values extracted from the aggregated documents.
1 property
MaxAggregation
object
A single-value metrics aggregation that keeps track and returns the minimum value among numeric values extracted from the aggregated documents.
1 property
FilterAggregation
object
Filter Aggregations are used to insert custom query syntax at an aggregation level to limit the scope of the matching documents for that aggregation and any pi…
1 property
Condition
object
exclude
object
1 property
exists
object
1 property
geoFilter
object
1 property
BoundingBox
object
Provide coordinates as comma separated strings ("lat, lon") for point of the box, and point.
1 property
matchedList
object
Used to return and/or filter down which locations match in the locations array.
5 properties 1 required
nameMatch
object
1 property
alphaFilter
object
1 property
prefix
object
1 property
NestedAggregation
object
Nested Aggregations are used to get aggregate values about the nested path.
1 property
nested
object
Specifies a list where you can declare a nested path that corresponds to a list of documents on the main provider document (ie, locations is a list of location…
1 property
Radius
object
For filtering by a certain radial distance, eg. 100 miles. Simply provide as a comma separated string, lat, lon and for your specified range. Be sure to includ…
1 property
range
object
Can accept a single logical operator (lt, lte, gt, gte), but at most one upper and one lower.
1 property
relevancyByDistance
object
Documents will be sorted based on distance from the specified field, according to the custom parameters set.
1 property
requireAll
object
A document must match all criteria in a requireAll to show up in results.
1 property
requireAny
object
Any criteria in a requireAny Query can be true for a document in order for that document to be returned. A minimum of one of the criteria must be true.
1 property
Shape
object
Provide an array of latitude, longitude points for your shape.
1 property
value
object
Used to apply logic that restricts a provided field in the document to an exact value. The Value query should only be used against fields that have an exact va…
1 property
values
object
Used to apply logic that restricts a provided field in the document to an array of exact values. The Values query should only be used against fields that have…
1 property
constantScore
object
Used to apply logic that Wraps a filter query and returns every matching document with a relevance score equal to the boost parameter value
1 property
Accreditation
object
7 properties
AdditionalAddress
object
16 properties
Address
object
18 properties
Affiliation
object
53 properties
AggResponse
object
6 properties
Aggregation
object
3 properties
AggregationType
object
2 properties
AggregationValues
object
2 properties
AreaNetworkService
object
7 properties
AvailabilityCondition
BadgeCertification
object
3 properties
Bucket
object
3 properties
CarrierEntity
object
39 properties
CarrierEntityResults
object
4 properties
CarrierEntityRequest
object
6 properties
CaveatMessage
object
3 properties
Day
object
4 properties
Disorder
object
3 properties
EligibleForDisplay
object
7 properties
GeoCoords
object
2 properties
HomeCommunityBasedService
object
9 properties
HospitalAffiliation
object
5 properties
License
object
6 properties
Location
object
25 properties
MatchedListsCondition
object
2 properties
Meta
object
3 properties
MedicaidNumber
object
4 properties
MedicareNumber
object
1 property
Modality
object
3 properties
Name
object
5 properties
NationalProviderIdentifiers
object
5 properties
Network
object
8 properties
NetworkCycle
object
5 properties
NetworkField
object
3 properties
NetworkLocationCycle
object
9 properties
PracPhone
object
5 properties
OfficeHours
object
7 properties
PhoneNumber
object
3 properties
PanelCycle
object
11 properties
Phone
object
3 properties
Population
object
3 properties
ProvPhones
object
3 properties
PublicTransportation
object
3 properties
RelevancyByDistanceCondition
object
6 properties
RelevancyCondition
object
RelevancyDistanceCondition
object
7 properties
Responses
object
5 properties
Result
object
1 property
ServiceType
object
3 properties
Specialty
object
19 properties
Training
object
8 properties
UDA
object
2 properties
UDAField
object
4 properties
AssociatedProvAttribute
object
2 properties
UDAS
object
3 properties
UDASField
object
5 properties
ParticipatingPhysicianGroupIdentifiers
object
5 properties
Query
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

centene-pces-openapi.yaml Raw ↑

Other APIs Centene publishes across the network.

Centene FHIR Patient Access API
AE Profile APIs.io
Centene FHIR Provider Directory 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) 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
#Provider Search#Search#Provider
← Back to C APIs
API Details
ID
centene:centene-pces
Base URL
https://external-api.search.my.centene.com/pces
Docs
https://partners.centene.com/apiDetail/a3cbbe9e-c2fe-4460-a248-6599e8b746be
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-pces&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/centene-pces"

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 Provider Carrier Entity Search (PCES) 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.