Pack Content Management API

Content management is a core part of Pack — the very reason Pack exists is so you can easily and flexibly manage complex content on your storefront. On this page, we'll dive into the different content management endpoints you can use to manage your content programmatically. Plus, we'll look at all our GraphQL endpoints for managing your content.

Authentication

All GraphQL Admin API queries require a valid Pack access token.

Include your token as a Authorization header on all API queries.

If you use the Secret Token you will will have authorization to read and write trhough the API. If you use the Public Token you will have only read authorization.

  curl --request POST \
    --url https://app.packdigital.com/graphql \
    --header 'Authorization: Bearer {YOUR_TOKEN}' \
    --header 'Content-Type: application/json' \
    --data '{"query":"query: "..."}'

Page

A page is structured data that will hold information like title, description, SEO data, and most importantly its sections – the building blocks of your site's content. When navigating to routes in your storefront under the /pages/ template, it will use this page data to get content.

Learn more about the Page content model

Queries

Mutations

Product Page

Product pages in Pack are not the actual product pages in Shopify. Pack product pages are separate data that will hold content and can be used in conjunction with your Shopify product.

A product page is structured data that will hold information like title, description, SEO data, and most importantly its sections – the building blocks of your site's content. When navigating to routes in your storefront under the /products/ template, it will use this page data to get content.

Learn more about the Product Page content model

Queries

Mutations

Collection Page

Collection pages in Pack are not the actual collection pages in Shopify. Pack collection pages are separate data that will hold content and can be used in conjunction with your Shopify collection.

A collection page is structured data that will hold information like title, description, SEO data, and most importantly its sections – the building blocks of your site's content. When navigating to routes in your storefront under the /collections/ template, it will use this page data to get content.

Learn more about the Collection Page content model

Queries

Mutations

Blog

A blog is structured data that will hold information like title, description, SEO data, and most importantly its sections – the building blocks of your site's content. When navigating to routes in your storefront under the /blogs/ template, it will use this page data to get content.

Learn more about the Blog content model

Queries

Mutations

Article

An article is structured data that will hold information like title, description, SEO data, and most importantly its sections – the building blocks of your site's content. When navigating to routes in your storefront under the /articles/ template, it will use this page data to get content.

Learn more about the Article content model

Queries

Mutations

Section

A section is the structured data that houses the content for your page. The section's data model is derived from its corresponding component schema in your code base.

Learn more about the Section content model

Queries

Mutations

Site Settings

This is the storefront site settings.

Learn more about the Site Settings content model

Queries

Mutations

Schedules

Schedules are used to publish or unpublish content at a specific time in the future.

Learn more about the Schedule content model

Queries

Mutations

Templates

A template is a container for template sections and is used to repeat these sections throughout pages that use the template.

Learn more about the Template content model

Queries

Mutations

Was this page helpful?