Ritten API
Integuru generates a production-ready HTTP API for Ritten, the behavioral health EMR used by detox, residential, PHP, IOP and outpatient programs. 18 verified actions cover the census and admissions roster, individual and group encounters with notes and attachments, signed encounter history, form submissions and PDF export, patient documents and payer authorizations, for AI documentation, UR and outcomes teams.
18
Verified actions live today
<3 sec
Response latency per call
99.9%+
Reliability rate on generated APIs
24/7
On-call maintenance on Production plans
Integration facts
- Authenticates against
- https://login.ritten.io/login
- Authentication
- Login flows, including 2FA, handled by Integuru using your own Ritten credentials.
- Approach
- Direct HTTP requests, with no browser automation or RPA involved.
Endpoints
Available actions
Don't see the action you need?
The actions above cover the most common Ritten integration patterns, but they're not the full picture. Integuru can build additional workflows for any capability the platform exposes. Our Managed Service handles scoping, building, and maintaining custom actions on your behalf, so just let us know what you need.
Guide
Ritten integration guide
Does Ritten have a public API?
Ritten, the behavioral health EMR for detox, residential, PHP, IOP and outpatient programs, publishes no developer API or documentation; its site says integration options are confirmed with each program during evaluation. Integuru generates a production-ready HTTP API from your Ritten login, with 18 verified actions across the census, individual and group encounters, forms, documents and authorizations.
An evaluation-time conversation works for a treatment center choosing its EMR. A documentation vendor whose customer already runs Ritten needs the encounter and the group note reachable this month. Integuru covers that with direct HTTP requests to the endpoints the Ritten web app uses, authenticated, using your own credentials, with login and any second factor handled for you.
What you can do with the Ritten API
A residential program's day runs from a morning process group through an intake to an afternoon utilization review call, and that last call needs signed notes and the current authorization for every client under review. The actions cover each of those.
Census and chart
list_patientsreturns the roster filtered byprogram_statuses(defaultactive;formeris the discharged bucket),admit_start_dateandadmit_end_date, andsearch_texton name or MRN, 20 per page increatedAt_descorder to match the roster UI.get_patientandget_patient_v2read one patient UUID;get_patient_authorizationsreturns the payer authorizations on file for that patient.
Individual and group encounters
create_encounteropens an encounter for apatient_idwith anencounter_typematched exactly to the account's individual types;datedefaults to today.create_group_encounterbuilds a session from atitle, anencounter_template_id(fromlist_group_encounter_templates) and aparticipantsarray with optional per-client notes, plusdate,start_time,end_timeand PDFdocuments.send_forms_to_charts: truesubmits the session to every participant's chart; the default leaves it in Draft.list_encounters_by_datereturns every encounter betweendate_fromanddate_toin clinic-local time, optionally filtered by exactencounter_type.list_patient_encounterspages one patient's history;list_patient_encounters_detailedadds date bounds in atimezoneand, withinclude_signature_detail, who signed and cosigned each form.delete_encounteranddelete_document_and_empty_encounterremove only what the acting user created and only when the encounter is empty.
Forms and documents
list_patient_formsfilters a patient's forms bysearch_queryon title;get_form_submissionreturns a completed form's answers andexport_form_pdfrenders it, both byform_instance_id.list_patient_documents,get_document(as adataurlormetadataonly) andupload_patient_documentcover the chart's attachments. Uploads takefile_name,file_base64, an exactdocument_type(defaultCorrespondence), an optionaltitle, and anencounter_idto file the document under a session rather than loosely on the chart.
Who uses this
AI scribe and group-note tools write the morning process group through create_group_encounter, one note per participant, and file the session with send_forms_to_charts. Utilization review teams pull list_patient_encounters_detailed with signature detail and get_patient_authorizations before a payer call, so the case is argued from signed notes and the current auth. Outcomes and analytics teams read get_form_submission for every completed assessment to track scores across a stay. Programs that run a second EMR at another level of care pair this page with the Sunwave and Lightning Step integrations, and billing teams add the Insync page for claims work. The healthcare industry page covers behavioral health alongside the rest of the clinical stack.
Setup notes
Integuru authenticates against login.ritten.io with your Ritten user. Every identifier on this platform is a UUID: patients, encounters, documents and form instances. Encounter and document types are matched by exact display name, and a mismatch returns the valid names rather than creating anything. Date ranges are clinic-local calendar days; list_patient_encounters_detailed lets you set the IANA timezone, which defaults to America/Los_Angeles. upload_patient_document accepts document_date for compatibility but Ritten records the server upload time.
Get started
Install the CLI and connect your Ritten login:
npm install -g integuru
Or sign in at app.integuru.com, add Ritten, and call list_patients for the active census. Scheduling, medication orders, claims and the bed board are built on request through the Managed Service.
Guides in Healthcare
Platform API guides in this vertical
Good to know
Before you start
- Can I use it today?
- Yes. Every action listed above has been verified against live Ritten traffic. Install the CLI or sign in at app.integuru.com, connect your Ritten account, and start calling the endpoints.
- What if Ritten changes or breaks?
- On Production plans the Integuru team is on call around the clock, with auth auto-healing included, so target-platform changes get fixed by Integuru rather than by your engineers.
- What does it cost?
- Start on the Free plan at $0/month with 100 API calls/month. Production starts at $499/month with 24/7 on-call maintenance and auth auto-healing.
FAQ