Back to Changelog
v2026.08.03

Reliable multi-account connections and consistent account data

Today's release fixes how multiple accounts on the same network get connected and how account data is listed and returned:

  • Force account selection when connecting a network: Most networks were silently reusing whatever account was already signed in on the browser, so connecting a second account often just re-authorized the first one. Pass a new force_account_selection flag to POST /v1/social-networks/:network/auth-url (also available on the get_auth_url tool) to make the network show its account picker instead. Supported today for TikTok, Facebook, Instagram, YouTube, and Google Business Profile, with no effect on networks that don't support it, so you can send it unconditionally. Existing integrations are unaffected when the flag is left off.
  • tenant_id now included on every social account response: Connecting a Bluesky account without passing tenantId previously created the account with a null tenant and gave no indication anything was missing, which could later cause tenant-filtered lookups to come back empty with no explanation. The Bluesky connect response, and account list responses, now consistently include tenant_id so you can catch a missing tenant immediately instead of debugging it downstream.
  • Fixed missing and duplicate accounts when paginating GET /v1/social-accounts: Paging through accounts with limit/offset could skip some accounts entirely and return others twice, especially on orgs with many accounts under active token refresh. Results are now returned in a stable order, so paginating through your accounts returns every account exactly once.