Section themes REST API Changelog

Community Manager
Community Manager
238 8 240

Last updated at: November 14, 2019


The Section themes REST API helps you test out Section Themes for the new online store design experience. 


During the preview phase, we will be making changes to the sections API based on your feedback. This may cause invalid theme code or page data to be present in preview shops. As the API is iterated upon, we will clean up existing data and theme code on beta-flagged preview shops, which may result in data loss. Changes will be communicated and documentation will be updated.


June 19, 2019


  • Fixed a bug where HTML generated/wrapped by the HtmlWrapper was unintentionally escaped


June 21, 2019

  • Fixed validation where insert_section override had content: false or content: []
  • Fixed the response of product_pages overrides so they are serialized correctly


June 25, 2019

New Features

  • /master_pages.json supports:
    • Sort by created_at and updated_at
      • created_at_min
      • created_at_max
      • updated_at_min
      • updated_at_max
    • limit
    • last_id
    • last_value
    • order
    • direction
    • fields
  • Theme frame wrappers support multiple classes 


  • Fixed validation so content key is required for all content sections


June 26, 2019


  • Fixed a bug preventing section themes from being imported


June 28, 2019


  • Fixed validation so each presentation setting has a type field
  • Fixed a bug where errors were not being handled when master pages were being updated, resulting in 500 Internal server error
  • Fixed a bug that prevented master pages from being updated
  • Older setting types such as image, font, snippet, layout, and hidden are not supported in frame, page, and content sections


July 3, 2019

New Features

  • Allows master pages to be created via the API


July 4, 2019


  • Fixed validation on frames.json so blocks defined in ThemeFrameSectionData match the block types defined in ThemeFrameSectionsSchema


July 5, 2019


  • Aligns section ID validation across blocks, content, overrides, and section data
  • Disabled theme editor in the developer preview since it does not currently reflect the new online store design experience


July 8, 2019


  • Sections with false content will match section files with false content schemas
  • Fixes a bug where frame and page sections were not able to define content-type settings in their schema
  • Changes to the theme frame fallback order
    • Use theme_frame_id if it exists
    • Use the frame that has the same name as the page type (product, blog, etc) if it exists
    • Use default otherwise


July 9, 2019 


  • Fixed a bug that allowed blocks to be created without IDs


July 12, 2019 


  • Content sections with false content match section files with false content schemas
  • Each presentation setting is required to have a type field


July 16, 2019


  • All sections, regardless of their type, now require a schema tag


July 17, 2019


  • name field in schemas won't accept empty strings


July 22, 2019


  • Frame sections support max_blocks 

July 23, 2019


  • section_file field in schemas don't require .liquid. It's optional.


July 25, 2019

New Features

  • A theme frame can now be assigned to the password page. The page will automatically look for password theme frame before falling back to default.


July 31, 2019

New Features

  • Frame, page, and content sections support header and paragraph settings
    • They do not count towards the max number limit of settings
    • There is a limit of 6 header and paragraph settings that can be used per section/block/content.


  • sections in master_page require a section with id  page and a section_file that points to a page section file. 
  • Each content type instance has an id
  • Customer-area page section files are saved in subfolder 'customers'


August 2, 2019


  • Renamed content to body in the text content type


August 6, 2019


  • Default presentation settings for content sections can be rendered


August 7, 2019


  • Return an error instead of breaking when the master page sections data isn't a hash.


August 9, 2019


  • Content sections where content is defined as false will return as false.


August 12, 2019


  • Thelast_modified_with field is removed from all section data.


August 13, 2019


  • section.content will return a content drop if the section only accepts a single content.
  • section.content will return an array if the section accepts multiple content even if there currently is only one or zero content stored

November 14, 2019

  • The Content Schema  has been modified to allow for more flexible content combinations. As part of the change, the content schema property and section.content Liquid API have been updated.
  • New content types: html and custom.
  • The sections and overrides properties of the REST API have been updated to reflect the new content structure.
  • The REST API endpoint to create master pages has been removed. Master pages are now created automatically (one per type).

TyW | Community Manager @ Shopify
 - Was my reply helpful? Click Like to let me know! 
 - Was your question answered? Click Accept as Solution