Skip to main content
POST
Register provider
Use this endpoint to register a new healthcare in the Suki platform or to link an existing provider to a new -organization relationship. This is a one-time setup call for each provider within an organization.

Registration scenarios

This endpoint handles three different scenarios depending on the user’s status in the Suki system.

Code examples

Body

application/json

Provider registration details and partner credentials from onboarding.

partner_id
string
required

Unique identifier for the partner. This will be shared securely by Suki to the partner through a separate partner registration process.

Example:

"your-partner-id"

partner_token
string
required

JWT token issued by trusted authorization server. The token must include Provider Email.

Example:

"eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9..."

provider_name
string
required

Name of the provider.

Example:

"Dr. John Smith"

provider_org_id
string
required

Health system or organization to which the provider belongs.

Example:

"org-123"

provider_id
string

Optional for standard partners.

Required for:

  • Bearer authentication. Send provider_id so Suki can identify the provider during Login or Register.
  • Single Auth Token authentication. Send provider_id so Suki can identify the clinician during Login or Register.
Example:

"provider-123"

provider_specialty
string

Optional - Medical specialty of the provider. Defaults to FAMILY_MEDICINE if not provided.

Example:

"CARDIOLOGY"

Response

Last modified on July 23, 2026