Change history: Partner Connect

← Changelog. Entries: 33.

• 2026-11-04 FIX-1104-1: requesting vibe:storage when connecting in COMPANY mode
• 2026-11-03 NEW-1103-13: account hint in the Connect authorization link
• 2026-10-30 FIX-1030-10: previous webhook cleanup no longer closes Bitrix24 for a Company connection
• 2026-10-22 NEW-1022-5: Who is connected to a company key
• 2026-10-20 NEW-1020-7: Company connections: readiness checks at every phase
• 2026-10-20 NEW-1020-8: AI for company connections with separate administrator consent
• 2026-10-19 FIX-1019-2: Connect revokes the presented Cowork device key
• 2026-10-17 NEW-1017-6: sign-in source label for device flow
• 2026-10-14 FIX-1014-6: Connect sign-in accepts a localhost redirect address for both client types
• 2026-10-14 BC-1014-14: PKCE is also enforced for confidential clients
• 2026-10-13 BC-1013-1: App address outside the platform: https only, not with an app or server key
• 2026-10-12 BC-1012-4: The vibe:storage scope is not granted to Partner Connect applications
• 2026-10-12 FIX-1012-5: A vibe:storage scope refusal on a Partner Connect key no longer suggests an administrator grant
• 2026-10-12 NEW-1012-6: refusal outcomes for COMPANY clients
• 2026-10-12 NEW-1012-7: Refusal codes for company connections
• 2026-10-12 FIX-1012-8: Consistent refusal for closed company connection issuance
• 2026-10-12 NEW-1012-10: Company connection status polling
• 2026-10-09 BC-1009-19: Bitrix24 account approval for AI access in Connect applications
• 2026-10-08 NEW-1008-8: Partner Connect: a "Connect AI" button example for an application inside Bitrix24
• 2026-09-30 BC-0930-31: Key revocation with a server outside its owner and Bitrix24 account scope
• 2026-09-28 FIX-0928-15: empty POST requests receive the intended validation response
• 2026-09-14 FIX-0914-17: Connect app authorization on self-hosted portals
• 2026-09-14 FIX-0914-23: rate limit descriptions state the platform-wide cap and point at the header with the effective value
• 2026-09-13 NEW-0913-2: a Partner Connect application requests the vibe:ai scope itself
• 2026-09-12 NEW-0912-2: device_id parameter in the device-flow confirmation link
• 2026-09-11 NEW-0911-7: The flow_ref field in the device-code response
• 2026-09-09 FIX-0909-8: the spec declares the 429 refusal of endpoints that carry their own rate limit
• 2026-09-09 FIX-0909-10: the token endpoint's rate-limit refusal is now machine-readable
• 2026-09-08 NEW-0908-12: key issuance now says whether the key got access to Bitrix24 data
• 2026-09-07 NEW-0907-13: /v1/cowork/me and /v1/cowork/state now name the Bitrix24 account the key is bound to
• 2026-09-04 NEW-0904-9: a partner application can revoke its own key
• 2026-09-02 NEW-0902-6: device-flow accepts a device identifier
• 2026-08-11 NEW-0811-10: granted_scopes — the issued key's actual scopes in the exchange response