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

Account creation (e.g., identity proofing, eConsent) that is required for a patient to progress on the xCures Platform.

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

Tagged areas include Application. 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 3 paths, and defines 4 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 3 paths 4 schemas 1 GET2 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 Application API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer).

Paths & Operations 3

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

Application 3

Account creation (e.g., identity proofing, eConsent) that is required for a patient to progress on the xCures Platform.

GET
/api/v1/patient-registry/application/{id}
Get Application
PublicApplicationController_get 2 params → 200400401403429
POST
/api/v1/patient-registry/application
Create Application
PublicApplicationController_create 1 param body → 201400401403429
POST
/api/v1/patient-registry/application/{id}/resend-verification
Resend Application Invite
PublicApplicationController_resendVerification 2 params body → 201400401403429

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Application (22 properties), CreateApplicationResponse (21 properties), CreateApplication (17 properties), ApplicationWebhooks (3 properties). Each schema is shown below with its type and property counts.

CreateApplication
object
17 properties 7 required
CreateApplicationResponse
object
21 properties 9 required
Application
object
22 properties 9 required
ApplicationWebhooks
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xcures-application-api-openapi.yml Raw ↑

Other APIs xCures publishes across the network.

xCures Checklist API
xCures Clinical Concepts API
xCures Document API
xCures FHIR API
xCures Project API
xCures Query 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 Application 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.