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

# InvalidPartnerDetails During Sign-In or Registration

> Fix Headless Web SDK InvalidPartnerDetails when partnerId or partnerToken is wrong

Headless Web SDK returns **`InvalidPartnerDetails`** during registration, sign-in, or token updates when `partnerId` or `partnerToken` does not match your partner account.

Pass:

* **`partnerId`** (required) - Partner ID from [Partner onboarding](/documentation/get-started/partner-onboarding)
* **`partnerToken`** (required) - Partner Token (JWT) from your identity provider

Optional auth fields include `providerId`, `autoRegister`, and `loginOnMount`. Call `updatePartnerToken()` when your host app issues a new Partner Token.

| When | Meaning | Check |
| :- | :- | :- |
| Registration | Incorrect details during user registration | `partnerId`, secret key, and other registration details |
| Sign-in | Incorrect details during sign-in | `partnerId`, `partnerToken`, and related credentials |

<Note>
  Web SDK uses a different error shape (`code`, `details.name`, `details.reason`) and does not list `InvalidPartnerDetails` by name. Wrong Form filling credentials can leave a blank UI with no SDK error code.
</Note>

## Common causes

* `partnerId` is not the Partner ID from onboarding.
* `partnerToken` is truncated, expired, malformed, or issued for a different environment than the SDK `environment` setting.
* Registration details (including secret key, when your flow uses one) do not match the partner record.
* Staging credentials with `environment: "production"`, or the reverse.

## Fix

<Steps>
  <Step title="Use Credentials for One Environment">
    Use the `partnerId` and Partner Token for the same staging or production environment you set on the SDK.
  </Step>

  <Step title="Pass partnerId and partnerToken">
    Initialize the Headless auth hook with those SDK field names. Do not paste REST names (`partner_id` / `partner_token`) into SDK options.
  </Step>

  <Step title="Match Environment and CSP">
    Set `environment` to `staging` or `production` to match those credentials. For hosted iframe SDKs, allow `https://sdk.suki-stage.com` (staging) or `https://sdk.suki.ai` (production) in CSP `frame-src`. See [Wrong staging vs production endpoints](/documentation/troubleshooting/wrong-environment-endpoints).
  </Step>

  <Step title="Retry Sign-In or Registration">
    Fix the payload, then try again. If registration still fails, recheck Partner ID, secret key, and other onboarding details.
  </Step>
</Steps>

<Tip>
  If the Partner Token itself fails validation (expired `exp`, missing user identifier, JWKS unreachable), follow [401 Unauthorized or invalid Partner Token](/documentation/troubleshooting/invalid-partner-token-401).
</Tip>

## Form filling blank UI

Form filling does not open until `SukiAuthManager` sign-in succeeds with a valid `partnerId` and `partnerToken`. Wrong or expired credentials can leave a blank interface with **no** SDK error code. See [Form filling SDK error handling](/form-filling-sdk/guides/error-handling).

## Next steps

<Icon icon="file-lines" iconType="solid" /> **[Headless Web SDK error handling](/headless-web-sdk/guides/error-handling)** - AuthError codes including `InvalidPartnerDetails`

<Icon icon="file-lines" iconType="solid" /> **[Partner authentication](/documentation/how-to/partner-authentication)** - Partner Token requirements and claim checks

<Icon icon="file-lines" iconType="solid" /> **[401 Unauthorized or invalid Partner Token](/documentation/troubleshooting/invalid-partner-token-401)** - JWT and `sdp_suki_token` failures on Partner APIs

<Icon icon="file-lines" iconType="solid" /> **[Wrong staging vs production endpoints](/documentation/troubleshooting/wrong-environment-endpoints)** - Match credentials, hosts, and `environment`

<Icon icon="file-lines" iconType="solid" /> **[Provider register or login fails](/documentation/troubleshooting/provider-register-login-fails)** - Register and Login API failures