[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-changelog\u002F2026-11-08":3,"docs-tabs-changelog\u002F2026-11-08":6},{"content":4,"lastmod":5},"# API changes: November 8, 2026\n\n[← Changelog](\u002Fdocs\u002Fchangelog) · [November 2026](\u002Fdocs\u002Fchangelog\u002F2026-11)\n\n### FIX-1108-1: Model lists in GET \u002Fv1\u002Fme for a Cowork key match the subscription models\n\n**Before**\n\nFor a key carrying the `vibe:cowork` scope, the `ai.usableModels` and `ai.structuredOutputs.models` fields of the [GET \u002Fv1\u002Fme](\u002Fdocs\u002Fkeys-auth\u002Fme) response also named models outside the Cowork subscription. Calling such a model with this key answered `402 cowork_model_not_allowed`. The same extra models came in the `structuredOutputsModels` field of the `400 model_does_not_support_structured_outputs` refusal from [POST \u002Fv1\u002Fchat\u002Fcompletions](\u002Fdocs\u002Fai\u002Fchat\u002Fcompletions).\n\n**After**\n\nThe `GET \u002Fv1\u002Fme` response remains HTTP 200. For a Cowork key, both fields and the `structuredOutputsModels` field name only the models this key can call under the subscription, the same set as [GET \u002Fv1\u002Fmodels](\u002Fdocs\u002Fai\u002Fmodels\u002Flist) and the `allowedModelIds` field of the `402 cowork_model_not_allowed` refusal. For keys without `vibe:cowork`, the lists are unchanged.\n\n**Impact on integrators**\n\nNo changes are needed. An agent that picks a model from `GET \u002Fv1\u002Fme` no longer gets `402 cowork_model_not_allowed` for a model from these lists.\n\n### FIX-1108-2: a call to a disabled model now counts once in AI usage statistics\n\n**Before**\n\n[GET \u002Fv1\u002Fai\u002Fusage](\u002Fdocs\u002Fai\u002Fconsumption\u002Fusage) counted a call redirected from a disabled model to its replacement model twice: `totals.calls` and `byScope.\u003Cscope>.calls` included both the `DISABLED_REDIRECT` record for the requested model and the record of the call itself.\n\n**After**\n\nThe `DISABLED_REDIRECT` record no longer counts as a call, so a redirected call counts once. `recentCalls` still shows it next to the call record. Tokens and cost do not change: they are zero for this record.\n\n**Impact on integrators**\n\nNo action needed. If you reconciled `totals.calls` with your own request counter, the mismatch on redirected calls goes away.\n\n### NEW-1108-3: Polls in chat messages and feed posts\n\nVibe supports Bitrix24 polls through `\u002Fv1\u002Fpolls` with the `vote` scope: discovery by posts or messages, questions, results, voters, voting, vote recall, stopping and resuming. `POST \u002Fv1\u002Fchats\u002F:dialogId\u002Fpolls` creates a chat poll with a UUID `idempotencyKey`; duplicate protection depends on the installed Bitrix24 version. The post list includes `hasPoll` to identify attached polls. Creating feed polls is unavailable. `resultsVisible` indicates result visibility: when `false`, counters and percentages are `null` and voters are hidden; voter lookup returns `403 RESULTS_HIDDEN`. All operations are denied to Cowork keys with read-only access to the Bitrix24 account.\n",null,{},1794739486857]