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

# Partner Onboarding

> Complete onboarding process to become a Suki Developer Platform partner

Before you can use Suki's APIs and SDKs, you must complete a **one-time** onboarding process. This guide walks you through getting started as a Suki partner.

Once onboarded, you'll receive a <Tooltip tip="A unique identifier assigned by Suki during onboarding that links an application to its configuration in the Suki Developer Platform." cta="View in Glossary" href="/Glossary/p">Partner ID</Tooltip> (`partner_id`) that identifies your organization. Then register users and start integrating Suki's AI capabilities into your application.

## Key concepts

<Card>
  <CardGroup cols={3}>
    <Card title="Partner" icon="handshake">
      An organization that integrates with Suki to use our services. A partner can contain multiple organizations.
    </Card>

    <Card title="Organization" icon="building">
      A group of users within a partner, such as a hospital or a clinic.
    </Card>

    <Card title="Provider" icon="user">
      A user within an organization, such as a doctor or a nurse, who uses Suki's services.
    </Card>
  </CardGroup>
</Card>

## Partner ID

A Partner ID is a unique identifier that Suki assigns to your organization during onboarding. You'll use this ID in all API calls and SDK initializations.

**What it's used for:**

* Links your application to its configuration in the Suki Developer Platform
* Determines which authentication endpoint to use for token validation
* Maps your user roles to Suki's capabilities

<Tip>
  You'll receive your Partner ID after completing onboarding. Include it in all API requests and when initializing SDKs.
</Tip>

## How authentication works

Suki uses your existing identity provider to authenticate users. You don't need to create separate user accounts in Suki.

**The authentication flow:**

1. A provider signs in to your application using your identity provider (like Okta, Azure AD, or Auth0)
2. Your identity provider issues a token for that user
3. You send this token to Suki in your API requests
4. Suki verifies the token to confirm the user's identity and grant access

<Tip>
  **Identity Provider**: A service that authenticates users and issues identity tokens. Examples include Okta, Auth0, and Azure AD. You'll use your existing identity provider (no need to set up a new one for Suki).
</Tip>

## Onboarding process

Follow these steps to get started:

### Onboarding flow

```mermaid actions={false} theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
flowchart TD
    A([Start]) --> B[Contact Suki Customer Success]
    B --> C[Share business details, use case,<br/>contact person, and authentication method]
    C --> D[Suki reviews and provisions your account]
    D --> E[You receive your Partner ID]
    E --> F[Register users and call APIs<br/>with identity provider tokens]
    F --> G([Integrate and go live])

    classDef stepStyle fill:#FFE148,stroke:#D4A017,stroke-width:2px,color:#000000
    classDef milestoneStyle fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#000000
    classDef doneStyle fill:#FFD700,stroke:#D4A017,stroke-width:3px,color:#000000

    class B,C,D stepStyle
    class E milestoneStyle
    class F,G doneStyle
```

<Steps>
  <Step title="Contact Suki" icon="user-plus">
    Reach out to the Suki Customer Success team to begin onboarding. Have this information ready:

    * **Business details**: Official business name, email address, and phone number
    * **Use case**: Description of your business and how you plan to use Suki
    * **Contact person**: Name of the person managing the integration
    * **Authentication method**: How you'll authenticate users (see options below)

    <Callout icon="lock-open">
      **Supported Authentication Methods**

      Suki supports these authentication methods. You'll use your existing identity provider:

      * **Stored Secret** - Share your public key with Suki, stored securely in our database
      * **JWKS URL** - Host your public keys at a public endpoint; Suki fetches them automatically
      * **Okta** - Use Okta as your identity provider; Suki gets keys from your Okta issuer URL
      * **JWT Assertion** - Share your public key as a signed JWT following RFC 7523

      Learn more in the [Partner authentication](/documentation/partner-authentication) guide.
    </Callout>
  </Step>

  <Step title="Suki reviews your information" icon="check-circle">
    The Suki team reviews your information and sets up your account. This typically takes a few business days.
  </Step>

  <Step title="Receive your Partner ID" icon="key">
    Once approved, you'll receive your unique Partner ID. Use this ID in all API calls and SDK initializations to identify your organization.
  </Step>
</Steps>

## Getting support

Need help? Reach out through any of these channels:

<AccordionGroup>
  <Accordion title="Contact the Suki team">
    Reach out to your Suki Customer Success or Program Manager directly.
  </Accordion>

  <Accordion title="Slack channel">
    Use the dedicated Slack channel created for your integration team.
  </Accordion>

  <Accordion title="Support ticket">
    Create a [Support ticket](https://forms.suki.ai/SukiSupport/form/SukiSDKSupport/formperma/T3z7hYJ7Ph-J7JrWSN08QJn32BYjarkxqm8Lm8XFPow) for technical issues or questions.
  </Accordion>
</AccordionGroup>