ui-color-palette-manage-palettes

Publishing a color palette requires authenticating via start_authentication to obtain an accessToken, then submitting palette metadata including name, colors, presets, shifts, themes, and color_space to create a new publicly or privately visible palette.

Browsing public community color palettes does not require authentication. You can freely retrieve and explore published palettes, but protected actions like publishing, updating, sharing, or deleting palettes require a valid accessToken.

Updating an existing color palette requires a valid accessToken and the paletteId, along with payload fields such as name, description, colors, presets, shift, themes, and color_space to modify the palette's properties and visibility.

Sharing or restricting color palette visibility involves authenticating with an accessToken, then using the share or unshare functions to toggle public visibility, update sharing status, and control access to your published palettes.

Permanently deleting a color palette requires authentication via an accessToken and the specific paletteId, which removes the palette and its associated metadata including colors, themes, presets, and shifts from the system.