Skip to main content

API keys

All requests to /v1/* endpoints require an API key passed in the x-api-key header.
curl -H "x-api-key: sk-your-api-key" \
  https://api.scraper.creatorlookup.com/v1/credit-balance
The /health endpoint does not require authentication.

Key format

API keys follow the format sk- followed by 32 hex characters:
sk-a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4

Key properties

Each API key has the following attributes:
PropertyDescription
keyThe API key string
nameA human-readable label
credits_remainingAvailable credits for this key
rate_limit_per_minuteMaximum requests per minute
is_activeWhether the key is enabled

Error responses

Missing API key

// 401 Unauthorized
{
  "error": {
    "code": "UNAUTHORIZED",
    "message": "Missing x-api-key header"
  }
}

Invalid or deactivated key

// 401 Unauthorized
{
  "error": {
    "code": "UNAUTHORIZED",
    "message": "Invalid API key"
  }
}

Security best practices

  • Store API keys in environment variables, never in source code
  • Use different keys for development and production
  • Rotate keys if you suspect they have been compromised
  • Monitor your usage via the credit balance endpoint