> ## Documentation Index
> Fetch the complete documentation index at: https://developer.suki.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Authentication APIs

> Learn how to register providers, obtain tokens, and retrieve JSON Web Key Set (JWKS) material for the Suki platform

The Authentication APIs enable partners to register healthcare providers with Suki and exchange a Partner Token for a Suki access token. Providers typically sign in to your application through your identity provider. Your identity provider issues a Partner Token (JWT), and your servers send that token to Suki on Register and Login. Suki does not store provider passwords or host provider sign-in screens.

Register is a one-time call that creates a provider in Suki or links an existing provider to your partner organization. Login returns a Suki Token (`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

<Columns cols={3}>
  <Card title="Register" href="/api-reference/authentication/register" arrow={true} icon="code">
    Register a new provider or link an existing provider to your partner organization
  </Card>

  <Card title="Login" href="/api-reference/authentication/login" arrow={true} icon="code">
    Exchange your Partner Token for a Suki Token
  </Card>

  <Card title="JWKS" href="/api-reference/authentication/jwks" arrow={true} icon="code">
    Return the current JSON Web Key Set for verifying Suki-issued tokens
  </Card>
</Columns>

## Related guides

<Columns cols={2}>
  <Card title="Standard Provider Authentication" href="/api-reference/provider-authentication" icon="book" cta="Learn more">
    Learn how to authenticate standard partners using the Suki Token
  </Card>

  <Card title="Single Auth Token Authentication" href="/api-reference/single-auth-token-authentication" icon="book" cta="Learn more">
    Learn how to authenticate Single Auth Token partners using the Suki Token and send provider identity on every request
  </Card>

  <Card title="Bearer Partner Authentication" href="/api-reference/bearer-partner-authentication" icon="book" cta="Learn more">
    Learn how to authenticate Bearer partners using the Suki Token and send provider identity on Login and Register
  </Card>
</Columns>

## Common use cases

<Columns cols={2}>
  <Card title="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.
  </Card>

  <Card title="Refresh authentication for long-running sessions">
    Renew authentication before Suki Tokens expire so ambient capture, dictation, and other workflows continue without interruption.
  </Card>

  <Card title="Verify Suki Tokens in your backend">
    Validate Suki Tokens using the JWKS endpoint before creating sessions, processing webhooks, or authorizing API requests.
  </Card>

  <Card title="Authenticate multiple clinicians with one Partner Token">
    Use a shared organization-level Partner Token while identifying each clinician with `provider_id` during authentication.
  </Card>
</Columns>