[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-changelog\u002F2026-06-18":3,"docs-tabs-changelog\u002F2026-06-18":6},{"content":4,"lastmod":5},"# API changes: June 18, 2026\n\n[← Changelog](\u002Fdocs\u002Fchangelog) · [June 2026](\u002Fdocs\u002Fchangelog\u002F2026-06)\n\n### NEW-0618-1: grouping in deal aggregation\n\n[POST \u002Fv1\u002Fdeals\u002Faggregate](\u002Fdocs\u002Fentities\u002Fdeals\u002Faggregate) accepts `groupBy: \"stageSemanticId\"` — a breakdown by stage semantics (in progress, won, lost) for funnel analytics.\n\n### NEW-0618-2: pagination and filter for stage history\n\n`GET \u002Fv1\u002Fstage-history` supports pagination (`meta.total`, `meta.hasMore`) and a filter by entity type `entityTypeId`.\n\n### FIX-0618-3: task time tracking does not reassign the author\n\n**Before**\n\n[PATCH \u002Fv1\u002Ftasks\u002F:taskId\u002Ftime\u002F:id](\u002Fdocs\u002Fentities\u002Ftasks\u002Ftime) accepted a `userId` field, but Bitrix24 does not reassign the record author — the value was silently ignored.\n\n**After**\n\nThe `userId` field is rejected with `400` — the author of a time-tracking record cannot be changed.\n\n**Impact on integrators**\n\nDo not pass `userId` when updating a time-tracking record.\n\n### FIX-0618-4: calendar event time zone\n\n**Before**\n\n[PATCH \u002Fv1\u002Fcalendar-events\u002F:id](\u002Fdocs\u002Fentities\u002Fcalendar-events\u002Fupdate) could save the time in the Bitrix24 user's time zone rather than the event's own.\n\n**After**\n\nThe event time zone is preserved on update.\n",null,{},1794739466870]