Content pages

Content pages hold web content that sits beside your catalog, such as shipping policies, buying guides and blog posts. Each page has a title, slug, status, optional channel, tags, categories, media and a set of fields that comes from its content type.

A content type is an attribute family for content. New organizations get three: Page, Post and Other. Every type gets Body (rich text), SEO title, SEO description, SEO keywords and Summary, and Post also gets Author.

In the admin

Turn the feature on:

1. Go to System → Settings.
2. Under Optional features, tick Content pages and click Save changes.
3. A Content group appears in the sidebar, and a Content types panel appears in Settings where you can rename types or add new ones with Add type.

If your plan doesn’t include content pages, the checkbox is disabled.

Create and edit a page:

1. Go to Content → Content pages and click New page.
2. Enter a Title and optionally a Slug (left blank, it’s generated from the title), choose a Type, and click Create.
3. On the page editor, set Title, Slug, Status and Channel (org-wide or a specific channel) and click Save.
4. Fill in the fields under Content and save them with the attribute editor’s save bar. Tags, media and categories (Save categories) save on their own.

With the API

Method	Path	What it does
GET, POST	/v1/content	List or create pages
GET, PATCH, DELETE	/v1/content/{id}	Read, update or delete a page
GET	/v1/content/by-slug/{slug}	Look a page up by slug
PUT	/v1/content/{id}/categories	Replace a page’s categories
GET	/v1/content/tags	Content tags in use, with counts
GET	/v1/content/{id}/media	A page’s media

A storefront route like /blog/[slug]:

const { data } = await pim.GET('/v1/content/by-slug/{slug}', {
  params: { path: { slug }, query: { status: 'active', channelId } },
});

List filters: status, q (title search), slug, ids (up to 200), familyId, categoryId with includeDescendants=true, channelId, tag (repeatable, all must match) and updatedSince. Sort with sortBy (publishedAt, updatedAt, createdAt, title) and sortDir. Results are paged with limit (max 200) and offset. See Listing, filtering and pagination. Full reference: api.minipim.com/docs.

Rules and limits

• If content pages aren’t turned on for the organization, or aren’t in your plan, every /v1/content request returns 403.
• By-slug returns any status unless you filter. Always pass ?status=active on routes shoppers can reach, or anyone who guesses a slug can read drafts. Unknown query parameters are rejected with 422.
• Slugs are unique per channel. Org-wide pages and each channel’s pages are separate namespaces. With channelId, by-slug returns the channel’s page and falls back to the org-wide one. Without channelId, it returns org-wide pages only.
• A duplicate slug in the same namespace returns 409. A missing slug is generated from the title.
• Publishing is gated. Creating a page as active, or moving one to active, requires the type’s required fields. Drafts can be saved incomplete. Editing a page that’s already active doesn’t re-check.
• publishedAt is set automatically the first time a page becomes active, unless you send one. Send it to keep original dates when importing. Undated pages sort last.
• A page’s family must be a content type. Product families are rejected.
• page and post can be renamed but not deleted, because the BigCommerce content import looks them up by code. A type still used by pages can’t be deleted.
• A page can have up to 100 categories. Categories are shared with products.
• Changes emit content_page.* and content_category.* events for webhooks.