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

Alleva Treatment Plans API

The TreatmentPlans API from Alleva — 10 operation(s) for treatmentplans.

Alleva Treatment Plans API is one of 37 APIs that Alleva publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Treatment Plans. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 10 operations across 10 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.helloalleva.com.

10 operations 10 paths 18 schemas 6 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.helloalleva.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Alleva Treatment Plans API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer). By default, every request must be authenticated.

  • Bearer — JWT Authorization header using the Bearer scheme. Enter Bearer [space] and then your token in the text input below. Example: Bearer 12345abcdef

Paths & Operations 10

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

TreatmentPlans 10
POST
/treatment-plans/{id}/signature
3 params body → 200
POST
/v{version}/treatment-plans/{id}/signature
4 params body → 200
POST
/treatment-plans/{id}/review-signature
3 params body → 200
POST
/v{version}/treatment-plans/{id}/review-signature
4 params body → 200
GET
/treatment-plans/{id}/diagnosis
3 params → 200
GET
/v{version}/treatment-plans/{id}/diagnosis
4 params → 200
GET
/treatment-plans
7 params → 200
GET
/v{version}/treatment-plans
8 params → 200
GET
/treatment-plans/{id}
3 params → 200
GET
/v{version}/treatment-plans/{id}
4 params → 200

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are ClientDiagnosis (21 properties), User (19 properties), TreatmentPlan (18 properties), Facility (14 properties). Each schema is shown below with its type and property counts.

UserName
object
4 properties
UserImageUrl
object
3 properties
User
object
19 properties
Signature
object
5 properties
UserLicenseType
object
7 properties
TreatmentPlan
object
18 properties
ResourceLink
object
2 properties
State
object
6 properties
Goal
object
3 properties
Facility
object
14 properties
Intervention
object
3 properties
BehavioralDefinition
object
2 properties
DiagnosisPriority
object
2 properties
Objective
object
4 properties
Problem
object
5 properties
UserLicense
object
11 properties
ClientDiagnosis
object
21 properties
Address
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

alleva-treatmentplans-api-openapi.yml Raw ↑

Other APIs Alleva publishes across the network.

Alleva Advanced Form API
Alleva Advanced Form Data Backup API
Alleva Advanced Form Element API
Alleva Advanced Form Instance API
Alleva Appointments API
Alleva Bed API
Alleva Bed Occupancy API
Alleva Bed Reservation API
Alleva Client Device API
Alleva Clients API
Alleva Data Facet API
Alleva Data Value API
Where this information came from

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