Walls
Walls are content spaces where posts are published. Each wall can be scoped to specific groups (departments, professions or custom groups). Walls are read-only over the API today; create them in the Monotree admin.
Required scope: read:walls. The walls feature must be enabled for the company: while it is off, every wall, post and comment endpoint returns 403 with the message The walls feature is not enabled., reads and writes alike (see feature-gated endpoints).
Endpoints
GET
/api/open/v1/wallsList all walls (paginated)
GET
/api/open/v1/walls/{id}Get a single wall
List walls
Walls are sorted by name. Standard list parameters apply: page, per_page (max 50), since. See Pagination.
curl "https://customer.monotree.com/api/open/v1/walls?per_page=10" \
-H "Authorization: Bearer mono_your_token_here"| Query param | Notes |
|---|---|
page, per_page, since | Standard pagination — see Pagination. |
Response
{
"data": {
"id": 1,
"name": "General",
"groups": [
{
"id": 1,
"name": "Kitchen Staff",
"type": "department",
"created_at": "2026-01-15T10:00:00+01:00"
}
],
"created_at": "2026-01-15T10:00:00+01:00"
}
}Field notes
groupslists the groups the wall is targeted at: departments, professions or custom groups. A wall can also be targeted at individually chosen people, and the API does not return those. So an emptygroupsarray means the wall is company-wide only if it has no chosen people either; a wall for chosen people only also shows"groups": [].- The list includes walls that are not published, and the response has no field that tells them apart.
- Posts live under the wall:
GET /walls/{id}/posts.