API Documentation

Everything you need to integrate the MCC Color API into your application.

Authentication

Bearer token in headers

Base URL

api.mycarcolor.com

Rate Limits

Per-plan, per-second

HTTPS Only

TLS 1.2+ required

Authentication

All API requests require a valid API key passed in the Authorization header as a Bearer token.

Authorization: Bearer mcc_sk_your_api_key_here

API keys are prefixed with mcc_sk_ for secret keys and mcc_pk_ for publishable keys. Secret keys should never be exposed in client-side code.

Quick Start

Make your first API call in seconds.

curl
curl -X GET "https://api.mycarcolor.com/v1/colors/search?q=candy+white&make=toyota" \
  -H "Authorization: Bearer mcc_sk_your_api_key" \
  -H "Content-Type: application/json"

Sample Response

200 OKapplication/json
{
  "colors": [
    {
      "id": "clr_abc123",
      "code": "040",
      "name": "Super White",
      "manufacturer": "Toyota",
      "rgb": "#F5F5F0",
      "year_range": "2018-2024",
      "vehicles": [
        { "make": "Toyota", "model": "Camry", "years": ["2020", "2021", "2022"] },
        { "make": "Toyota", "model": "Corolla", "years": ["2019", "2020", "2021"] }
      ]
    }
  ],
  "total": 1,
  "limit": 20,
  "offset": 0
}

Endpoints

Complete reference for all available API endpoints.

GET/v1/colors/search

Search colors by name, code, or RGB value

ParameterTypeRequiredDescription
qstringRequiredSearch query (color name or code)
makestringOptionalFilter by vehicle make
modelstringOptionalFilter by vehicle model
yearstringOptionalFilter by vehicle year
limitintegerOptionalResults per page (default: 20, max: 100)
offsetintegerOptionalPagination offset
GET/v1/colors/:id

Get full color details by ID, including vehicle compatibility and swatches

ParameterTypeRequiredDescription
idstringRequiredColor ID or cloud reference ID
include_vehiclesbooleanOptionalInclude full vehicle compatibility list
GET/v1/brands

List all available automotive brands

ParameterTypeRequiredDescription
limitintegerOptionalResults per page (default: 50)

Rate Limiting

Rate limits are enforced per API key on a per-second basis. When you exceed your rate limit, the API will return a 429 Too Many Requests response.

Rate limit headers included in every response:

X-RateLimit-Limit: 20        # Requests allowed per second
X-RateLimit-Remaining: 19    # Remaining requests this second
X-RateLimit-Reset: 1709913600  # Unix timestamp when limit resets