01Who this is for
- Marketplace developers can automate brand asset handling without manual UI work.
- Integration partners can incorporate brand design data into their own applications.
02Design kits API, explained
The Design Kits API is a public REST interface inside the Brand Boards API v3 suite. It gives programmatic access to design kits, which hold visual brand settings used across HighLevel pages and templates. All operations work on a specific location identified in the URL.
Six endpoints are offered under the path /brand boards/locations/:locationId/design kits. They allow listing all kits, creating a new kit, retrieving a single kit, applying partial updates, permanently deleting a kit, and marking a kit as the default for the location.
Authentication follows the standard OAuth 2.0 flow used by every HighLevel marketplace API. An access token with the right scopes must be placed in the Authorization header as a Bearer token before any request is sent.
03How businesses use design kits API
- Marketing agency. The agency registers its app in the HighLevel marketplace, obtains an OAuth token, then uses the API to create design kits for each client location. It can update fonts or colors in bulk and set the preferred kit as default.
- SaaS platform developer. A SaaS provider adds the Design Kits API to its onboarding flow. After a user links a HighLevel location, the platform calls the create endpoint to generate a starter kit, then reads it later to render consistent branding inside the SaaS UI.
- Ecommerce site builder. The builder integrates the API to synchronize store brand colors with HighLevel pages. It fetches the current design kit, updates the palette when a store owner changes preferences, and ensures the default kit reflects the latest style.
04The numbers and rules that matter
- Uses standard OAuth 2.0 authentication with Bearer token.
- Versioned as part of Brand Boards API v3.
05Before you start
- A marketplace app must be registered in the HighLevel marketplace.
- Developers need an OAuth 2.0 access token that includes scopes for Brand Boards resources.
- Each request requires the location identifier of the HighLevel location to be managed.
06How to set up and use design kits API in HighLevel
Use the Design Kits API to manage brand design data
- Obtain a valid OAuth 2.0 access token and include it as a Bearer token in the Authorization header.
- Call GET /design kits to retrieve all kits for the target location.
- Send POST /design kits with the desired configuration to create a new kit.
- Use GET /design kits/:designKitId to fetch a specific kit’s details.
- Apply PATCH /design kits/:designKitId with the fields you want to change.
- Execute DELETE /design kits/:designKitId to permanently remove a kit. Note: Deleting a design kit permanently removes it and cannot be undone.
- Invoke POST /design kits/:designKitId/default to mark a kit as the location’s default. This action automatically unsets any previous default design kit.
07Things to know before you rely on it
- Only one design kit can be set as default for a location at any time.
- Deleting a design kit cannot be undone and removes the kit permanently.
- All endpoints require a valid location ID in the URL path.
- The API follows the v3 versioning scheme, ensuring stable behavior across releases.
08How it connects to the rest of HighLevel
- OAuth 2.0 authentication details for HighLevel marketplace APIs OAuth 2.0 guide
- Explore the Brand Voices API for managing brand content data Brand Voices API
- Full documentation of all HighLevel developer resources Developer resources
Michael's take

When you need to push brand colors or fonts into HighLevel at scale, the Design Kits API lets you avoid manual UI updates and keep branding consistent across many locations from a single script.
If you only ever set up a single brand and never change visual elements programmatically, the API adds complexity without much benefit. In that case staying with the Brand Boards UI is the simpler path.