Read enabled browse layouts
GET /browse-views
Returns the browse layouts this installation offers.
Signed-out callers need public mode to be on; signed-in callers need no extra permission. The response lists the enabled layouts in canonical order (grid, masonry, thumbnail, list, feed), limited to the saved selection.
Missing, null or empty settings, or a saved selection with no recognized layouts, resolve to all five. Duplicates and unknown entries are dropped, so a partly recognized selection returns only its recognized entries. These are layout choices, not permission grants. The response is the complete set, with no pagination.
The production endpoint uses a shared single-entry cache in this app instance. If a settings read fails on a cache miss, you get all five and the failure isn’t cached; a successful value can go stale. Admin writes evict the local entry and send a best-effort invalidation to other instances, but a lost notification or a read already in flight can leave old values cached. There’s no time-based expiry or freshness guarantee.
The web client applies its cached selection, refreshes from this endpoint at startup, and filters device, account and pointer-based layout choices through the offered set. A failed refresh keeps the client’s previous set, so an open browser may not reflect an admin’s change right away.
Responses
Section titled “ Responses ”A nonempty enabled-layout list in canonical order.
The browse layouts this instance offers. They control how content is shown, not who can read it.
object
Enabled layout names, returned in the order grid, masonry, thumbnail, list, feed. A write needs at least one recognized name, and any unknown name rejects the whole write. Names are case-sensitive and aren’t trimmed; duplicates are accepted and removed. On reads, a missing or empty saved list means all five; unknown saved names are skipped, and if none is left you get all five.
Example
[ "grid", "list", "feed"]