nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

REST API support for page content width (narrow/full-width) setting

Daniel Bisque

The page content width toggle (narrow vs. full-width) is currently UI-only
(⋯ menu → Full width). Teams managing Confluence pages programmatically —
via REST API, MCP tooling, or automation pipelines — cannot control this
setting, forcing manual intervention on every page.

Proposed: Add a contentWidth property (e.g., "default" | "full") to the
page create/update endpoints:
- PUT /wiki/api/v2/pages/{id}
- POST /wiki/api/v2/pages

This is an increasingly common gap as teams adopt AI-assisted and
API-first documentation workflows.

Accepted answers

Aron Gombas _Midori_

@Daniel Bisque

That is controlled by two content properties, and the good news is that you can manage content properties through the "v2" REST API you are already using!

REST API v2

POST /wiki/api/v2/pages/{page-id}/properties

Request Body:

JSON

{
  <span>"key"</span>: <span>"content-appearance-published"</span>,
  <span>"value"</span>: <span>"full-width"</span>
}

Similarly, repeat the call for "key": "content-appearance-draft" to ensure consistency (for the page editor).

All comments

Dan Breyen

Hi @Daniel Bisque welcome to the community. I don't see a specific issue for this suggestion on Atlassian's Jira Site. I would suggest creating one out there, as that sounds like a good option to have. Having it out there will allow people search for it and vote on it for future consideration in the product. Feel free to post the number here after you create it, so we could vote for it too.

Aron Gombas _Midori_

@Daniel Bisque

That is controlled by two content properties, and the good news is that you can manage content properties through the "v2" REST API you are already using!

REST API v2

POST /wiki/api/v2/pages/{page-id}/properties

Request Body:

JSON

{
  <span>"key"</span>: <span>"content-appearance-published"</span>,
  <span>"value"</span>: <span>"full-width"</span>
}

Similarly, repeat the call for "key": "content-appearance-draft" to ensure consistency (for the page editor).

Daniel Bisque

Brilliant, thank you. Have a nice day!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud