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

Ritten Cases API

Endpoints for accessing CRM cases (admissions pipeline).

Ritten Cases API is one of 15 APIs that Ritten publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cases. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.

This API exposes 6 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.ritten.io/v1.

6 operations 4 paths 11 schemas 2 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.ritten.io/v1
Resource Areas
1

Paths & Operations 6

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

cases 6

Endpoints for accessing CRM cases (admissions pipeline).

GET
/cases
List cases in a clinic
listCases 4 params → 200400
POST
/cases
Create a case
createCase body → 200400401
GET
/cases/{id}
Retrieve a case by ID
getCase 1 param → 200400404
PATCH
/cases/{id}
Update a case
updateCase 1 param body → 200400401404
POST
/cases/{id}/notes
Create a case note
createCaseNote 1 param body → 200400401404
POST
/cases/{id}/action-items
Create a case action item
createCaseActionItem 1 param body → 200400401404

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Case (13 properties), PatchCaseBody (11 properties), PostCaseBody (11 properties), CaseActionItem (7 properties). Each schema is shown below with its type and property counts.

PostCaseBody
object
11 properties 1 required
Program
object
3 properties
CaseActionItem
object
7 properties
PostCaseNoteBody
object
2 properties 1 required
PatchCaseBody
object
11 properties
CaseContact
object
A contact as it appears on a case. Deliberately narrower than the Contact returned by the /contacts endpoints: it carries identity only, with no email or organ…
7 properties
User
object
6 properties
PostCaseActionItemBody
object
1 property 1 required
Case
object
13 properties
CaseNote
object
5 properties
ListCases
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ritten-cases-api-openapi.yml Raw ↑

Other APIs Ritten publishes across the network.

Ritten Calendar API
Ritten Contacts API
Ritten Encounters API
Ritten Facilities API
Ritten Forms API
Ritten Insights API
Ritten Insurance API
Ritten OAUTH API
Ritten Organizations API
Ritten Patients API
Ritten Programs API
Ritten Tasks API
Where this information came from

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