LAIKA Integration Lab — AQORIO Voice Sandbox

AQORIO × LAIKA

Integration Lab

LAIKA adapter · AITEM

Integration Lab

Adapter ready · dry run

LAIKA API v1.01. Aqorio holds every credential and token server-side. No LAIKA host is assumed: until AITEM supplies a base URL and credentials, the adapter renders the exact requests it would send and transmits nothing.

Mode: DRY RUN — not connected to LAIKA
Host: Not supplied — LAIKA's API document specifies no host
Authenticated: No LAIKA token held
Readiness: Checking configuration…
Licences: Licence state may be inspected. Aqorio never initiates a LAIKA licence purchase; any purchase redirect is surfaced to the user, never followed automatically.

Configuration readiness (names only — values are never read into the browser)

Authentication stages

01External system authentication
POST /ext-sys-login with the external system ID and secret
requires: LAIKA_BASE_URL · LAIKA_EXTERNAL_SYSTEM_ID · LAIKA_EXTERNAL_SYSTEM_SECRET
02System token refresh
GET /ext-sys-refresh-token with the externalSystemRefreshToken header
requires: externalSystemRefreshToken (runtime)
03User authentication
POST /user-login with the system access token header; may return a registrationURL instead
requires: LAIKA_USER_EMAIL · LAIKA_USER_SECRET
04User token refresh
GET /user-refresh-token with externalSystemAccessToken + userRefreshToken
requires: userRefreshToken (runtime)

Supported endpoints

systemLoginauth
External system login
POST /ext-sys-login · auth none
body { externalSystem: { ID, Secret } } → externalSystemAccessToken + externalSystemRefreshToken
refreshSystemTokenauth
Refresh external system token
GET /ext-sys-refresh-token · auth none
header externalSystemRefreshToken → new externalSystemAccessToken
userLoginauth
User login
POST /user-login · auth system
body { user: { email, secret } } → userAccessToken + userRefreshToken, or registrationURL
refreshUserTokenauth
Refresh user token
GET /user-refresh-token · auth system
headers externalSystemAccessToken + userRefreshToken
listUsersread
List users (admin)
POST /admin-list-user · auth system
retrieveUserread
Retrieve a user (admin)
POST /admin-retrieve-user · auth system
createUserwritehuman confirmation
Create a user (admin)
POST /admin-create-user · auth system
modifyUserwritehuman confirmation
Modify a user
POST /modify-user · auth system+user
listPatientsread
List patients
POST /list-patient · auth system+user
retrievePatientread
Retrieve a patient
POST /retrieve-patient · auth system+user
createPatientwritehuman confirmation
Create a patient
POST /create-patient · auth system+user
body { patient: { name, owner { firstName, lastName }, gender M|F, sterilized unknown|no|yes, species Cat|Dog, breed, birthdate } }
modifyPatientwritehuman confirmation
Modify a patient
POST /modify-patient · auth system+user
createMedicalRecordwritehuman confirmation
Create a medical record
POST /create-medical-record · auth system+user
body { patientId, type, sampleDate, resultDate, laboratoryData[], findings[] }
createOrRetrieveSessionwritehuman confirmation
Create or retrieve a consultation session
POST /create-retrieve-session · auth system+user
Sessions are patient-specific and remain active for 72 hours

Test LAIKA connection

Read-only by construction: system login, user login and one patient list. No write is ever attempted by this control. In dry run the three requests are rendered in full and nothing is transmitted.

Vertical slice · prepare next patient

Reads the next appointment from the Aqorio demonstration practice records, maps it to the LAIKA patient schema, checks whether a LAIKA patient would be retrieved or created, maps the recent diagnostics into a medical record and prepares a consultation session. Writes never run until you confirm.

Observe
Bind
Execute
Verify