Developers · Partner API

Ratatui Partner API

Invite-only API access for consent-scoped peptide and GLP-1 care data. Use Ratatui with Keragon to move patient-approved summaries, dose history, weight history, symptom alerts, and consent updates into healthcare workflows.

Request access Read quickstart

Base URL: https://api.ratatui.ai/v1

Quickstart

Read consent-scoped data with an invite-only key.

Ratatui partner API keys are scoped to one approved clinic or clinician and only to specific actions. Use fake data until production access and required BAA/security review are complete.

Request · patient summary

curl "https://api.ratatui.ai/v1/patients/summary?external_system=demo_ehr&external_patient_id=ehr_demo_456" \
  -H "Authorization: Bearer ratatui_test_REDACTED"

Response · fake data

{
  "ok": true,
  "summary": {
    "patient_id": "pat_demo_123",
    "consent_level": "limited",
    "shared_features": ["weight", "doses", "symptoms"],
    "latest_weight": { "value": 182, "unit": "lb" },
    "last_dose": {
      "medication": "Demo peptide",
      "amount": 5,
      "unit": "mg"
    }
  }
}

Resources

Endpoints for EHR and CRM sync.

GET/patients/summaryPatient summary by Ratatui ID or external link

GET/dosesDose history

GET/symptomsSymptom history

GET/weightsWeight history

GET/consentConsent and shared-feature status

POST/patients/linkExternal patient ID link

GET/patients/external-linkExternal link lookup

POST/webhooksWebhook subscription

POST/webhooks/revokeWebhook revocation

Webhooks

Start workflows when care events happen.

Ratatui sends signed HTTPS webhooks to Keragon when subscribed events happen. Verify the HMAC signature before trusting a payload.

dose.loggedsymptom.loggedweight.loggedsevere_symptom.alertpatient.consent.updated

Webhook signature

const signedPayload = `${timestamp}.${rawBody}`;
const expected = hmacSha256(webhookSigningSecret, signedPayload);
if (expected !== headerSignature) {
  throw new Error("Invalid Ratatui webhook signature");
}

Admin setup

Create, rotate, and revoke keys without storing plaintext secrets.

Approved doctor or clinic admins manage keys through protected admin endpoints. A key is shown once when created or rotated; Ratatui stores only a hash. Production keys require signed clinic BAA status, HIPAA mode, and signed Keragon BAA evidence.

Create keyIssues a one-time ratatui_test_ or ratatui_live_ secret for a scoped integration.

Rotate keyReplaces the secret immediately if a vendor, employee, or system changes.

Revoke keyDisables future calls while keeping audit history.

Record Keragon BAABlocks production API calls until signed evidence is saved.

Admin endpoints

GET  /api/admin/partner/v1/keys
POST /api/admin/partner/v1/keys
POST /api/admin/partner/v1/keys/rotate
POST /api/admin/partner/v1/keys/revoke
GET  /api/admin/partner/v1/compliance/keragon
POST /api/admin/partner/v1/compliance/keragon

Security

Built for cautious healthcare integrations.

Access is invite-only. Public docs do not mean public keys.

Every real integration must use explicit external patient IDs instead of name/date-of-birth guessing.

API keys are scoped by clinic or clinician, environment, allowed action, expiration, and revocation status.

Production partner API calls are blocked unless clinic BAA status, HIPAA mode, and signed Keragon BAA evidence are present.

Write requests require an Idempotency-Key header so retries do not duplicate work.

Webhook payloads are signed with HMAC headers and include event IDs and timestamps.

Ratatui is BAA-backed and HIPAA-compliant for approved production customers; it does not claim government HIPAA certification.

Keragon

Route into the healthcare systems clinics already use.

The first connector release is Keragon-first: Ratatui publishes safe events and read actions, then Keragon maps them into EHRs, CRMs, scheduling, messaging, and operations tools.

Read Keragon guide