Skip to main content
These options affect how provider OAuth behaves. They are available in both hosted and custom flows unless noted otherwise.

disableAutoLogin

Supported for Facebook, Instagram via Facebook, Instagram direct OAuth, and TikTok where the provider supports it. When true, we add provider-specific flags that try to prevent silent account reuse. Use it when your users manage many accounts from the same browser. Without it, the OAuth popup can reuse the last logged-in platform account.

tiktokForceLogin

Supported only for TikTok and currently experimental. When true, bundle.social routes the user through TikTok logout before starting authorization. Use it when TikTok keeps reusing the wrong active account even with disableAutoLogin.
This signs the user out of their active TikTok browser session. Use it only when choosing a fresh account is more important than preserving that session.

forceBrowserOAuth

Supported for Instagram direct OAuth. When true, direct Instagram connections on phones try to open browser OAuth instead of the Instagram app flow. This helps when the Instagram iOS app deep-link flow gets stuck or returns users without completing authorization.
This is separate from disableAutoLogin. forceBrowserOAuth changes which Instagram OAuth surface we try to use. disableAutoLogin asks the provider to avoid silently reusing the current logged-in session where supported.

withBusinessScope

Supported for Facebook and Instagram via Facebook. When true, OAuth uses the broader Meta scope set, including business_management, ads_management, and ads_read among the permissions we request. When false, OAuth uses the standard scope set.
Some Facebook Pages and Instagram accounts only appear in the picker when the connection was made with business scope. If something is missing from the list, reconnect using the other method (withBusinessScope flipped) before assuming the picker is wrong.

Instagram Connection Method

Supported for type: "INSTAGRAM" in custom UI and hosted portal links. Use Facebook Login when you need Facebook-backed Instagram features such as Page-connected account selection, comments, insights, location search, or Instagram audio search for Reels. Use direct Instagram OAuth when you explicitly want the direct Instagram OAuth path and do not need Facebook-backed channel selection.

serverUrl

Supported for Mastodon and Bluesky in the custom UI flow.