Skip to main content
CMS in Fire spark is how you publish named content blocks that channels can fetch by a reserved name. Use it for terms of service, promo videos, PDFs, and other content that is not owned by your POS menu sync.

​
Templates and blocks

In the dashboard, CMS is under Templates (/cms/templates) and Blocks (/cms/blocks).

​
Item types and limits

Each block has 1–25 top-level named slots (key). A LIST slot holds 1–10 entries of one leaf type. Lists cannot nest. In storefront code, find a slot by key (for example banners), then map items when the type is LIST.

​
How channels consume blocks

  1. Create a template (optional) that defines item keys and types.
  2. Create a block, optionally starting from that template, and reserve a unique name (for example legal-tos).
  3. Fill item content in the dashboard.
  4. Fetch the block from Storefront with GET /api/storefront/v1/cms/blocks/{name}.
Only ACTIVE, non-deleted blocks are returned. The name is unique per merchant and environment.
See Get CMS block.
Older entity-field templates attached to brands and stores (cms_template_id) remain in the API for compatibility. New merchandising content should use CMS blocks.

​
When CMS helps

Channels

Where storefront apps run

Brands

Brand identity and legacy entity CMS

Stores

Location pages

Menus

Catalog structure from your POS