Extract brand color palettes from any public website URL

Overview

Brand color extraction for developer products

Give Me Colors is an API for extracting useful brand and theme color palettes from public website URLs. It fetches static HTML, reads page metadata, analyzes inline styles and linked CSS, optionally samples favicons and OpenGraph images, and returns a structured palette for design tools, AI website builders, lead enrichment systems, brand analysis workflows, internal dashboards, and marketing tools.

Authentication

Use RapidAPI for public access

Use the RapidAPI headers shown in your subscription dashboard. RapidAPI handles API keys, plan quotas, usage tracking, and billing for public access.

Endpoints

Routes with direct anchor links

curl "https://YOUR_RAPIDAPI_HOST/v1/palette?input=https%3A%2F%2Fexample.com&colors=8&max_assets=0" \
  -H "X-RapidAPI-Key: YOUR_RAPIDAPI_KEY" \
  -H "X-RapidAPI-Host: YOUR_RAPIDAPI_HOST"

Request body

Every request option has an anchor

{
  "input": "https://example.com",
  "colors": 8,
  "ignore_neutrals": false,
  "timeout_seconds": 10,
  "max_css_files": 8,
  "max_assets": 5
}

Request option table

{
  "colors": 8,
  "ignore_neutrals": false,
  "timeout_seconds": 8,
  "max_css_files": 6,
  "max_assets": 2
}

Response schema

Hex colors, RGB values, percentages, confidence, and evidence

{
  "source": {
    "input": "https://example.com",
    "kind": "website",
    "final_url": "https://example.com/",
    "title": "Example Domain",
    "description": null,
    "canonical_url": null,
    "metadata": {
      "theme_color": null,
      "og_image": null,
      "favicon": null
    }
  },
  "palette_block": [
    { "hex": "#2563EB", "percentage": 41.2 },
    { "hex": "#FFFFFF", "percentage": 33.8 }
  ],
  "palette": [
    {
      "hex": "#2563EB",
      "rgb": [37, 99, 235],
      "percentage": 41.2,
      "confidence": 0.89,
      "sources": ["css_variable", "linked_css_file"]
    },
    {
      "hex": "#FFFFFF",
      "rgb": [255, 255, 255],
      "percentage": 33.8,
      "confidence": 0.76,
      "sources": ["inline_style", "linked_css_file"]
    }
  ],
  "warnings": [
    {
      "code": "NO_JS_RENDERING",
      "message": "This analysis used static HTML/CSS/assets only. JavaScript-rendered styles may be missing."
    }
  ]
}

Source fields

Palette fields

Possible sources values can include CSS variables, matched CSS selectors, inline styles, metadata, SVG colors, raster image evidence, favicon evidence, logo image evidence, or OpenGraph image evidence. Treat sources as descriptive labels, not a fixed enum.

Errors and rate limits

Handle expected failures as product states

All error responses use {"error":{"code":"ERROR_CODE","message":"Human-readable message"}}.

Security and public API limits

Hardened for public website analysis

These limits reduce abuse risk, prevent SSRF, avoid port probing, and control bandwidth and cost.

• Only http and https URLs are accepted.
• Only standard public ports are accepted: 80 for HTTP and 443 for HTTPS.
• Localhost, .localhost, private IPs, loopback, link-local, multicast, documentation, carrier-grade NAT, benchmarking, and reserved ranges are blocked.
• DNS is resolved before each upstream fetch, and redirects are manually revalidated.
• Linked CSS files and visual assets use the same public URL checks.
• Response size caps are enforced: HTML 2 MB, CSS 1 MB, and images/assets 5 MB.
• Public options are bounded: colors 1-32, timeout_seconds 1-30, max_css_files 0-32, max_assets 0-8.

Best practices for API consumers

• Use POST /v1/palette for production integrations.
• Send requests through your backend when you need to protect your RapidAPI key.
• Use max_assets: 0 when speed matters more than visual asset analysis.
• Use max_assets: 5 to 8 when logos, favicons, and OpenGraph images matter.
• Cache repeated URL analysis and normalize URLs before sending requests.
• Use warnings to communicate confidence caveats to users.
• Treat confidence as a relative score, not a guarantee.
• Handle 422 NO_COLORS as a valid nothing-useful-found result.
• Respect Retry-After on 429 responses.

Integration pattern

Call RapidAPI from your backend for production apps

RapidAPI examples are easy to try with curl, but production web apps should usually make the request from server-side code. That protects your RapidAPI key and gives you a place to normalize URLs, cache repeated analysis, and enforce your own product limits.

Your app frontend
  -> Your backend or serverless function
  -> RapidAPI Give Me Colors endpoint
  -> Public target website

const paletteRequest = {
  input,
  colors: 8,
  ignore_neutrals: false,
  timeout_seconds: 8,
  max_css_files: 6,
  max_assets: 2
};

• Accept a URL from your application UI.
• Validate or normalize the URL before calling the API.
• Choose faster options for previews and richer options for saved analysis.
• Send X-RapidAPI-Key and X-RapidAPI-Host from server-side code.
• Cache normalized URL results when repeated analysis is likely.

Example use cases

Where a website theme color API fits

Limitations

Fast static analysis, not browser rendering

Give Me Colors v1 is optimized for fast, static brand color extraction from public URLs. It works best on websites that expose meaningful colors through HTML, metadata, CSS, favicons, logos, or OpenGraph images. It does not execute JavaScript, so results from heavily client-rendered websites may be partial.

• No browser screenshots, Playwright, or Chromium rendering.
• CSS parsing is lightweight and deterministic, not a full browser cascade engine.
• AVIF URLs may be detected as image inputs, but AVIF decoding is not enabled yet.

FAQ

Common integration questions