Brand assets · Berrycrawl Docs

The brand object from POST /brand keeps visual assets deliberately simple.

{
  "logos": [
    {
      "url": "https://cdn.berrycrawl.com/brand/logo/…",
      "type": "logo",
      "theme": "light",
      "width": 1200,
      "height": 300
    }
  ],
  "images": [
    {
      "url": "https://cdn.berrycrawl.com/brand/image/…",
      "type": "cover",
      "width": 2400,
      "height": 1260
    }
  ],
  "colors": [{ "hex": "#d81b3c" }],
  "fonts": [{ "family": "Inter", "weights": ["400", "700"] }],
  "branding": {
    "images": {
      "logo": "https://cdn.berrycrawl.com/brand/logos/wordmark.png",
      "favicon": "https://cdn.berrycrawl.com/brand/logos/icon.png",
      "ogImage": "https://cdn.berrycrawl.com/brand/backdrops/cover.jpg"
    }
  }
}

Logo candidates come from favicon links, page metadata, structured data, navigation markup, and inline SVG. Square icon candidates are exposed as branding.images.favicon; a landscape wordmark is exposed as branding.images.logo; social preview imagery is exposed as branding.images.ogImage. Representative images come from social metadata, hero imagery, and structured data. Berrycrawl validates selected assets and mirrors them to its CDN when asset storage is enabled.

Use returned URLs directly. Do not derive internal object keys or assume that every website exposes every field.