sdp_suki_token) that authorizes subsequent REST and WebSocket API calls for that provider. Critically, a Partner Token alone is not enough to call session, streaming, or content APIs. You must exchange it for a Suki Token first.
Register and Login are called from your servers and authenticated with your partner_id and Partner Token. Suki Tokens are valid for 1 hour. Call Login again with a valid Partner Token to refresh. The JWKS endpoint is public and returns Suki’s public keys so you can verify Suki-issued tokens such as the Suki Token.
Available endpoints
Register
Register a new provider or link an existing provider to your partner organization
Login
Exchange your Partner Token for a Suki Token
JWKS
Return the current JSON Web Key Set for verifying Suki-issued tokens
Related guides
Standard Provider Authentication
Learn how to authenticate standard partners using the Suki Token
Single Auth Token Authentication
Learn how to authenticate Single Auth Token partners using the Suki Token and send provider identity on every request
Bearer Partner Authentication
Learn how to authenticate Bearer partners using the Suki Token and send provider identity on Login and Register
Common use cases
Authenticate clinicians with your existing sign-in
Use your own authentication flow while Suki securely authenticates clinicians in the background. No separate Suki sign-in is required.
Refresh authentication for long-running sessions
Renew authentication before Suki Tokens expire so ambient capture, dictation, and other workflows continue without interruption.
Verify Suki Tokens in your backend
Validate Suki Tokens using the JWKS endpoint before creating sessions, processing webhooks, or authorizing API requests.
Authenticate multiple clinicians with one Partner Token
Use a shared organization-level Partner Token while identifying each clinician with
provider_id during authentication.