API directory · Partner ambient documentation API
Suki API
The most completely documented developer portal among the clinician-facing scribe vendors: public REST session API, WebSocket audio streaming, webhooks and a staging quickstart.
Short answer
What does the Suki API give a developer?
The most completely documented developer portal among the clinician-facing scribe vendors: public REST session API, WebSocket audio streaming, webhooks and a staging quickstart.
Base URL: Environment-specific (staging documented in the quickstart); production base URL issued to partners
Auth: Login endpoint returns a JWT (suki_token) used as the bearer credential on subsequent calls
Cite as: Suki API listing, Compare Healthcare API, last reviewed 2026-09-01.
Endpoints
Copied from the vendor's own reference. Where a path is described rather than published, the description is what the vendor states.
| Method | Endpoint | Mode | Purpose |
|---|---|---|---|
| POST | /login | Auth | Authenticate a provider and obtain an access token. |
| POST | Create ambient session | Session | Open an encounter session; accepts emr_encounter_id and returns a composition_id used as the note id. |
| WS | Audio streaming socket | Streaming | Stream raw PCM audio for the open session. |
| POST | End session | Session | Close the session and trigger note generation. |
| GET | Note / composition | Session | Poll for the generated structured clinical note. |
| POST | Webhooks (HMAC-signed) | Webhook | Receive note-ready and status events instead of polling. |
Published rate limits
Numbers the vendor states publicly. Anything unpublished should be made contractual before you plan capacity.
| Concurrency / sessions per minute | Not publicly documented |
|---|
Published pricing
List prices as published on the vendor's own pricing page at the verification date. Follow the source link before you quote these to anyone.
| Published price | Not publicly disclosed by the vendor |
|---|---|
| Third-party estimate | ~$250 per user per month (ITQlick estimate — not vendor-confirmed, do not plan against it) |
Data handling and compliance
The three answers a health-system security review will ask you for, as published.
| BAA | HIPAA-aware handling documented for developers; BAA via the commercial agreement |
|---|---|
| Retention | Per-session audio and data retention schedule published in the developer security FAQ |
| Training on PHI | Not publicly documented |
How to integrate the Suki API
An ordered path based on the public documentation, written for an engineering team scoping the work.
- 01
Read the quickstart
Walk the staging quickstart end to end on paper first: authenticate, create session, stream audio, end session, retrieve note.
- 02
Request partner credentials
Open the partnership conversation in parallel with your spike — the gate here is commercial, not technical.
- 03
Implement the token flow
Call the login endpoint, store the JWT server-side, and never ship it to a browser client.
- 04
Stream raw PCM
Match the documented wire format and message order exactly; audio format mismatches are the most common first failure.
- 05
Switch polling to webhooks
Verify the HMAC signature on every webhook before trusting a note-ready event.
- 06
Bind sessions to encounters
Pass emr_encounter_id at session creation so notes reconcile to the chart without a fuzzy match later.
What the documentation does not warn you about
The judgement an endpoint list cannot give you.
Suki documents the platform properly but does not publish rate limits or prices, so you can design the integration precisely and still cannot model its unit economics until you are in a commercial conversation.
Primary sources for this listing
Every fact above traces to one of these pages. If one has changed, tell us and the listing is re-verified.
- Developer portal https://developer.suki.ai/
- API reference overview https://developer.suki.ai/api-reference/overview
- Quickstart https://developer.suki.ai/api-reference/quickstart
- Security & best practices https://developer.suki.ai/api-reference/security-best-practices
- EHR integrations https://www.suki.ai/ehr-integrations/
Evidence & sources
Standards the integration steps above assume. Vendor-specific evidence is the primary source list on this page.
U.S. Department of Health & Human Services · Regulation · Tier A — primary documentation
Supports: The contractual clauses a documentation vendor's BAA must contain.
U.S. Department of Health & Human Services · Regulation · Tier A — primary documentation
Supports: Administrative, physical and technical safeguards a vendor handling recorded encounter audio must implement.
HL7 International · Standard · Tier A — primary documentation
Supports: Resource definitions (DocumentReference, Composition, Encounter, Condition, MedicationRequest) that clinical documentation output must map onto.
Source tiers are defined on the methodology page. Outbound links are unaffiliated and carry no commercial relationship.
Frequently asked questions
- Does Suki have a public API?
- The most completely documented developer portal among the clinician-facing scribe vendors: public REST session API, WebSocket audio streaming, webhooks and a staging quickstart.
- How do you authenticate with the Suki API?
- Login endpoint returns a JWT (suki_token) used as the bearer credential on subsequent calls
- What are the Suki API rate limits?
- Concurrency / sessions per minute: Not publicly documented
- How much does the Suki API cost?
- Published price: Not publicly disclosed by the vendor. Third-party estimate: ~$250 per user per month (ITQlick estimate — not vendor-confirmed, do not plan against it)
- Can you evaluate Suki without a sales conversation?
- Documentation and a staging quickstart are public; usable credentials come through the partner programme