Skip to main content
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
  • 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.
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.

โ€‹
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

1

Use Credentials for One Environment

Use the partnerId and Partner Token for the same staging or production environment you set on the SDK.
2

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

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

Retry Sign-In or Registration

Fix the payload, then try again. If registration still fails, recheck Partner ID, secret key, and other onboarding details.
If the Partner Token itself fails validation (expired exp, missing user identifier, JWKS unreachable), follow 401 Unauthorized or invalid Partner Token.

โ€‹
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.

โ€‹
Next steps

Headless Web SDK error handling - AuthError codes including InvalidPartnerDetails Partner authentication - Partner Token requirements and claim checks 401 Unauthorized or invalid Partner Token - JWT and sdp_suki_token failures on Partner APIs Wrong staging vs production endpoints - Match credentials, hosts, and environment Provider register or login fails - Register and Login API failures
Last modified on September 29, 2026