Back — Shift Scheduling API
Product updates

What's new

Every engine version that changed the public API — new fields and endpoints, validation, and breaking changes, with the date it shipped. It signals and justifies; it does not guarantee compliance.

10 updatesone entry per engine version

November 2026

2
Improvement

v0.9.0 — ⚠️ BREAKING: two pattern keys renamed

Two shift patterns that were named after companies now have keys that describe their structure: one is the 28-day 8-hour "7,3,7,3,7,1" cycle (8h-7-3-7-3-7-1), the other the 8-hour morning–afternoon–night rotation with 12-hour days (8h-rde-12h). The cycles are identical character for character, so rosters do not change. There is no alias: the old key is now an unknown pattern and returns 422 — if you stored it, pick it again from /v1/patterns. The v1 schema is unchanged; only the accepted key values changed.

  • Old key → 422 (unknown pattern); new keys: 8h-7-3-7-3-7-1 and 8h-rde-12h
  • Pattern library version: 2026-11-12
Feature

v0.8.0 — employment interval per person

The new optional employed_from / employed_until fields on an employee (inclusive; reversed order → 422) describe mid-month joiners and leavers. Days outside the interval are -, do not count towards coverage, assignments has no effect on them, the compliance check evaluates only the employed days, and the working-time-frame expected_hours counts only the workdays inside the interval, per person. On both build endpoints; without the fields the response is the same as before.

September 2026

7
Feature

v0.7.0 — roster for any date range: POST /v1/schedule:build-range

The new endpoint builds a roster for any inclusive date range (up to 366 days), not just a calendar month. Rolling compliance windows run over the WHOLE range; a reversed or too-long range returns 422. The monthly /v1/schedule:build is unchanged.

Security

v0.6.2 — input size limits

Request fields now have upper limits (e.g. at most 500 people on the roster, 400 holidays, rule_overrides 50×50, assignments 500 people × 62 days); an oversized request gets a clean 422 instead of loading the server.

Security

v0.6.1 — invalid input: 422 instead of a server error

An out-of-range crew number, a LEAN employee (not supported over REST), a duplicate staff_id and a non-finite number (NaN, Infinity) in rule_overrides now return a readable 422 instead of a 5xx.

Improvement

v0.6.0 — statistics count flex and holiday-rest days

Two new fields in the per-person statistics: flex_days (flex off, CS) and holiday_rest_days (rest for a public holiday, Üp).

Feature

v0.5.0 — working-time frame: expected hours and balance

New work_time_frame rule type and the Hungarian rulebook's munkaidokeret rule (Labour Code §§ 93–94, parameters weekly_hours 40 and frame_months 4 — adjustable via rule_overrides). Statistics now also return the month's expected hours (expected_hours: general workdays × daily hours, public holidays deducted) and the per-person balance (balance = worked − expected). It signals and justifies — it does not guarantee compliance.

Feature

v0.4.0 — per-person statistics in the response

The roster response has a new statistics field per person: worked hours (worked_hours), nights (night_count), shifts (shift_count) and leave days (vacation_days) — computed with the overrides applied.

Feature

v0.3.0 — per-day overrides on top of the rotation: assignments

The new assignments field (staff_id → {day → symbol}) overrides a person's symbol on a given day on top of the rotation; coverage and the compliance check use the overridden symbols. The override is part of the input, so the output stays deterministic; an unknown symbol returns 422.

August 2026

1
Feature

v0.2.0 — your own holiday calendar, rule overrides, time zone and clock changes

The request's holidays field takes your actual holiday calendar, and rule_overrides adjusts rule thresholds and switches rules on or off per request (the engine stores nothing). The site's timezone field (IANA, default Europe/Budapest) gives real working hours: the night of a clock change is 11 or 13 hours. Two new reference-data endpoints: GET /v1/holidays?year= and GET /v1/rules.

Newsletter

Follow how OPEREX evolves

New modules, industrial shift-log tips and ISO 45001 practices — once a month at most, no spam.

You can unsubscribe anytime — the link is at the bottom of every email.