GET
/api/v1/households/{householdId}/calendar-eventsList upcoming events from every feed, one slice per feed
Any member, a Junior included (#553). from defaults to today and to to from + 14 days; the window is clamped to 31 days. A feed that cannot be read comes back with a fixed error on its own slice — one broken calendar never hides the others (#979). busyEvenings names, per day, the event that touches that day's dinner hour — the planner's rule, so the week marks the day busy for the same reason (#3379) — and, where the planned dinner cannot reach the table around that event, dinnerMove: the one later dinner time Bryti proposes, which only the household's press applies (#4350).
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
householdId | path | string (uuid) | Required | — |
from | query | string (date) | — | — |
to | query | string (date) | — | — |
Responses
- 200OK
application/jsonUpcomingCalendarEventsResponse- 400The request could not be read as the route needs it: a body that is not the documented shape (a required field left out, a null where none is allowed, a value too long for its field), a parameter that does not parse, or a NUL character anywhere (#3540, #3541, #3543). Code validation_failed or value_too_long.
application/problem+jsonProblemDetails- 401No session, or the session is no longer valid.
application/problem+jsonProblemDetails- 426The build named in X-App-Version is below its platform's version floor (ADR-070). Problem type app-version-unsupported; the only way forward is the store. Callers without the header are never turned away.
application/problem+jsonProblemDetails- 429Too many calls in the window; Retry-After says how long.
application/problem+jsonProblemDetails- Headers
Retry-After- — Seconds to wait when a rate limit answered or the server is down for maintenance, or an HTTP date when the household's AI is paused. Absent when the household's AI quota for the period is used up — that resets by itself.
- 503The server is down for maintenance (#4693). Retry-After says when to try again; problem type maintenance. Every call under /api answers this while maintenance mode is on, the version floor included.
application/problem+jsonProblemDetails- Headers
Retry-After- — Seconds to wait when a rate limit answered or the server is down for maintenance, or an HTTP date when the household's AI is paused. Absent when the household's AI quota for the period is used up — that resets by itself.
Example
curl -b "bryti_session=…" \
"https://bryti.app/api/v1/households/3fa85f64-5717-4562-b3fc-2c963f66afa6/calendar-events"Example response
200
application/json{
"feeds": [
{
"feedId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"feedName": "string",
"events": [
{}
],
"error": "string"
}
],
"from": "2026-09-07",
"to": "2026-09-07",
"busyEvenings": [
{
"date": "2026-09-07",
"title": "string",
"startTime": "string",
"endTime": "string"
}
]
}