# API changes: June 18, 2026

[← Changelog](/docs/changelog) · [June 2026](/docs/changelog/2026-06)

### NEW-0618-1: grouping in deal aggregation

[POST /v1/deals/aggregate](/docs/entities/deals/aggregate) accepts `groupBy: "stageSemanticId"` — a breakdown by stage semantics (in progress, won, lost) for funnel analytics.

### NEW-0618-2: pagination and filter for stage history

`GET /v1/stage-history` supports pagination (`meta.total`, `meta.hasMore`) and a filter by entity type `entityTypeId`.

### FIX-0618-3: task time tracking does not reassign the author

**Before**

[PATCH /v1/tasks/:taskId/time/:id](/docs/entities/tasks/time) accepted a `userId` field, but Bitrix24 does not reassign the record author — the value was silently ignored.

**After**

The `userId` field is rejected with `400` — the author of a time-tracking record cannot be changed.

**Impact on integrators**

Do not pass `userId` when updating a time-tracking record.

### FIX-0618-4: calendar event time zone

**Before**

[PATCH /v1/calendar-events/:id](/docs/entities/calendar-events/update) could save the time in the Bitrix24 user's time zone rather than the event's own.

**After**

The event time zone is preserved on update.