taking longer than usual.

skip to content
sometimes/ developers

developers / bots / start here

bot development

build third-party bots that users install in sometimes. API 1 provides authenticated REST endpoints, permission-filtered events and individual WebRTC call streams.

API 1 · REST + gatewaydownload reference

availability

register a bot in the developer dashboard, configure its profile and requested permissions, then publish its install link. publication requires no admin approval. use a private bot and invite list for development; public bots also need HTTPS support and privacy-policy URLs. API requests use https://sometimeschat.com/api/bots/v1.

applications and installations

developers host their own bot code. sometimes stores the application identity, publication configuration, user consent and installation scope. REST handles durable reads and writes, a WebSocket gateway delivers filtered events and command invocations, and WebRTC carries individual call media streams. the bot never receives a user’s password, session cookie or account bearer token.

what bots can do

the 67 permissions cover chat, artwork, media, polls, call participation, profiles, settings, social actions and commands. actions can use the bot identity or the installing user’s identity where explicitly supported. a user can install account-wide or in one chat according to the developer’s configured policy. public and private bots publish without an admin approval step.

excluded operations

even administrator cannot vote as a bot, join or play games, publish screen shares, inspect read receipts, mark messages read, or moderate anyone else’s messages. bots cannot export account data, view reports, change usernames or account credentials, alter testing roles or install other bots. starting a game never makes the bot a player. bot calls never impersonate a human participant.

using this reference

start with registration and installation, then choose the smallest permission set for your bot. every resource chapter specifies its routes, permission requirements and object shapes. all runtime routes in the tables are relative to /api/bots/v1 unless a full control-plane path is shown. the downloadable reference contains the same content as these pages.