Citt.ai
Integration & API

Built for institutional
integration from day one.

REST APIs, 154 AI tools, WhatsApp integration, and multi-tenant architecture designed for health systems deploying at scale.

Talk to our integration teamView safety architecture

Integration surfaces

Every capability in Citt.ai is accessible via API. These are the primary surfaces used in institutional integrations.

REST API

Core

Standard HTTPS endpoints for all platform operations. Patient management, clinical data, assessments, billing, and scheduling, all accessible via authenticated API routes.

GET /api/patients/[id]/pre-session-context
POST /api/chat/stream
GET /api/patients/[id]/assessments
POST /api/transcription/save

AI Tools (MCP)

154 tools

154 natural language AI tools powering the Ask Citt assistant. Each tool is a discrete, typed capability: session prep, risk indicators, clinical notes, billing queries, and more.

get_session_prep - pre-session patient brief
get_risk_indicators - safety pattern analysis
list_patient_check_ins - check-in history
get_treatment_goals - goal tracking

WhatsApp Integration

WhatsApp Business

Native WhatsApp Business API integration. Patients receive and respond to check-ins, chat with their AI co-pilot, and receive crisis resources, all within WhatsApp.

Inbound message handling
Check-in flow delivery
Crisis detection on WhatsApp messages
Intervention scheduling

Webhooks

Event-driven

Event-driven integrations for billing and communication events. Verified webhook signatures on all inbound payloads.

Stripe: subscription, payment, invoice events
Paystack: transfer success/failure (SA)
WhatsApp: message status callbacks
Resend: email delivery events

Realtime Subscriptions

Realtime

Live data subscriptions via Supabase Realtime. Listen for patient activity events, new messages, check-in submissions, and crisis alerts without polling.

New patient messages
Check-in submissions
Crisis alert triggers
Assessment completions

Safety API

Public

Aggregate safety metrics endpoint for trust reporting and institutional dashboards. PHI-safe: all metrics are aggregate with cohort size suppression.

GET /api/safety/metrics
Crisis detection rates
Platform-level safety statistics
CEP v2 evaluation targets
Multi-tenant architecture

Designed for health systems with 50+ therapists

Every data access in Citt.ai is enforced at the database layer via row-level security, not just application logic. A therapist can only see their assigned patients. An admin sees only their institution. Cross-tenant data leakage is architecturally prevented, not just policy-controlled.

Role hierarchy
Admin → Therapist → Patient
Enforced at the API layer and database RLS level
Data isolation
Row-level security
Every query scoped to authenticated user's assigned relationships
Therapist capacity
Tested to 50+ therapists
Per institution; no hard limit on caseload size
Patient assignment
patient_therapists junction
Explicit assignment required; no accidental cross-patient access
Admin visibility
Full institution scope
Admins see all patients/therapists in their organisation
Audit trail
All clinical actions logged
User ID, timestamp, action, resource type on every event
154 AI tools

Ask Citt: natural language access to everything

Every clinical operation in Citt.ai is accessible via the Ask Citt natural language interface. Therapists type a question; the AI selects and calls the right tool, fetches the data, and responds in plain language. No forms, no navigation.

"What should I know before my session with James today?"
"Show me PHQ-9 trend for Sarah over the last 3 months"
"Which patients have had crisis alerts this week?"
"Schedule a GAD-7 for Michael in two weeks"
"What coping strategies has Anna mentioned in sessions?"
"Generate session notes for this morning's transcription"

Ready to discuss integration?

Our integration team works with health system IT and clinical technology officers on technical design, security review, and pilot scoping.

Book a technical reviewEmail the team