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

Jane Care Plans API

The CarePlans API from Jane — 4 operation(s) for careplans.

Jane Care Plans API is one of 21 APIs that Jane publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Care Plans. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 4 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 2026-01-01.

Requests are made against a single base URL, https://jdpdocsdemo.jane.qa.

7 operations 4 paths 9 schemas 3 GET2 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-01-01
Server
https://jdpdocsdemo.jane.qa
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Jane Care Plans API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 27 scopes. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • OAuth2 — OAuth2 authorization code flow with PKCE (Proof Key for Code Exchange) support. PKCE Flow Required: All integrations must use PKCE flow for authentication. PKC…

Paths & Operations 7

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

CarePlans 7
POST
/api/2026-01-01/medical-record/care-plans
Create a care plan
createCarePlan body → 201400
GET
/api/2026-01-01/medical-record/care-plans
List care plans
listCarePlans 6 params → 200400401403
POST
/api/2026-01-01/medical-record/care-plans/{care_plan_id}/activities
Create a care plan activity
createCarePlanActivity 1 param body → 201400
GET
/api/2026-01-01/medical-record/care-plans/{care_plan_id}
Get a care plan
getCarePlan 1 param → 200404
PATCH
/api/2026-01-01/medical-record/care-plans/{care_plan_id}
Update a care plan
updateCarePlan 1 param body → 200400404422
GET
/api/2026-01-01/medical-record/care-plans/{care_plan_id}/activities/{care_plan_activity_id}
Get a care plan activity
getCarePlanActivity 2 params → 200404
PATCH
/api/2026-01-01/medical-record/care-plans/{care_plan_id}/activities/{care_plan_activity_id}
Update a care plan activity
updateCarePlanActivity 2 params body → 200400404422

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are care_plan (12 properties), care_plan_activity (6 properties), care_plans_response (5 properties), update_care_plan_activity_request (1 property). Each schema is shown below with its type and property counts.

care_plan_activity
object
6 properties 1 required
update_care_plan_request
object
1 property
care_plans_response
object
5 properties 3 required
care_plan
object
12 properties 2 required
not_found_error_response
object
bad_request_error_response
object
create_care_plan_request
object
1 property
update_care_plan_activity_request
object
1 property
create_care_plan_activity_request
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jane-app-careplans-api-openapi.yml Raw ↑

Other APIs Jane publishes across the network.

Jane Patients API
Jane Appointments API
Jane Practice and Scheduling API
Jane Medical Records API
Jane Documents API
Jane Webhooks API
Jane Extensions API
Jane Appointments API
Jane Catalog API
Jane Company API
Jane Disciplines API
Jane Document Uploads API
Where this information came from

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