Update a colour
A patch: omitted fields are left alone.
Renaming retags every variant colour tag and event colour scheme that carried the old label, because the label is the join key. That is a cascade across the catalogue, so rename deliberately rather than as a way to create.
Errors
404 color_not_found— unknown ID, or one belonging to another tenant.409 color_name_taken— the new label already exists.409 preset_color_immutable— a built-in palette colour can’t be edited.422 invalid_hex_format—hexisn’t a valid hex colour.
PATCH
/api/v1/colors/{id}Authorization
AuthorizationBearer token (bloomcount_...) · headerrequiredPath parameters
idstringrequiredRequest body
requiredapplication/jsonnamestringhexstring#RRGGBB, case-insensitive.
Responses
200Updated
colorIdstringrequirednamestringrequiredThe label a variant's colors array is matched against.
hexstringrequiredisPresetbooleanrequiredPreset colours ship with the account and can't be deleted.
401Missing or invalid API key, or revoked / expired.
errorstringrequired403Authenticated, but the key lacks the required scope or the tenant has no API access.
errorstringrequired404The requested resource doesn't exist or belongs to a different tenant.
errorstringrequired409The request is well formed, but it conflicts with the current state: a name already taken, a row the app
protects (the hidden Default supplier, a preset colour or category), or a staff member who has an account.
errorstringrequired422Request body or arguments failed validation.
errorstringrequired429Per-minute rate limit (60/min) or per-month cap exceeded.
errorstringrequired