> ## 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

> Register providers, exchange Partner Tokens for Suki Tokens, and retrieve JWKS public keys for E/M Coding API authentication

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 E/M Coding REST API calls for that provider. Critically, a Partner Token alone is not enough to start E/M coding sessions or retrieve codes. 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

> [card] [POST Register](https://developer.suki.ai/em-coding-api-reference/authentication/register.md)
>
> Purpose: Register a new provider or link an existing provider to your partner organization.

> [card] [POST Login](https://developer.suki.ai/em-coding-api-reference/authentication/login.md)
>
> Purpose: Exchange your Partner Token for a Suki Token.

> [card] [GET JWKS](https://developer.suki.ai/em-coding-api-reference/authentication/jwks.md)
>
> Purpose: Return the current JSON Web Key Set for verifying Suki-issued tokens.

## Related guides

> [card] [Standard Provider Authentication](https://developer.suki.ai/api-reference/provider-authentication.md)
>
> Learn how to authenticate standard providers using the Suki Token.

> [card] [Single Auth Token Authentication](https://developer.suki.ai/api-reference/single-auth-token-authentication.md)
>
> Learn how to authenticate Single Auth Token partners using the Suki Token and send provider identity on every request.

> [card] [Bearer Partner Authentication](https://developer.suki.ai/api-reference/bearer-partner-authentication.md)
>
> Learn how to authenticate Bearer partners using the Suki Token and send provider identity on Login and Register.

## Common use cases

> [card] 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] Refresh authentication for long-running sessions
>
> Renew authentication before Suki Tokens expire so E/M Coding capture and retrieval continue without interruption.

> [card] Verify Suki Tokens in your backend
>
> Validate Suki Tokens using the JWKS endpoint before creating E/M Coding sessions, processing webhooks, or authorizing API requests.

> [card] Authenticate multiple clinicians with one Partner Token
>
> Use a shared organization-level Partner Token while identifying each clinician with `provider_id` during authentication.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.