StrydeOS API Reference

84 endpoints · Last updated 17 June 2026

84
Total Endpoints
13
Business Areas
6
Webhook Integrations
7
Auth Methods
🏥
Clinic Onboarding & Signup

How clinics join StrydeOS

When a clinic owner signs up, the system creates their account, sets up their workspace, and starts a 30-day free trial. Behind the scenes, this involves creating a secure login (Firebase Auth), a clinic record in the database, and a billing profile with Stripe.

Clinic owners can also invite their clinicians by email. Each invited clinician gets a password-reset link to set up their own login.

During setup, StrydeOS can auto-fill the clinic's Ava knowledge base from public sources (Google Places, Companies House, the clinic website), and self-heals a clinician's own record on first login so their data lands under the right clinic.

Who uses this: Clinic owners signing up, StrydeOS admin provisioning pilot clinics manually
/api/clinic/signup /api/admin/provision-clinic /api/clinic/check-go-live /api/clinic/resend-invite /api/clinic/enrich /api/clinic/ensure-clinician
👤
Clinician Management

Adding and managing clinicians

Clinic owners can add clinicians to their practice. The number of clinicians allowed depends on the billing tier: Solo (1), Studio (2–5), Clinic (6+). Extra seats can be purchased if you need more capacity within your tier.

Each clinician is linked to their PMS practitioner ID so their appointment data flows through automatically. Owners and admins can change a team member's role (owner / admin / clinician) at any time, with safeguards: the last owner can't be demoted, you can't change your own role, and admins can't grant owner. Clinicians can also opt in or out of the Heidi clinical scribe individually.

Who uses this: Clinic owners and admins managing their team
/api/clinicians/add /api/clinicians/[id]/role /api/clinicians/[id]/heidi /api/billing/seats
💳
Billing & Subscriptions

How payments work

StrydeOS uses Stripe for all billing. Clinics choose which modules they want (Intelligence, Pulse, Ava, or Full Stack bundle), pick a tier based on clinic size, and select monthly or annual billing (20% discount for annual).

When a clinic subscribes, Stripe tells StrydeOS which modules to activate. If a payment fails, the clinic is marked "past due" but access isn't revoked immediately — giving time to update payment details via the billing portal.

Ava (voice receptionist) has a one-time £195 setup fee in addition to the recurring subscription. This setup fee applies only when subscribing to Ava as a standalone module — Full Stack does not include a setup fee.

Who uses this: Clinic owners managing their subscription
/api/billing/checkout /api/billing/portal /api/billing/seats /api/billing/webhooks
🔗
Practice Management & HEP Integrations

Connecting your practice software

StrydeOS connects to your existing Practice Management System (PMS) to pull in appointment data, clinician rosters, and patient records. Supported systems: WriteUpp, Cliniko, Halaxy, Zanda (Power Diary). PPS and TM3 support coming soon.

You enter your PMS API key in Settings, test the connection, and StrydeOS starts syncing. Data refreshes automatically — WriteUpp pushes updates in real-time via webhooks; other systems sync on a schedule.

For clinics without API access, you can upload CSV exports of your appointment or patient data. StrydeOS auto-detects common formats or lets you create a custom column mapping.

Home Exercise Programme (HEP) data flows in from your connected HEP provider (Physitrack, Rehab My Patient, or Wibbi) — tracking programme assignments, adherence, and completion rates per patient.

Who uses this: Clinic owners connecting their PMS during onboarding, or uploading CSV exports
/api/pms/save-config /api/pms/test-connection /api/pms/disconnect /api/pms/sync /api/pms/import-csv /api/pms/import-csv/inbound /api/pms/csv-schema /api/pms/import-history /api/hep/save-config /api/hep/test-connection /api/hep/disconnect
📞
Ava — Voice Receptionist

How Ava handles calls and bookings

