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

DentaQuest FHIR Provider Directory API

FHIR R4 (4.0.1) Provider Directory API from DentaQuest, the Sun Life U.S. dental company, conforming to the HL7 Da Vinci PDex Plan-Net Implementation Guide 1.1.0 and published under CMS-9115-F. Exposes read and search over Practitioner, PractitionerRole, Organization, Location, HealthcareService, InsurancePlan and Endpoint, each with _history and version reads, so third-party applications can find in-network dentists and dental plans. Authenticated with an Azure API Management subscription key sent in the Ocp-Apim-Subscription-Key header or the subscription-key query parameter. Errors return a FHIR OperationOutcome. The same API is served for the Delta Dental of Massachusetts brand.

This API exposes 36 operations across 36 paths, and defines 1 schema. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 2 base URLs: https://api.dentaquest.com/FhirProviderDirectory, https://api.deltadentalma.com/FhirProviderDirectory.

36 operations 36 paths 1 schemas 36 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.dentaquest.com/FhirProviderDirectory
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

DentaQuest FHIR Provider Directory API declares 2 security schemes for authenticating requests. An API key is passed in the header as Ocp-Apim-Subscription-Key (apiKeyHeader). An API key is passed in the query as subscription-key (apiKeyQuery). By default, every request must be authenticated.

Paths & Operations 36

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

Operations 36
GET
/metadata
Get conformance statement.
get-metadata → 200
GET
/Endpoint
/Endpoint - GET
get-endpoint 13 params → 200
GET
/Endpoint/{id}
/Endpoint/{id} - GET
get-endpoint-id 1 param → 200
GET
/Endpoint/{id}/_history/{vid}
/Endpoint/{id}/history/{vid} - GET
get-endpoint-id-_history-vid 2 params → 200
GET
/Endpoint/{id}/_history
/Endpoint/{id}/history - GET
get-endpoint-id-_history 3 params → 200
GET
/Endpoint/_history
/Endpoint/history - GET
get-endpoint-_history 2 params → 200
GET
/HealthcareService
/HealthcareService - GET
get-healthcareservice 19 params → 200
GET
/HealthcareService/{id}
/HealthcareService/{id} - GET
get-healthcareservice-id 1 param → 200
GET
/HealthcareService/{id}/_history/{vid}
/HealthcareService/{id}/history/{vid} - GET
get-healthcareservice-id-_history-vid 2 params → 200
GET
/HealthcareService/{id}/_history
/HealthcareService/{id}/history - GET
get-healthcareservice-id-_history 3 params → 200
GET
/HealthcareService/_history
/HealthcareService/history - GET
get-healthcareservice-_history 2 params → 200
GET
/InsurancePlan
/InsurancePlan - GET
get-insuranceplan 21 params → 200
GET
/InsurancePlan/{id}
/InsurancePlan/{id} - GET
get-insuranceplan-id 1 param → 200
GET
/InsurancePlan/{id}/_history/{vid}
/InsurancePlan/{id}/history/{vid} - GET
get-insuranceplan-id-_history-vid 2 params → 200
GET
/InsurancePlan/{id}/_history
/InsurancePlan/{id}/history - GET
get-insuranceplan-id-_history 3 params → 200
GET
/InsurancePlan/_history
/InsurancePlan/history - GET
get-insuranceplan-_history 2 params → 200
GET
/Location
/Location - GET
get-location 21 params → 200
GET
/Location/{id}
/Location/{id} - GET
get-location-id 1 param → 200
GET
/Location/{id}/_history/{vid}
/Location/{id}/history/{vid} - GET
get-location-id-_history-vid 2 params → 200
GET
/Location/{id}/_history
/Location/{id}/history - GET
get-location-id-_history 3 params → 200
GET
/Location/_history
/Location/history - GET
get-location-_history 2 params → 200
GET
/Organization
/Organization - GET
get-organization 20 params → 200
GET
/Organization/{id}
/Organization/{id} - GET
get-organization-id 1 param → 200
GET
/Organization/{id}/_history/{vid}
/Organization/{id}/history/{vid} - GET
get-organization-id-_history-vid 2 params → 200
GET
/Organization/{id}/_history
/Organization/{id}/history - GET
get-organization-id-_history 3 params → 200
GET
/Organization/_history
/Organization/history - GET
get-organization-_history 2 params → 200
GET
/Practitioner
/Practitioner - GET
get-practitioner 24 params → 200
GET
/Practitioner/{id}
/Practitioner/{id} - GET
get-practitioner-id 1 param → 200
GET
/Practitioner/{id}/_history/{vid}
/Practitioner/{id}/history/{vid} - GET
get-practitioner-id-_history-vid 2 params → 200
GET
/Practitioner/{id}/_history
/Practitioner/{id}/history - GET
get-practitioner-id-_history 3 params → 200
GET
/Practitioner/_history
/Practitioner/history - GET
get-practitioner-_history 2 params → 200
GET
/PractitionerRole
/PractitionerRole - GET
get-practitionerrole 20 params → 200
GET
/PractitionerRole/{id}
/PractitionerRole/{id} - GET
get-practitionerrole-id 1 param → 200
GET
/PractitionerRole/{id}/_history/{vid}
/PractitionerRole/{id}/history/{vid} - GET
get-practitionerrole-id-_history-vid 2 params → 200
GET
/PractitionerRole/{id}/_history
/PractitionerRole/{id}/history - GET
get-practitionerrole-id-_history 3 params → 200
GET
/PractitionerRole/_history
/PractitionerRole/history - GET
get-practitionerrole-_history 2 params → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

Body
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sun-life-dentaquest-fhir-provider-directory-openapi.json Raw ↑
Where this information came from

This is an independent, third-party profile of DentaQuest 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.