Ritten
Ritten is a cloud-based electronic medical record (EMR), CRM and revenue-cycle platform built specifically for behavioral health and substance-use treatment organizations - detox, residential, PHP/IOP, and outpatient providers. Its browser-based product covers clinical documentation (group and individual notes, AI-assisted charting), scheduling, revenue-cycle management (claims, billing, authorizations), a HIPAA-compliant patient portal, treatment planning, compliance tooling (audit trails, signature routing), and outcomes reporting. Ritten publishes a public REST contract for integrating partners - the Ritten External API - documented with an OpenAPI 3.1.0 definition covering 56 paths, 71 operations and 93 schemas across patients, contacts, CRM cases, programs, facilities, organizations, tasks, encounters, forms, insurance payers, users and a 17-operation insights and reporting family, plus six webhook events. Authentication is OAuth 2.0 client_credentials with a required X-Ritten-Tenant header selecting the clinic instance; credentials are provisioned by Ritten to partners rather than self-service. Ritten is built for HIPAA-regulated and 42 CFR Part 2 confidentiality requirements with role-based access controls and audit logs, and supports operational integrations for e-prescribing, labs, eligibility/billing clearinghouses, and telehealth. Backed by 8VC and Threshold Ventures; based in Philadelphia, PA.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Ritten the way a machine reads it — 20 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Ritten scores 52.3/100 (developing), with a separate agent-readiness read of 32/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Ritten's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ritten/"
title="Ritten on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ritten.svg"
alt="Ritten Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/ritten/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ritten/"
title="Ritten on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ritten/card.svg"
alt="Ritten Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Ritten
Each block below is one kind of artifact we hold for Ritten. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Ritten Calendar API
The calendar API from Ritten — 2 operation(s) for calendar.
Ritten Cases API
Endpoints for accessing CRM cases (admissions pipeline).
Ritten Contacts API
The contacts API from Ritten — 3 operation(s) for contacts.
Ritten Encounters API
Endpoints for creating clinical encounters (visits) and discovering the encounter types they are created from.
Ritten Facilities API
Endpoints for accessing clinic facilities (service locations).
Ritten Forms API
Endpoints for accessing form definitions and form-related data.
Ritten Insights API
Ritten provides insights and reporting endpoints for analytics and data export. These endpoints return various reports about admissions, discharges, census, billing, and CRM dat...
Ritten Insurance API
The insurance API from Ritten — 2 operation(s) for insurance.
Ritten OAUTH API
OAuth 2.0 token endpoint for obtaining access tokens. This is the recommended way to authenticate with the Ritten External API.
Ritten Organizations API
Endpoints for accessing CRM organizations and organization members. Requires CRM to be available for the target clinic (`X-Ritten-Tenant`). Integrations must be explicitly provi...
Ritten Patients API
The patients API from Ritten — 8 operation(s) for patients.
Ritten Programs API
Endpoints for creating, accessing, and managing clinic programs.
Ritten Tasks API
Endpoints for accessing clinic tasks. Tasks linked to a client are only returned when the integration is authorized to read that client.
Ritten Users API
The users API from Ritten — 6 operation(s) for users.
Ritten Webhooks API
Ritten provides webhooks for various events that occur in the system. Integrating partners can subscribe to these events to receive real-time updates. Webhooks sent from Ritten ...
Scroll within the panel for all 15 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Ritten Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Ritten Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Ritten Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Ritten — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/ritten · machine-readable index on apis.io
This is an independent, third-party profile of Ritten, 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.