How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Beeper Accounts API

Chat Accounts connected to this Beeper Desktop instance. Each Account owns a bridge and network.

Beeper Accounts API is one of 7 APIs that Beeper publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Account. The published artifact set on APIs.io includes an OpenAPI specification and an AsyncAPI specification.

This API exposes 1 operation across 1 path, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version 5.0.0.

Requests are made against a single base URL, http://localhost:23373.

1 operations 1 paths 5 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
5.0.0
Base URL
http://localhost:23373
Authentication
HTTP Bearer, OAuth 2.0
Contact
Terms of Service
Resource Areas
1

Authentication & Security 2

Beeper Accounts API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 2 scopes. By default, every request must be authenticated.

  • bearerAuth — Bearer token authentication. Access token obtained via OAuth2 PKCE flow or created in-app. Required for all API operations.
  • oauth2 — OAuth2 Authorization Code flow with PKCE for obtaining bearer access tokens. Used by MCP servers to authenticate clients.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Accounts 1

Chat Accounts connected to this Beeper Desktop instance. Each Account owns a bridge and network.

GET
/v1/accounts
List Chat Accounts
getAccounts → 200400401403404422429500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are User (8 properties), Account (4 properties), Error (3 properties), Bridge (3 properties). Each schema is shown below with its type and property counts.

GetAccountsOutput
array
Accounts configured on this device. Includes accountID, bridge metadata, optional network name, and user identity.
Bridge
object
Bridge metadata for the account. Available in Beeper Desktop v4.2.785+.
3 properties 3 required
User
object
User the account belongs to.
8 properties 1 required
Account
object
A chat account added to Beeper.
4 properties 3 required
Error
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

beeper-accounts-api-openapi.yml Raw ↑

Other APIs Beeper publishes across the network.

Beeper App API
Beeper Chats API
Beeper Contacts API
Beeper Files API
Beeper Messages API
Beeper Server API
Where this information came from

This is an independent, third-party profile of Beeper Accounts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.