>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3589801. --> Reported by: [wotnak](https://www.drupal.org/user/3558113) Related to !1100 >>> <h3 id="overview">Overview</h3> <p>Currently, page regions are managed only through auto-save or direct config changes. To allow managing page regions through the CLI and Workbench (<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/canvas/-/work_items/3576837" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/canvas/-/work_items/3576837</a></span>) we need HTTP API endpoints for getting, creating, updating, and deleting page regions.</p> <h3 id="proposed-resolution">Proposed resolution</h3> <p>Expose page regions on the <code>canvas.api.config.list</code>, <code>canvas.api.config.get</code>, <code>canvas.api.config.post</code>, <code>canvas.api.config.patch</code> and <code>canvas.api.config.delete</code> routes.</p> <p>To avoid introducing the concept of a Drupal theme for a local code components codebase managed with Canvas CLI the list endpoint should include only regions for the default theme, and the post endpoint should allow omitting the region theme and assume then the default one.</p> <h3 id="ui-changes">User interface changes</h3> <p>n/a</p> > Related issue: [Issue #3576837](https://www.drupal.org/node/3576837)