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

The Prospects API from Alleva — 12 operation(s) for prospects.

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

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

This API exposes 16 operations across 12 paths, and defines 20 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.

16 operations 12 paths 20 schemas 4 GET4 PATCH8 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 Prospects 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 16

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

Prospects 16
POST
/prospects
2 params body → 200
GET
/prospects
7 params → 200
POST
/v{version}/prospects
3 params body → 200
GET
/v{version}/prospects
8 params → 200
PATCH
/prospects/{id}
3 params body → 200
GET
/prospects/{id}
3 params → 200
PATCH
/v{version}/prospects/{id}
4 params body → 200
GET
/v{version}/prospects/{id}
4 params → 200
POST
/prospects/{id}/contacts
3 params body → 200
POST
/v{version}/prospects/{id}/contacts
4 params body → 200
POST
/prospects/{id}/insurances
3 params body → 200
POST
/v{version}/prospects/{id}/insurances
4 params body → 200
PATCH
/prospects/insurances/{id}
3 params body → 200
PATCH
/v{version}/prospects/insurances/{id}
4 params body → 200
POST
/prospects/import
2 params body → 200
POST
/v{version}/prospects/import
3 params body → 200

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are AdmissionScreening (60 properties), ClientInsurances (28 properties), Prospect (24 properties), Document (17 properties). Each schema is shown below with its type and property counts.

Document
object
17 properties
JToken
array
Prospect
object
24 properties
DocumentData
object
4 properties
BulkProspect
object
6 properties
ClientImageUrl
object
3 properties
Phone
object
5 properties
Address
object
7 properties
BulkProspectReturn
object
3 properties
ResourceLink
object
2 properties
DocumentUrl
object
3 properties
AdmissionScreening
object
60 properties
BillingIntake
object
ExternalData
object
4 properties
BulkProspectReturnObject
object
5 properties
FaceToFace
object
12 properties
ClientName
object
8 properties
InsuranceReturn
object
2 properties
ClientContact
object
8 properties
ClientInsurances
object
28 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

alleva-prospects-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 Prospects 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.