Brand kit & profile JSON
Describe, compact meta, and full brand-kit routes beside colors and intelligence — all secret-key JSON surfaces.
These GET JSON routes augment logos and palettes with profile snippets and bundled brand kits. Except where OpenAPI explicitly notes optional anonymous access (rare here), assume secret key required.
Base pattern:
GET https://api.logorouter.com/api/{route}/{domain}
Authorization: Bearer $LOGOROUTER_API_KEY/api/describe/{domain}
Describe domain — normalized company profile projection (firmographic-style fields usable in CRM merges). Think “stable JSON shape for data pipelines”, not prose marketing copy.
Ideal for enriching leads when you already have an apex hostname.
/api/meta/{domain}
Brand metadata — compact card-friendly JSON (titles, shorthand labels, condensed facts). Fits UI chips and search result subtitles where the full /api/brand payload would be wasteful.
/api/brand/{domain}
Brand kit — combines logo artefact URLs/variants where available, color rolls, snippets, and other packaged assets tailored for design tooling scenarios.
Use /api/meta first if you only need header copy; escalate to /api/brand when designers need interchangeable assets.
/api/logo/{domain}/refresh · /api/logo/{domain}/cache
/api/logo/{domain}/refresh (POST) and /api/logo/{domain}/cache (DELETE) handle invalidate / rebuild workflows for cached raster / vector derivatives. Availability depends on billing entitlements flagged in-plan metadata.
Consult OpenAPI responses for entitlement errors (403 problem bodies).
Cross-links: OpenAPI overview · Fallbacks · Playground presets (intelligence + colors).