API CLIENTS • KEYS • PARTNERS

API keys built for real partners.

Create per‑partner clients, control PHI scope, allow safe status updates, and audit every request. Clean UX for teams. Predictable JSON for integrations.

Get started See endpoints
Scoped API keys
PHI permissions
Audit trail
Fast filters
KEY LIFECYCLE

Create. Scope. Rotate. Audit.

A clean workflow for clinics and partners—without compromising safety.

1) Create a client
One client per partner app or system. Names stay readable for audits.
2) Choose permissions
Control PHI visibility and whether status changes are allowed.
3) Rotate keys
Keys are revealed once. Regenerate any time to invalidate old keys.
4) Audit requests
Track method, path, timestamp, and outcomes for traceability.
Open API settings Talk to us
ENDPOINTS

The essentials—done right.

A small set of predictable endpoints that map to real clinic workflows.

Appointments GET
List appointments
Filter by range, doctor, and status—fast, stable results.
GET /api/appointments?from=2026-01-01&to=2026-01-31&doctorId=12
Appointments GET
Get by id
Fetch a single appointment payload with consistent fields.
GET /api/appointments/44819
Appointments POST
Create appointment
Create with a validated payload and safe overlap checks.
POST /api/appointments
Status POST
Change status
External partners can cancel only when granted permission.
POST /api/appointments/44819/status
TRUST BY DESIGN

Security defaults that teams don’t fight.

Clinic time matters. Patient privacy matters more. Qlynic keeps integrations clean with safe constraints.

Tokenized links
Manage + review links use tokens and expiry.
PHI permission gates
Expose only what a partner is allowed to see.
UTC-native scheduling
Store UTC, display clinic time, reminders stay correct.