Theraswift Developers

Connect your EMR to Aanu.

Send prescriptions from your existing clinical system into the Theraswift network. Aanu coordinates medication fulfilment through TSOS and exposes progress back to your software.

Create sandbox Quickstart API reference

REST API

Simple JSON integration for EMRs, hospitals and digital-health products.

Aanu + TSOS

Your prescription becomes an executable medication mission, not another disconnected record.

Provider isolation

Hospital-scoped API keys and records keep each integration isolated.

Quickstart

One request starts the workflow.

Authenticate with your private provider key. Use a stable external_id so retries are idempotent. The response includes the exact medication request IDs created in TSOS.

curl -X POST https://theraswift.co/api/v1/prescriptions \
  -H "Authorization: Bearer tsh_test_..." \
  -H "Content-Type: application/json" \
  -d '{
    "external_id": "RX-2026-000184",
    "patient_phone": "2348012345678",
    "patient_name": "Example Patient",
    "doctor_name": "Dr Example",
    "medications": [{ "name": "Amlodipine", "dosage": "5 mg", "quantity": 30 }]
  }'

API reference

POST/api/v1/prescriptionsCreate an idempotent prescription and medication missions.

GET/api/v1/prescriptions/{id}Read a hospital-scoped prescription.

GET/api/v1/missions/{prescription_id}Track exact medication requests and TSOS mission progress.

Integration roadmap

REST is live first. Signed webhooks and FHIR adapters are being layered over the same TSOS primitives so integrations do not create parallel care workflows.

Production credentials are private and organization-scoped. Never expose a tsh_ key in browser code, public repositories or documentation.