ConnectAI Developer API

v1 is live. Patients, appointments, availability, lab reports, prescriptions and batch are all serving today. Webhook delivery is switched on per integrator while we bring partners across one at a time.

What it does

A clinic running ConnectAI alongside its existing software should not have to keep two diaries. The API exists so the clinic's front desk stays on the system it already knows, while ConnectAI's WhatsApp bot, voice receptionist, website and Google listing all fill the same diary.

You → ConnectAI

Push your data in

Send patients, doctors, schedules and appointments booked in your system. Bookings you send consume real slot capacity, so ConnectAI's booking agents stop offering them.

ConnectAI → You

Receive appointment events

We POST a signed event to your URL whenever an appointment is created, rescheduled, cancelled or completed — whichever ConnectAI channel it came from.

You → Patient

Deliver reports and prescriptions

Push a lab report or a prescription and we hand it to the patient on WhatsApp, under the clinic's own rules about what goes out and when.

Base URL

https://api-ec2.connectai.care/master/integration/v1

Nothing to configure first

There is no registration step. You do not map your doctors, patients or locations before you start — every endpoint resolves what it needs from the request itself, using the phone numbers you already hold, and remembers the answer. Your first real call works.

How keys work

One key per clinic, issued by ConnectAI. If you are a software vendor serving forty clinics, you hold forty keys and call the same endpoints with each. That means a clinic switching vendors is a key rotation rather than a migration, and a key that leaks exposes exactly one clinic.

There is no self-serve signup. Ask your ConnectAI contact, or have the clinic ask, and the key is generated for you.