Member Sites APIs

Use the Member API to manage a member’s own sites. Use bundle uploads to publish a static V1 site’s build. Start with Build a member site for the app, SDK and CLI workflow.

APIs for static V1 sites

Task	Reference
Manage sites	List, add, read, change and delete
Publish a build	Start a bundle upload and publish the bundle
Find published builds	List a site’s bundles and make an earlier bundle current. Read the rollback restrictions in the reference before using it
Share access	Search share targets, list shares, share, change permission and stop sharing
Set account preferences	Pin a site, order pins, unpin, choose a home site and clear it
Inspect the owner’s database	List tables and read rows with the site owner’s Bearer token
Download the database	Download a site’s database

Pins and the home site control the member’s account navigation. They do not showcase a site on a public profile. The owner database inspection APIs are read-only management APIs. They are separate from the database calls your site makes as a visitor. Follow Inspect your site’s data for the owner workflow. For database reads and writes inside your app, use the member site database SDK. Its tables and access rules come from db/schema.json and are published with the build.

Compatibility endpoints

The Member Sites compatibility section keeps references for older integrations separate from the V1 workflow. Their existing links still work. Current company-site APIs are grouped under Website. The Company Liquid copy, publishing and versions and Company Liquid files and pages groups are in Member Sites compatibility for company integrations that still use the older workflow.

Liquid copy, publishing and versions and Liquid files and pages describe the older Liquid content workflow. Publish static builds with bundles instead of Publish a site, Git versions or restore a Git version.
Copy a site currently copies the older Liquid content, not a static V1 bundle. It does not create a working copy of a V1 build.
Older database backend describes the older database status, setup, table, row and schema-statement operations. Those operations do not manage the V1 database declared in db/schema.json. The database download listed above does use the V1 database.
Account menu integration contains the member’s account menu and menu removals. The menu endpoint remains available for integrations that draw account navigation; publishing or sharing a V1 site does not require you to build that menu.

See Publish a member site for the recommended CLI workflow, and Share a site for visibility, access and credited links.

Overview

Storefront

Commerce

Checkout

Member API