---
title: "Register provider"
method: POST
path: "/api/v1/auth/register"
tags: ["/api/v1/auth"]
---

# Register provider

`POST /api/v1/auth/register`

Registers a new provider in Suki or links an existing provider to your partner organization. This is a one-time setup call per provider.

## Request body

- ControllersRegistrationRequest — 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.
  - `partner_token` string, required — JWT token issued by trusted authorization server. The token must include Provider Email.
  - `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.
  - `provider_name` string, required — Name of the provider.
  - `provider_org_id` string, required — Health system or organization to which the provider belongs.
  - `provider_specialty` string — **Optional** - Medical specialty of the provider. Defaults to FAMILY_MEDICINE if not provided.

## Response `201`

Resource created successfully.

## Other responses

- `400` — Bad request. The request body or parameters failed validation.
- `401` — Unauthorized. The Suki access token is missing, expired, or invalid.
- `403` — Forbidden. The authenticated user cannot access this resource.
- `404` — Not found. The session, encounter, or resource ID does not exist.
- `409` — Conflict
- `500` — Internal server error.

---

[API](https://skmtc.dev/suki/apis/suki-developer-platform.md) · [All operations](https://skmtc.dev/suki/apis/suki-developer-platform/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/suki/suki-developer-platform/revisions/5f420a18fb68/schema)