Ava is StrydeOS's AI voice receptionist, powered by ElevenLabs Conversational AI and Twilio telephony. When a patient calls, Ava answers, understands their request, and can book appointments directly into your PMS.

The booking flow: Patient calls → Ava converses → confirms booking details → n8n automation creates the appointment in your PMS → a copy is saved in StrydeOS for tracking. If the PMS write fails (e.g., the PMS is briefly offline), StrydeOS saves the booking locally and retries automatically.

Call data — duration, outcome (booked, cancelled, escalated, voicemail), transcripts, and sentiment — flows into the Receptionist dashboard so you can see how Ava is performing. A daily digest email summarises the day's calls. Owners can pause or resume Ava in one tap (which attaches or detaches the clinic's phone number from the agent), provision a UK number, sync the knowledge base, and warm-transfer a caller to reception when needed.

Who uses this: Automated — Ava handles calls; clinic owners view results and control Ava from the dashboard
/api/ava/agent /api/ava/provision-number /api/ava/knowledge /api/ava/toggle /api/ava/tools /api/ava/transfer /api/ava/digest /api/ava/post-call /api/bookings/create /api/bookings/retry-pms /api/webhooks/elevenlabs
💬
Patient Communications (Pulse)

Automated patient messaging

Pulse sends automated SMS and email messages to patients at the right moment. Six sequences run automatically:

  • Rebooking prompt — 72 hours after their last session
  • HEP reminder — before their next appointment
  • Review prompt — on discharge (includes NPS collection)
  • Reactivation (90 days) — for patients who haven't returned
  • Reactivation (180 days) — second nudge for lapsed patients
  • Insurance pre-auth — before the first session if flagged

When patients reply to a review prompt with an NPS score (0–10), StrydeOS automatically parses it and logs it to the Reputation dashboard. All messages are tracked: email opens and clicks (via Resend) and SMS delivery (via Twilio) flow back as delivery webhooks, so the Pulse dashboard shows open rates, click rates, and whether the patient rebooked.

Who uses this: Automated — triggered by patient events; clinic owners view results in Pulse dashboard
/api/comms/send /api/n8n/callback /api/webhooks/writeupp /api/webhooks/resend /api/webhooks/twilio
🛡️
Insurance & Patient Intake

Collecting insurance details safely, before the appointment

For insured patients, StrydeOS sends a secure, single-use link asking for their insurer, policy number, and address before their first session. A daily job polls upcoming Cliniko appointments and emails the link automatically; staff can also send one on demand, or Ava can text it mid-call.

The patient form is public but token-gated — it never touches your PMS. Submissions land in a staff review queue where sensitive fields are redacted to the last four digits. Only when a staff member approves does the insurance detail get written back to the patient's PMS record. Staff can also enter pre-authorisation codes received from insurers (authorised session counts, excess, expiry).

Who uses this: Patients (intake form); clinic staff (review, approve, pre-auth); automated (daily polling)
/api/insurance/poll-and-send /api/insurance/send-one /api/insurance/intake-link /api/insurance/intakes /api/insurance/intakes/[id] /api/intake/[token] /api/patients/pre-auth /api/integrations/inbound-email/provision
📈
Clinical Intelligence

Turning the numbers into action

The Intelligence module watches each clinic's KPIs and surfaces what changed and why. A daily detection pass creates insight events (drop-offs, anomalies, wins), feeds the Pulse re-engagement queue, and fires urgent alerts when something needs attention now.

Two weekly emails go out automatically: a State of the Clinic summary for owners (Sunday), and a per-clinician digest with each clinician's own stats benchmarked against the UK average — never naming or shaming, and revenue is never shown to clinicians (Monday). A separate value pass attributes outcomes back to revenue so owners can see the commercial impact of clinical work.

Who uses this: Automated (daily/weekly cron); owners and admins can trigger manually
/api/intelligence/detect /api/intelligence/value /api/intelligence/digest /api/intelligence/clinician-digest
📝
Clinical Scribe (Heidi)

