Skip to content

Read available browse layouts

GET
/admin/system/browse-views

Returns the enabled browse layouts.

You need system.config.read or system.admin for the whole install; a permission held only for a team doesn’t count. Without one you get 403, and signed-out callers get 401.

Enabled layouts come back in this order, with duplicates removed: grid, masonry, thumbnail, list, feed. With nothing saved, or an empty saved list, you get all five. Unknown saved values are skipped, and if none of the saved values is recognized you also get all five.

This admin endpoint reads the database directly. Clients load their layout choices from GET /browse-views, which uses a separate cache and is covered by public mode, so its answer can differ from this one. Layouts only change how content is shown, not who can read it.

The enabled layouts in their standard order, with defaults applied.

The browse layouts this instance offers. They control how content is shown, not who can read it.

object
enabled
required

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.

Array<string>
>= 1 items
Allowed values: grid masonry thumbnail list feed
Example
[
"grid",
"list",
"feed"
]

Authentication required, missing, or invalid

object
error
required

Human-readable error summary

string
Example
the request could not be completed
Example
{
"error": "authentication required: sign in and retry with a valid session or API token"
}

Authenticated but missing required capabilities

object
error
required

Human-readable error summary

string
Example
the request could not be completed