Application APIs
Citt.ai uses authenticated Next.js API routes for app workflows including clients, appointments, assessments, notes, billing, and account operations.
Developers & integrations
Citt.ai is primarily a therapist-led product. This page gives implementation teams a clear overview of integration surfaces and governance.
Integration surfaces
These surfaces are exposed through the application and configured per deployment. We do not present Citt.ai as an open API product with self-serve clinical automation.
Citt.ai uses authenticated Next.js API routes for app workflows including clients, appointments, assessments, notes, billing, and account operations.
Messaging integrations support opted-in care workflows such as check-ins, reminders, invites, and transactional notifications.
Stripe, Paystack, PayPal, WhatsApp, Resend, and calendar events are handled through verified server-side webhook routes where configured.
Clinical access is scoped around therapist-client relationships, role checks, audit logs, and server-side authorization.
Patient-originated support messages pass through deterministic risk screening before AI responses are generated.
For partner implementations, we provide data-flow notes, security documentation, and integration planning material during procurement.
Governance
Citt.ai integrations must preserve therapist oversight, patient consent, role-based access, and crisis-screening behavior. We do not support integrations that bypass safety checks or expose patient data outside scoped care relationships.
Patient support messages keep risk screening in the hot path.
Clinical data access must be scoped by role and care relationship.
External workflows need explicit consent and purpose limitation.
Raw AI orchestration and internal tool calls are not exposed to patients or therapists.
Send context on your clinic, integration target, and procurement needs. We will share the right technical and safety material.
Email hello@citt.ai