Connecting the Heidi clinical scribe

Clinics can connect Heidi Health as their clinical scribe. The clinic stores an encrypted API key, tests the connection, and runs a sync. Heidi issues a per-clinician token from each clinician's own email, so every team member opts in (or out) individually from their profile.

Who uses this: Owners and admins (connect); each clinician (opt in/out)
/api/heidi/save-config /api/heidi/test-connection /api/heidi/sync /api/heidi/disconnect /api/clinicians/[id]/heidi
Reputation & Reviews

Tracking your Google reputation

Clinics connect their Google Business profile by Place ID. StrydeOS verifies the credentials (returning the place name, rating, and review count for confirmation), then pulls reviews so rating and review-velocity sit alongside the NPS data in the Reputation dashboard. Disconnecting keeps the cached reviews so velocity history is preserved.

Who uses this: Clinic owners and admins connecting their Google profile
/api/reviews/save-config /api/reviews/test-connection /api/reviews/disconnect
📊
Data Pipeline & Metrics

How your KPIs are calculated

Every day at 6:00 AM UTC, StrydeOS runs its data pipeline. This pulls the latest data from your PMS, syncs patient and appointment records, computes the seven KPI metrics (follow-up rate, HEP compliance, programme assignment, utilisation, DNA rate, revenue per session, NPS), and triggers any due communications.

WriteUpp clinics also get near real-time updates — when an appointment is created or changed in WriteUpp, a webhook fires and StrydeOS re-computes within seconds.

For new clinics, a one-time 90-day backfill pulls historical data so you have context from day one. A second pass computes deep metrics — retention curve, cost of the empty chair, net growth, rebooking lag, discharge quality, and patient lifetime value. A daily data-health check flags any clinic whose PMS or CSV feed has gone stale, and a weekly cleanup enforces GDPR data-retention windows.

Who uses this: Runs automatically; clinic owners or superadmins can trigger manually
/api/pipeline/run /api/pipeline/backfill /api/metrics/compute /api/metrics/deep /api/data-health/check-staleness /api/data-health/cleanup /api/pms/sync
🔒
Compliance & Data Privacy

Patient data rights and compliance

StrydeOS supports GDPR and data privacy requirements out of the box:

  • Subject Access Requests (SAR) — patients can request a copy of all their data. Clinic owners export it as JSON with one click. All exports are audit-logged.
  • Data Deletion — patients can request deletion. The system marks records for removal with a 30-day grace period before purging.
  • BAA (Business Associate Agreement) — US clinics can accept a BAA clickthrough for HIPAA compliance.
  • Audit Trail — sensitive actions (data exports, config changes, SAR fulfilment) are logged with timestamps, user IDs, and IP addresses.
Who uses this: Clinic owners handling patient data requests
/api/compliance/sar /api/compliance/sar/[id]/export /api/compliance/sar/[id]/delete /api/compliance/baa
⚙️
Platform Health, Auth & Admin

Sign-in, health monitoring, and internal tools

Users sign in with Firebase, which StrydeOS exchanges for a short-lived, HMAC-signed session cookie (8-hour clinical workday). A no-login demo session is available for the public sandbox. Health endpoints report overall platform status and per-clinic module heartbeats (Ava, Intelligence, Pulse).

The StrydeOS team (superadmins) use the rest to monitor system health, run schema migrations, diagnose integration issues, and manage clinics. The integration health dashboard shows sync success rates across all clinics — if a PMS connection is degrading, the team can see it before the clinic owner notices. A secured MCP endpoint also exposes clinic operations to approved AI assistants.

Who uses this: All users (sign-in); StrydeOS superadmins (health, migrations, diagnostics, MCP)
/api/auth/session /api/auth/demo /api/health /api/health/modules /api/admin/integration-health /api/admin/run-migrations /api/debug/writeupp-probe /api/mcp