Skip to main content
Not a Suki partner yet?
  • Onboarding is a one-time process. You cannot self-provision credentials.
  • To get started, contact the Suki Partnerships team. They configure your authentication, environments, and webhooks, then issue your Partner ID that you will use for API and SDK authentication.
Onboarding is the process of registering your organization on the Suki Developer Platform. During onboarding, Suki creates your partner account, configures your integration, and provisions the credentials and settings required to use Suki APIs and SDKs. You cannot self-provision these credentials. The Suki Partnerships team works with you throughout the onboarding process to configure your account. During onboarding, you provide:
  • Authentication method: How your identity provider authenticates users and issues a Partner Token (JWT). Suki uses this token to verify users before they access Suki APIs or SDKs. Suki recommends OAuth 2.0 or OpenID Connect with a public JWKS URL. For more information, see Partner authentication.
  • Environments: The environments you plan to use, such as staging and production, so Suki can provision the appropriate access, credentials, and base URLs.
  • Webhook configuration (optional): The HTTPS callback URL that Suki should use to send webhook notifications to your backend. If you plan to use webhooks, provide this during onboarding. For more information, see Configure webhooks.
After onboarding is complete, Suki issues a (partner_id) that identifies your integration. Refer to the sections below for the full checklist of what you provide, what you receive, and the step-by-step onboarding flow.

​
What you provide and what you receive

When you contact Suki, provide the following information so the partnership team can begin onboarding your organization. The exact fields vary by product (API, Web SDK, or Mobile SDK), but most partners provide the following information:
Onboarding does not give you a long-lived API key. Instead, your users sign in through your identity provider, and you pass the resulting Partner Token (JWT) to Suki. Suki verifies the token and returns SDK access or an sdp_suki_token for Partner APIs. To learn how to authenticate users with Suki, refer to the Partner authentication guide.

​
Key concepts to understand before onboarding

As a partner, you must understand the following key concepts and their roles and relationships in the Suki Developer Platform.

​
How authentication works in the Suki Developer Platform

Suki does not host your login screens or store end-user passwords. Your identity provider authenticates each user and issues a JWT, known as the Partner Token. Suki verifies that token with the public keys you registered during onboarding, then grants access. If you cannot host a JWKS URL, Suki supports other public-key methods during onboarding. To learn about the supported methods and the recommended setup, refer to the Partner authentication guide.

​
How the onboarding process works

The onboarding and verification process typically takes a few business days after you submit all required information and Suki verifies your details. While you wait, review the Partner authentication and Integration decision guide to determine the API or SDK integration path you’ll use after your account is approved. Here is a high-level overview of the onboarding process:

​
Detailed steps of the onboarding process

Contact Suki

Reach out through Contact Partnership team (or your Suki account contact). Have the checklist ready: business details, use case, recommended auth (OAuth JWT + JWKS URL), user identifier field, host URLs if you embed an SDK, and webhook URL if you want notifications from day one.

Suki Reviews and Provisions

Suki registers your public-key method and other settings on the partner record, then provisions staging or production access as agreed. Missing JWKS, identifier, or allowlist details are the most common cause of delay, so send them complete the first time.

Receive Your Partner ID

On approval, you receive your Partner ID. Confirm that your registered JWKS URL, identifier field, host allowlist, and webhook URL (if any) match what your code will use, then move on to authentication setup.

​
Getting support

Reach out to your Suki Customer Success or Program Manager, or use Contact Partnership Team.
Use the dedicated Slack channel created for your integration team after onboarding starts.
Create a Support ticket for technical issues or questions.

​
Next steps

After you have a Partner ID and confirmed settings: Partner authentication - Register OAuth JWT + JWKS (recommended) and understand Partner Token verification. Integration decision guide - Choose Web SDK, Headless Web SDK, Mobile SDK, Dictation SDK, or Partner APIs. Ambient API quickstart - First ambient session on staging with paste-ready scripts. Form filling API quickstart - First Form filling session on staging. Configure webhooks - Callback URL and secret if you deferred webhooks during onboarding.
Last modified on July 24, 2026