These options affect how provider OAuth behaves. They are available in both hosted and custom flows unless noted otherwise.Documentation Index
Fetch the complete documentation index at: https://info.bundle.social/llms.txt
Use this file to discover all available pages before exploring further.
disableAutoLogin
Supported for Facebook, Instagram via Facebook, Instagram direct OAuth, and TikTok where the provider supports it. Whentrue, 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.
forceBrowserOAuth
Supported for Instagram direct OAuth. Whentrue, 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. Whentrue, 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.
Instagram Connection Method
Supported only fortype: "INSTAGRAM" in the custom UI flow.
| Value | Meaning | Channel selection |
|---|---|---|
FACEBOOK | Instagram through Facebook Login. This is the default path when omitted. | Required. Use set-channel. |
INSTAGRAM | Direct Instagram OAuth. | Not supported. The account is selected directly during OAuth. |
serverUrl
Supported for Mastodon and Bluesky in the custom UI flow.| Platform | Required? | Example |
|---|---|---|
| Mastodon | Yes | https://mastodon.social |
| Bluesky | No, but supported | https://bsky.social |