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
Dexcare

DexCare Visit Service API

Create and follow on-demand virtual visits, and read regional virtual-care availability and estimated wait times. Declares two distinct bearer schemes, PatientJWT and StaffJWT, bound to different operations. OpenAPI 3.0.3, version 9.2.0, 9 operations.

Documentation Provider Profile APIs.io OpenAPI GitHub

This API exposes 9 operations across 9 paths, organized into 6 resource areas. It is described by OpenAPI 3.0.3, at version 9.2.0.

Requests are made against 7 base URLs: https://ecvapi.frosh.dex.care/api/9, https://ecvapi.care-uat.ecommunity.com/api/9, https://ecvapi.care-uat.froedtert.com/api/9, https://ecvapi.care-uat.psjhealth.org/api/9, https://ecvapi.kp-uat.dex.care/api/9, https://ecvapi.uat.houstonmethodistcare.org/api/9, https://ecvapi.demo-uat.dex.care/api/9.

9 operations 9 paths 0 schemas 6 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
9.2.0
Base URL
https://ecvapi.demo-uat.dex.care/api/9
Authentication
HTTP Bearer, HTTP Bearer
Contact
DexCare Engineering
Resource Areas
6

Authentication & Security 2

DexCare Visit Service API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (PatientJWT). It accepts HTTP bearer tokens (JWT) (StaffJWT).

  • PatientJWT — [Patient] Bearer token format Bearer {KEY}
  • StaffJWT — [Staff] Bearer token format Bearer {KEY}

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 6 GET, 2 POST, 1 PUT. They span 6 resource areas: visits, waittimes, assignmentqualifiers, modalities, tokbox, virtual-visits. Each is listed below with its method, path, parameters, and response codes.

visits 3
POST
/visits
request visit
createVisitV9 1 param body → 200400401403409
GET
/visits/{visitId}/waittime
get virtual visit wait time
getEstimatedVirtualVisitWaitTime 1 param → 200400401404
GET
/visits/{visitId}/summary
Returns a summarized visit
visitSummaryV9 2 params → 200401404500
waittimes 2
GET
/regions/{regionCode}/waittimes
get availability and wait times for region
getRegionAvailabilityAndWaitTimes 6 params → 200
GET
/regions/waittimes
get availability and wait times
getAvailabilityAndWaitTimes 6 params → 200
assignmentqualifiers 1
GET
/assignmentqualifiers
get assignment qualifiers
getAssignmentQualifiers 2 params → 200
modalities 1
GET
/modalities
get all modalities
getModalities 2 params → 200
tokbox 1
POST
/tokbox-events
Send an update for the virtual visit via webhook configured in Tokbox
processTokboxSessionEvents 1 param body → 202
virtual-visits 1
PUT
/visits/{visitId}/acceptTerms
Update whether patient accept terms for a visit
updateAcceptTerms 2 params → 200401404409500

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dexcare-visit-service-openapi.yml Raw ↑
#Virtual Care#Telehealth#Scheduling
← Back to D APIs
API Details
ID
dexcare:dexcare-visit-service-api
Base URL
https://ecvapi.demo-uat.dex.care/api/9
Docs
https://developers.dexcarehealth.com/api/visits/
Provider
Dexcare
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=dexcare-dexcare-visit-service-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/dexcare-dexcare-visit-service-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 DexCare Visit Service 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.