Bridges
Manage available bridges, connect or reconnect chat accounts
List available bridges
Get bridge
Get bridge capabilities
ModelsExpand Collapse
Bridge { id, accounts, activeAccountCount, 7 more } 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: "connected" | "connecting" | "backfilling" | 5 moreCurrent 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.
capabilities?: Capabilities { allowed_reactions, archive, custom_emoji_reactions, 24 more } Runtime bridgev2 room feature capabilities for this connected account, when available.
Runtime bridgev2 room feature capabilities for this connected account, when available.
Allowed Unicode reactions. Omitted means all emoji reactions are allowed.
delete?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
disappearing_timer?: DisappearingTimer { omit_empty_timer, timers, types } Disappearing-message timer capabilities.
Disappearing-message timer capabilities.
edit?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
file?: Record<string, File>Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or bridgev2 pseudo-msgtype.
Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or bridgev2 pseudo-msgtype.
formatting?: Record<string, -2 | -1 | 0 | 2 more>Supported rich-text formatting features keyed by bridgev2 feature name. Omitted means no formatting support is advertised.
Supported rich-text formatting features keyed by bridgev2 feature name. Omitted means no formatting support is advertised.
location_message?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
member_actions?: MemberActions { ban, invite, kick, 2 more } Participant management capabilities.
Participant management capabilities.
ban?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
invite?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
kick?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
message_request?: MessageRequest { accept_with_button, accept_with_message } Message request capabilities.
Message request capabilities.
poll?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
reaction?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
reply?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
state?: State { com.beeper.disappearing_timer, m.room.avatar, m.room.name, m.room.topic } Room state update capabilities keyed by Matrix state event type.
Room state update capabilities keyed by Matrix state event type.
provider: "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: "available" | "connected" | "limit_reached" | 2 moreWhether 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.
BridgeLogin { bridgeID, loginID, removeScopes, 4 more } 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 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.
CookieField { id, name, pattern, 3 more }
sources?: Array<Cookie { name, type, cookieDomain } | RequestHeader { name, type, requestURLRegex } | LocalStorage { name, type } | Special { name, type } >Browser sources to inspect for this field, matching the Desktop browser flow.
Browser sources to inspect for this field, matching the Desktop browser flow.
GroupTypeCapabilities { type_description, avatar, disappear, 5 more } Group creation capabilities for one group type.
Group creation capabilities for one group type.
LoginSession { bridgeID, loginSessionID, status, 6 more }
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: "connected" | "connecting" | "backfilling" | 5 moreCurrent 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.
capabilities?: Capabilities { allowed_reactions, archive, custom_emoji_reactions, 24 more } Runtime bridgev2 room feature capabilities for this connected account, when available.
Runtime bridgev2 room feature capabilities for this connected account, when available.
Allowed Unicode reactions. Omitted means all emoji reactions are allowed.
delete?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
disappearing_timer?: DisappearingTimer { omit_empty_timer, timers, types } Disappearing-message timer capabilities.
Disappearing-message timer capabilities.
edit?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
file?: Record<string, File>Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or bridgev2 pseudo-msgtype.
Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or bridgev2 pseudo-msgtype.
formatting?: Record<string, -2 | -1 | 0 | 2 more>Supported rich-text formatting features keyed by bridgev2 feature name. Omitted means no formatting support is advertised.
Supported rich-text formatting features keyed by bridgev2 feature name. Omitted means no formatting support is advertised.
location_message?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
member_actions?: MemberActions { ban, invite, kick, 2 more } Participant management capabilities.
Participant management capabilities.
ban?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
invite?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
kick?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
message_request?: MessageRequest { accept_with_button, accept_with_message } Message request capabilities.
Message request capabilities.
poll?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
reaction?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
reply?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
state?: State { com.beeper.disappearing_timer, m.room.avatar, m.room.name, m.room.topic } Room state update capabilities keyed by Matrix state event type.
Room state update capabilities keyed by Matrix state event type.
currentStep?: UserInput { fields, stepID, type, 2 more } | Cookies { fields, stepID, type, 5 more } | DisplayAndWait { display, stepID, type, instructions } | Complete { type, account, instructions, 2 more } 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.
Cookies { fields, stepID, type, 5 more }
sources?: Array<Cookie { name, type, cookieDomain } | RequestHeader { name, type, requestURLRegex } | LocalStorage { name, type } | Special { name, type } >Browser sources to inspect for this field, matching the Desktop browser flow.
Browser sources to inspect for this field, matching the Desktop browser flow.
DisplayAndWait { display, stepID, type, instructions }
Complete { type, account, instructions, 2 more }
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: "connected" | "connecting" | "backfilling" | 5 moreCurrent 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.
capabilities?: Capabilities { allowed_reactions, archive, custom_emoji_reactions, 24 more } Runtime bridgev2 room feature capabilities for this connected account, when available.
Runtime bridgev2 room feature capabilities for this connected account, when available.
Allowed Unicode reactions. Omitted means all emoji reactions are allowed.
delete?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
disappearing_timer?: DisappearingTimer { omit_empty_timer, timers, types } Disappearing-message timer capabilities.
Disappearing-message timer capabilities.
edit?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
file?: Record<string, File>Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or bridgev2 pseudo-msgtype.
Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or bridgev2 pseudo-msgtype.
formatting?: Record<string, -2 | -1 | 0 | 2 more>Supported rich-text formatting features keyed by bridgev2 feature name. Omitted means no formatting support is advertised.
Supported rich-text formatting features keyed by bridgev2 feature name. Omitted means no formatting support is advertised.
location_message?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
member_actions?: MemberActions { ban, invite, kick, 2 more } Participant management capabilities.
Participant management capabilities.
ban?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
invite?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
kick?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
message_request?: MessageRequest { accept_with_button, accept_with_message } Message request capabilities.
Message request capabilities.
poll?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
reaction?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
reply?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
state?: State { com.beeper.disappearing_timer, m.room.avatar, m.room.name, m.room.topic } Room state update capabilities keyed by Matrix state event type.
Room state update capabilities keyed by Matrix state event type.
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 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.
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 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.
ProvisioningCapabilities { group_creation, resolve_identifier, image_pack_import } Advanced network capabilities for account lookup and group creation.
Advanced network capabilities for account lookup and group creation.
group_creation: Record<string, GroupTypeCapabilities { type_description, avatar, disappear, 5 more } >
BridgeListResponse { items } 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: "connected" | "connecting" | "backfilling" | 5 moreCurrent 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.
capabilities?: Capabilities { allowed_reactions, archive, custom_emoji_reactions, 24 more } Runtime bridgev2 room feature capabilities for this connected account, when available.
Runtime bridgev2 room feature capabilities for this connected account, when available.
Allowed Unicode reactions. Omitted means all emoji reactions are allowed.
delete?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
disappearing_timer?: DisappearingTimer { omit_empty_timer, timers, types } Disappearing-message timer capabilities.
Disappearing-message timer capabilities.
edit?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
file?: Record<string, File>Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or bridgev2 pseudo-msgtype.
Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or bridgev2 pseudo-msgtype.
formatting?: Record<string, -2 | -1 | 0 | 2 more>Supported rich-text formatting features keyed by bridgev2 feature name. Omitted means no formatting support is advertised.
Supported rich-text formatting features keyed by bridgev2 feature name. Omitted means no formatting support is advertised.
location_message?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
member_actions?: MemberActions { ban, invite, kick, 2 more } Participant management capabilities.
Participant management capabilities.
ban?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
invite?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
kick?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
message_request?: MessageRequest { accept_with_button, accept_with_message } Message request capabilities.
Message request capabilities.
poll?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
reaction?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
reply?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
state?: State { com.beeper.disappearing_timer, m.room.avatar, m.room.name, m.room.topic } Room state update capabilities keyed by Matrix state event type.
Room state update capabilities keyed by Matrix state event type.
provider: "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: "available" | "connected" | "limit_reached" | 2 moreWhether 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.
BridgeRetrieveResponse { id, accounts, activeAccountCount, 7 more } 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: "connected" | "connecting" | "backfilling" | 5 moreCurrent 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.
capabilities?: Capabilities { allowed_reactions, archive, custom_emoji_reactions, 24 more } Runtime bridgev2 room feature capabilities for this connected account, when available.
Runtime bridgev2 room feature capabilities for this connected account, when available.
Allowed Unicode reactions. Omitted means all emoji reactions are allowed.
delete?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
disappearing_timer?: DisappearingTimer { omit_empty_timer, timers, types } Disappearing-message timer capabilities.
Disappearing-message timer capabilities.
edit?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
file?: Record<string, File>Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or bridgev2 pseudo-msgtype.
Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or bridgev2 pseudo-msgtype.
formatting?: Record<string, -2 | -1 | 0 | 2 more>Supported rich-text formatting features keyed by bridgev2 feature name. Omitted means no formatting support is advertised.
Supported rich-text formatting features keyed by bridgev2 feature name. Omitted means no formatting support is advertised.
location_message?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
member_actions?: MemberActions { ban, invite, kick, 2 more } Participant management capabilities.
Participant management capabilities.
ban?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
invite?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
kick?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
message_request?: MessageRequest { accept_with_button, accept_with_message } Message request capabilities.
Message request capabilities.
poll?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
reaction?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
reply?: -2 | -1 | 0 | 2 more-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
state?: State { com.beeper.disappearing_timer, m.room.avatar, m.room.name, m.room.topic } Room state update capabilities keyed by Matrix state event type.
Room state update capabilities keyed by Matrix state event type.
provider: "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: "available" | "connected" | "limit_reached" | 2 moreWhether 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
BridgesLogins
Available bridges, bridge logins, login sessions for connect and reconnect flows, and advanced network capabilities.
List bridge logins
Get bridge login
Remove bridge login
ModelsExpand Collapse
LoginListResponse { items }
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.
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.