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 Subject API

An individual patient created on the xCures Platform.

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

Tagged areas include Subject. 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 6 operations across 4 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version V1.

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

6 operations 4 paths 15 schemas 3 GET2 POST1 PUT

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 Subject API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer).

Paths & Operations 6

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

Subject 6

An individual patient created on the xCures Platform.

GET
/api/v1/patient-registry/subject
Search Subjects
PublicSubjectController_search 40 params → 200400401403429
POST
/api/v1/patient-registry/subject
Create Subjects
PublicSubjectController_create 1 param body → 201400401403409429
GET
/api/v1/patient-registry/subject/{id}
Get Subject
PublicSubjectController_get 2 params → 200400401403404429
PUT
/api/v1/patient-registry/subject/{id}
Update Subject
PublicSubjectController_update 2 params body → 200400401403404429
GET
/api/v1/patient-registry/subject/{id}/status/clinical-concepts
Get Clinical Concepts Status
PublicSubjectController_getClinicalConceptsStatus 2 params → 200400401403404429
POST
/api/v2/patient-registry/subject
Create Subject V2
PublicSubjectControllerV2_create 1 param body → 201400401403409429500503

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are CreateSubjectResult (25 properties), Subject (24 properties), CreateSubjectV2 (20 properties), CreateSubject (19 properties). Each schema is shown below with its type and property counts.

UpdateSubject
object
18 properties 2 required
Subject
object
24 properties 6 required
CreateSubjectBatchOptions
object
1 property
CreateSubject
object
19 properties 3 required
SubjectTagDto
object
11 properties 2 required
SubjectAdditionalName
object
3 properties
SubjectPaginationResult
object
6 properties 2 required
ProblemDetails
object
3 properties
SubjectExternalIdentifier
object
2 properties 2 required
CreateSubjectResult
object
25 properties 6 required
ClinicalConceptsStatusDto
object
2 properties 1 required
CreateSubjectV2
object
20 properties 3 required
CreateSubjectBatch
object
2 properties 1 required
CreateSubjectOptions
object
1 property
SubjectAddressDto
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xcures-subject-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 Query API
xCures Reciprocity Template API
xCures Summary API
xCures O Auth API
Where this information came from

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