Admin GraphQL API / 2026-04 · Shopify Plus only

Checkout And Accounts Configuration API
Branding for checkout, customer accounts, and sign-in is unified into a single API

Settings and branding that were previously split between the Checkout Profile API and the Checkout Branding API are consolidated into one API in API version 2026-04. Configure shared design tokens once and apply them consistently across all three surfaces. Shopify Plus only.

On this page
  1. What's actually changing (understand in 30 seconds)
  2. How it works: a shared layer + per-surface overrides
  3. Four things you can do
  4. Before vs. after the unification
  5. Color palette reference model, illustrated
  6. Requirements
  7. Five points engineers need to know
  8. Three practical use cases
  9. One-line summary you can pitch with

1What's actually changing

Until now Checkout Profile API and Checkout Branding API the two-API split for settings and branding has been
API version 2026-04 introduced in Checkout And Accounts Configuration API consolidated into one.
The target surfaces also expand from "checkout only" to checkout + customer accounts + sign-in —three surfaces in total.
Profile Branding

Before: two separate APIs

Checkout Profile API and Checkout Branding API were handled separately, focused mainly on checkout. Both APIs are nowdeprecated.

After: consolidated into a single API

All settings and branding capabilities are unified into one API. Apply consistent branding across checkout, customer accounts, and sign-in.

2How it works: a shared layer + per-surface overrides

Shared layer (configured once) designTokens Colors, spacing, etc. components Component styles surfaces.checkout Override logo, colors, and section styles surfaces.customerAccounts section styles can now be applied too surfaces.signIn Override logo, colors, and section styles Keep the shared settings and override only the parts you need per surface
The two-layer structure is the key : Shared designTokens / components defines the overall brand in one place, andsurfaces.checkout / surfaces.customerAccounts / surfaces.signIn overrides only the per-surface differences.
Previously checkout-only, section styles (padding, shadows, colors, borders, border radius) can now also be applied to customer account pages.

3Four things you can do

① Shared branding settings

Shared designTokens and components , set your brand once and it applies consistently across checkout, customer accounts, and sign-in. section styles can also be extended to customer account pages.

② Per-surface overrides

surfaces.checkout / surfaces.customerAccounts / surfaces.signIn , you can pinpoint-override logo, colors, and section styles per surface.

#HEX

③ Direct color specification

main / header / orderSummary and other sections, set HEX values or palette colors directly. No more mapping to a limited set of color schemes. Save and reference a palette of up to 20 colors.

④ Per-market branding

Apply branding settings unique to each market. Vary the page appearance by country or region.

4Before vs. after the unification

ItemBeforeCheckout And Accounts Configuration API
Number of APIs 2 Checkout Profile API + Checkout Branding API 1 consolidated into
Target surfaces Checkout-centric 3 surfaces checkout, customer accounts, sign-in
section styles Checkout only Also applies to customer account pages
Color specification Mapping to a limited set of color schemes HEX values or palette colors specified directly on sections
Per-market branding — Supported Configured per market
Status of legacy APIs — Deprecated The 2 legacy APIs are deprecated
Checkout Profile API / Checkout Branding API areDeprecatedbut this release post does not documentspecific migration steps or end-of-support dates. Check the developer documentation for the actual migration design.

5Color palette reference model diagram

Editable palette (up to 20 colors) Update this one color, and... Reference checkout / header 's color customer accounts 's color sign-in color Every place referencing it switches to the new color at once
Save brand colors as apalette of up to 20 colorsand reference them from anywhere you pick a color.Update one color in the palette, and every place referencing it reflects the change—centralized management like design tokens kicks in.

6Requirements

Shopify Plus only

This API is exclusive to Shopify Plus merchants. It is not available on plans other than Plus.

2026-04

API version 2026-04 or later

Available from API version 2026-04. On earlier versions, you'll have to use the legacy APIs (deprecated).

Part of the Admin GraphQL API family. See the developer documentation for the detailed schema, field definitions, and migration guide (this post does not cover the full set of fields).

75 points engineers need to know

1. The two legacy APIs are deprecated

Both Checkout Profile API and Checkout Branding API are deprecated. Build new implementations on the unified API. Existing code becomes a migration target (no migration steps or end date are documented—check the docs).

2. A two-layer "shared + override" model

Lay down a shared designTokens / components as the base, and override only the diffs withsurfaces.* . Keeping the shared layer thick and overrides thin makes operations less likely to break down.

3. Colors drop scheme mapping

You no longer have to assign colors to a limited set of color schemes—specify HEX or palette colors directly onmain / header / orderSummary and similar. The color you intend lands exactly as is.

4. Palettes are "reference"-based

Define a palette of up to 20 colors, and specify them by reference rather than by value from each location. Update the palette once, and all references change in lockstep. You can operate it with the same mindset as CSS variables or design tokens.

5. Per-market branding consolidates multi-country support into a single API

You can apply branding settings unique to each market, so country- and region-specific visual variations are handled within the same API. You can consolidate brand management for multi-country rollouts into a single API.

83 business use cases

USE CASE 1

Eliminate the "visual inconsistency" between checkout and account pages

Problem
Checkout has been brand-tuned, but the customer account and sign-in screens still use the default design, leaving logo, colors, and spacing inconsistent.
Approach
Shared designTokens / components to define the brand in one place and apply the same tone across all three surfaces. Extend section styles to customer accounts as well.
Impact
A consistent experience from purchase through the member area, eliminating brand erosion and the "different site" feeling.
Technical notes
Build on the shared layer and override only the screens that need to differ with surfaces.* . Shopify Plus only, API version 2026-04 and later.
Update once → reflected everywhere
USE CASE 2

Run rebrands and seasonal campaign color swaps from a single source

Problem
Every brand color change or sale theme swap requires editing colors screen-by-screen and section-by-section, leading to missed spots and rework.
Approach
Consolidate brand colors into a palette of up to 20 colors, and have each surface reference the palette. To change colors, just update the palette.
Impact
All references update at once with zero missed colors. Dramatically reduces the effort and mistakes involved in rebrands and campaign swaps.
Technical notes
Direct HEX values are also supported, but colors you plan to swap operationally should use palette references so changes propagate.
USE CASE 3

Apply market-specific local brands across multi-region stores

Problem
You want to vary logos and color schemes by country or region, but separate screens and APIs make per-market delivery cumbersome.
Approach
Define market-specific branding per market, layering each market's diffs on top of the shared base.
Impact
Deliver local brands per country through a single API. Centralize brand management while still optimizing for each locale.
Technical notes
A design that overrides only market-specific values on top of the shared layer is the most resilient. Plus only.

9One-line summary for proposals

"Branding for checkout, customer accounts, and sign-in isunified into a single API(the previous two APIs are deprecated).
Configure everything at once with shared tokens + per-screen overrides, with colors specified as HEX or via a palette of up to 20 colors,either directly or by reference,Per-market deliveryis also supported.
Available on API version 2026-04 and later, Shopify Plus only."