Desktop API Changelog

Find a version

All versions

Version v4.2.808 (2026-05-06) Latest

Part of Beeper Desktop 4.2.808.

Added

• New chat actions - You can now update more chat state directly through the API.

  API changes:

  • Added PATCH /v1/chats/{chatID} to update chat state, including drafts, title, description, avatar path, archive state, pin state, mute state, low-priority state, and disappearing-message timer.
  • Added POST /v1/chats/{chatID}/read to mark a chat as read.
  • Added POST /v1/chats/{chatID}/unread to mark a chat as unread.
  • Added POST /v1/chats/{chatID}/notify-anyway to bypass mute/snooze state when supported.

• Start direct chats - Starting a direct chat now has a dedicated endpoint.

  API changes:

  • Added POST /v1/chats/start.
  • Direct-message start behavior moved out of POST /v1/chats.
  • POST /v1/chats/start accepts accountID, user, optional messageText, and optional allowInvite.

• Message management - Individual messages can now be fetched and deleted.

  API changes:

  • Added GET /v1/chats/{chatID}/messages/{messageID}.
  • Added DELETE /v1/chats/{chatID}/messages/{messageID}.
  • PUT /v1/chats/{chatID}/messages/{messageID} responses now return the updated Message object.

• Richer chat metadata - Chat responses now include more state and display information.

  API changes:

  • Added fields to the Chat response, including network, description, imgURL, draft, reminder, snooze, isReadOnly, isMarkedUnread, isLowPriority, messageExpirySeconds, unreadMentionsCount, and capabilities.
  • network is now always included in chat responses from GET /v1/chats/{chatID}, GET /v1/chats, and GET /v1/chats/search.

• Richer message metadata - Message responses now include more delivery, edit, deletion, mention, link, and read-status information.

  API changes:

  • Added fields to the Message response, including type, editedTimestamp, sendStatus, isHidden, isDeleted, mentions, links, and seen.
  • Added attachment transcription metadata.

• Better message pagination - Message listing now returns explicit cursors for paging in both directions.

  API changes:

  • ListMessagesOutput now includes required oldestCursor and newestCursor.
  • Cursor values are opaque and should not be parsed.

• Account bridge metadata - Account responses now include bridge information, making it easier to understand which bridge or network backs each account.

  API changes:

  • Added Account.bridge to GET /v1/accounts responses.
  • Added optional Account.network.
  • No request changes are required; clients do not send bridge.

Breaking changes

• Reaction removal URL changed - The reaction key is now part of the path instead of a query parameter.

  API changes:

  • Old: DELETE /v1/chats/{chatID}/messages/{messageID}/reactions?reactionKey=...
  • New: DELETE /v1/chats/{chatID}/messages/{messageID}/reactions/{reactionKey}

• Chat creation no longer starts DMs - POST /v1/chats is now for creating chats. Starting a direct chat moved to POST /v1/chats/start. See the Start direct chats section above for the new request shape.

  API changes:

  • Removed mode from CreateChatInput.
  • Removed user from CreateChatInput.
  • Removed allowInvite from CreateChatInput.
  • CreateChatInput now requires type and participantIDs.

• Response shapes are richer - Some endpoints now return full resource objects instead of small ID/success envelopes.

  API changes:

  • CreateChatOutput is now based on Chat.
  • EditMessageOutput is now based on Message.
  • Clients should prefer id over legacy chatID or messageID compatibility fields.