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

xCures Query API

A specified, approved request for patient records across the network (e.g., via Carequality/TEFCA to support treatment activities, via TEFCA for IAS queries) with an associated status (e.g., “completed”).

xCures Query API is one of 11 APIs that xCures publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Query. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and a changelog.

This API exposes 3 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version V1.

Requests are made against a single base URL, https://partner.xcures.com.

3 operations 2 paths 6 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
V1
Base URL
https://partner.xcures.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

xCures Query API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer).

Paths & Operations 3

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

Query 3

A specified, approved request for patient records across the network (e.g., via Carequality/TEFCA to support treatment activities, via TEFCA for IAS queries) with an associated st…

GET
/api/v1/patient-registry/query
Search Queries
PublicQueryController_search 9 params → 400401403429default
POST
/api/v1/patient-registry/query
Create Query
PublicQueryController_create 1 param body → 201400401403429
GET
/api/v1/patient-registry/query/{id}
Get Query
PublicQueryController_get 2 params → 400401403404429default

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are QueryDto (9 properties), Query (7 properties), GetQueryResponse (6 properties), QueryPaginationResult (6 properties). Each schema is shown below with its type and property counts.

QueryPaginationResult
object
6 properties 2 required
GetQueryResponse
object
6 properties 4 required
QueryDto
object
9 properties 9 required
CreateQueryDto
object
2 properties 1 required
QueryAttempt
object
5 properties 2 required
Query
object
7 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xcures-query-api-openapi.yml Raw ↑

Other APIs xCures publishes across the network.

xCures Application API
xCures Checklist API
xCures Clinical Concepts API
xCures Document API
xCures FHIR API
xCures Project API
xCures Reciprocity Template API
xCures Subject API
xCures Summary API
xCures O Auth API
Where this information came from

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