Brand colors

GET https://api.logorouter.com/api/colors/{domain}
Authorization: Bearer $LOGOROUTER_SECRET_KEY

LogoRouter extracts deterministic palettes keyed on normalized apex hostnames — ideal when you tint CRM rows, onboarding modals, or chart series using live brand pigment instead of placeholders.

Authentication

Requires a secret key. Publishable keys are intentionally rejected, mirroring broader rules in Authentication (browser <img> stays cheap; enrichment stays trusted).

Rotate secrets through the dashboard; KV-backed caches converge within operator-tunable windows.

Illustrative JSON

{
  "domain": "stripe.com",
  "colors": {
    "primary": "#635BFF",
    "palette": ["#635BFF", "#0A2540", "#00D4FF"]
  }
}

Schemas evolve additively — generate TypeScript bindings from /api/openapi.json versus hand-writing interfaces.

Usage patterns

Pair colors payloads with deterministic CDN <img> bytes documented alongside logos:

1. Tint layout chrome from palette[0] / palette[1].
2. Use WCAG tooling externally — LogoRouter exposes pigment, not compliance guarantees.
3. Cache JSON server-side respecting plan TTL headers.

Relationship to /api/meta · /api/brand

Colours land here compactly — escalate to /api/brand-endpoints when designers need richer kit exports.

Live playground preview: /docs/playground (Brand colors preset).