Bridges
Manage bridge-backed account types, connections, and login sessions
Get bridge capabilities
ModelsExpand Collapse
class Bridge: …Available bridge that can connect or reconnect chat accounts.
Available bridge that can connect or reconnect chat accounts.
Connected accounts for this bridge. Uses the same Account schema as GET /v1/accounts.
Connected accounts for this bridge. Uses the same Account schema as GET /v1/accounts.
Chat account added to Beeper. Use this to route account-scoped actions. Examples include matrix for Beeper/Matrix, discordgo for a cloud bridge, slackgo.TEAM-USER for workspace-scoped cloud bridges, and local-whatsapp_ba_… for local bridges.
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
Bridge identifier. Beeper Cloud accounts often use the network type (for example matrix or discordgo); on-device accounts use a local bridge ID (for example local-whatsapp). Available in Beeper Desktop v4.2.785+.
status: Literal["connected", "connecting", "backfilling", 5 more]Current connection status for this account.
Current connection status for this account.
User the account belongs to.
User the account belongs to.
True if Beeper cannot initiate messages to this user (e.g., blocked, network restriction, or no DM path). The user may still message you.
Display name as shown in clients (e.g., ‘Alice Example’). May include emojis.
Avatar image URL if available. This may be a remote URL, media URL, data URL, or local file URL depending on the source. May be temporary or available only on this device; download promptly if durable access is needed.
Runtime chat/message capabilities for this connected account, when available.
Bridge login ID for this account, when known. One bridge login can contain multiple chat accounts.
provider: Literal["cloud", "self-hosted", "local", "platform-sdk"]Where accounts for this bridge run: on this device or in Beeper Cloud.
Where accounts for this bridge run: on this device or in Beeper Cloud.
status: Literal["available", "connected", "limit_reached", 2 more]Whether this bridge can currently be used to connect new accounts.
Whether this bridge can currently be used to connect new accounts.
Whether this bridge can have multiple active accounts for the same network.
class GroupTypeCapabilities: …Group creation capabilities for one group type.
Group creation capabilities for one group type.
class LoginSession: …
account: Optional[Account]A chat account added to Beeper.
A chat account added to Beeper.
Chat account added to Beeper. Use this to route account-scoped actions. Examples include matrix for Beeper/Matrix, discordgo for a cloud bridge, slackgo.TEAM-USER for workspace-scoped cloud bridges, and local-whatsapp_ba_… for local bridges.
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
Bridge identifier. Beeper Cloud accounts often use the network type (for example matrix or discordgo); on-device accounts use a local bridge ID (for example local-whatsapp). Available in Beeper Desktop v4.2.785+.
status: Literal["connected", "connecting", "backfilling", 5 more]Current connection status for this account.
Current connection status for this account.
User the account belongs to.
User the account belongs to.
True if Beeper cannot initiate messages to this user (e.g., blocked, network restriction, or no DM path). The user may still message you.
Display name as shown in clients (e.g., ‘Alice Example’). May include emojis.
Avatar image URL if available. This may be a remote URL, media URL, data URL, or local file URL depending on the source. May be temporary or available only on this device; download promptly if durable access is needed.
Runtime chat/message capabilities for this connected account, when available.
Bridge login ID for this account, when known. One bridge login can contain multiple chat accounts.
current_step: Optional[CurrentStep]Step the client should show or complete next. Omitted when the session is complete, cancelled, or failed.
Step the client should show or complete next. Omitted when the session is complete, cancelled, or failed.
class CurrentStepCookies: …
class CurrentStepComplete: …
account: Optional[Account]A chat account added to Beeper.
A chat account added to Beeper.
Chat account added to Beeper. Use this to route account-scoped actions. Examples include matrix for Beeper/Matrix, discordgo for a cloud bridge, slackgo.TEAM-USER for workspace-scoped cloud bridges, and local-whatsapp_ba_… for local bridges.
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
Bridge identifier. Beeper Cloud accounts often use the network type (for example matrix or discordgo); on-device accounts use a local bridge ID (for example local-whatsapp). Available in Beeper Desktop v4.2.785+.
status: Literal["connected", "connecting", "backfilling", 5 more]Current connection status for this account.
Current connection status for this account.
User the account belongs to.
User the account belongs to.
True if Beeper cannot initiate messages to this user (e.g., blocked, network restriction, or no DM path). The user may still message you.
Display name as shown in clients (e.g., ‘Alice Example’). May include emojis.
Avatar image URL if available. This may be a remote URL, media URL, data URL, or local file URL depending on the source. May be temporary or available only on this device; download promptly if durable access is needed.
Runtime chat/message capabilities for this connected account, when available.
Bridge login ID for this account, when known. One bridge login can contain multiple chat accounts.
login: Optional[CurrentStepCompleteLogin]Signed-in identity for a bridge. One bridge login can contain multiple chat accounts.
Signed-in identity for a bridge. One bridge login can contain multiple chat accounts.
user: Optional[User]User the account belongs to.
User the account belongs to.
True if Beeper cannot initiate messages to this user (e.g., blocked, network restriction, or no DM path). The user may still message you.
Display name as shown in clients (e.g., ‘Alice Example’). May include emojis.
Avatar image URL if available. This may be a remote URL, media URL, data URL, or local file URL depending on the source. May be temporary or available only on this device; download promptly if durable access is needed.
login: Optional[Login]Signed-in identity for a bridge. One bridge login can contain multiple chat accounts.
Signed-in identity for a bridge. One bridge login can contain multiple chat accounts.
user: Optional[User]User the account belongs to.
User the account belongs to.
True if Beeper cannot initiate messages to this user (e.g., blocked, network restriction, or no DM path). The user may still message you.
Display name as shown in clients (e.g., ‘Alice Example’). May include emojis.
Avatar image URL if available. This may be a remote URL, media URL, data URL, or local file URL depending on the source. May be temporary or available only on this device; download promptly if durable access is needed.
class ProvisioningCapabilities: …Advanced network capabilities for account lookup and group creation.
Advanced network capabilities for account lookup and group creation.
class BridgeListResponse: …Available bridges and their connected accounts.
Available bridges and their connected accounts.
Connected accounts for this bridge. Uses the same Account schema as GET /v1/accounts.
Connected accounts for this bridge. Uses the same Account schema as GET /v1/accounts.
Chat account added to Beeper. Use this to route account-scoped actions. Examples include matrix for Beeper/Matrix, discordgo for a cloud bridge, slackgo.TEAM-USER for workspace-scoped cloud bridges, and local-whatsapp_ba_… for local bridges.
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
Bridge identifier. Beeper Cloud accounts often use the network type (for example matrix or discordgo); on-device accounts use a local bridge ID (for example local-whatsapp). Available in Beeper Desktop v4.2.785+.
status: Literal["connected", "connecting", "backfilling", 5 more]Current connection status for this account.
Current connection status for this account.
User the account belongs to.
User the account belongs to.
True if Beeper cannot initiate messages to this user (e.g., blocked, network restriction, or no DM path). The user may still message you.
Display name as shown in clients (e.g., ‘Alice Example’). May include emojis.
Avatar image URL if available. This may be a remote URL, media URL, data URL, or local file URL depending on the source. May be temporary or available only on this device; download promptly if durable access is needed.
Runtime chat/message capabilities for this connected account, when available.
Bridge login ID for this account, when known. One bridge login can contain multiple chat accounts.
provider: Literal["cloud", "self-hosted", "local", "platform-sdk"]Where accounts for this bridge run: on this device or in Beeper Cloud.
Where accounts for this bridge run: on this device or in Beeper Cloud.
status: Literal["available", "connected", "limit_reached", 2 more]Whether this bridge can currently be used to connect new accounts.
Whether this bridge can currently be used to connect new accounts.
Whether this bridge can have multiple active accounts for the same network.
class BridgeRetrieveResponse: …Available bridge that can connect or reconnect chat accounts.
Available bridge that can connect or reconnect chat accounts.
Connected accounts for this bridge. Uses the same Account schema as GET /v1/accounts.
Connected accounts for this bridge. Uses the same Account schema as GET /v1/accounts.
Chat account added to Beeper. Use this to route account-scoped actions. Examples include matrix for Beeper/Matrix, discordgo for a cloud bridge, slackgo.TEAM-USER for workspace-scoped cloud bridges, and local-whatsapp_ba_… for local bridges.
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
Bridge identifier. Beeper Cloud accounts often use the network type (for example matrix or discordgo); on-device accounts use a local bridge ID (for example local-whatsapp). Available in Beeper Desktop v4.2.785+.
status: Literal["connected", "connecting", "backfilling", 5 more]Current connection status for this account.
Current connection status for this account.
User the account belongs to.
User the account belongs to.
True if Beeper cannot initiate messages to this user (e.g., blocked, network restriction, or no DM path). The user may still message you.
Display name as shown in clients (e.g., ‘Alice Example’). May include emojis.
Avatar image URL if available. This may be a remote URL, media URL, data URL, or local file URL depending on the source. May be temporary or available only on this device; download promptly if durable access is needed.
Runtime chat/message capabilities for this connected account, when available.
Bridge login ID for this account, when known. One bridge login can contain multiple chat accounts.
provider: Literal["cloud", "self-hosted", "local", "platform-sdk"]Where accounts for this bridge run: on this device or in Beeper Cloud.
Where accounts for this bridge run: on this device or in Beeper Cloud.
status: Literal["available", "connected", "limit_reached", 2 more]Whether this bridge can currently be used to connect new accounts.
Whether this bridge can currently be used to connect new accounts.
Whether this bridge can have multiple active accounts for the same network.
BridgesLogin Flows
Available bridges, bridge logins, login sessions for connect and reconnect flows, and advanced network capabilities.
List login flows
BridgesConnections
BridgesLogin Sessions
Available bridges, bridge logins, login sessions for connect and reconnect flows, and advanced network capabilities.
Create bridge login session
Get bridge login session
Cancel bridge login session
BridgesLogin SessionsSteps
Available bridges, bridge logins, login sessions for connect and reconnect flows, and advanced network capabilities.