Activity calendar conflict hints (success payload)

This page documents conflict_hints returned on GET /api/v1/activities/activities/calendar/ when the request succeeds (HTTP 200). Each calendar slot may include an array of small objects with a stable code and a human detail.

These values are not RFC 9457 type URIs. Query validation for the same endpoint (missing window, bad datetimes, and similar) is still 422 with application/problem+json; see activities calendar validation.

Shape

Each slot may include:

"conflict_hints": [
  { "code": "activities.calendar.hint.instructor_overlap", "detail": "…" }
]

• code: stable identifier for clients, tests, and this catalogue. Branch on code, not on detail.
• detail: short explanation for people (for example tooltips). Do not parse for automation; wording may change.

When there are no overlaps, conflict_hints is an empty array.

Catalogue (code)

activities.calendar.hint.instructor_overlap

This slot overlaps another session in the calendar window and they share at least one instructor staff member, on different activities (or otherwise counted as a separate booking).

activities.calendar.hint.space_overlap

Both sessions have a space assigned, it is the same space, and their times overlap. Sessions that only share a location but have no space (or different spaces) do not receive this hint.