ChannelCrawler API
Getting Started

Evaluate the API

Coverage, access, pricing, limits, freshness, and a practical API evaluation plan.

Evaluate the ChannelCrawler API

Use this page to decide whether the API fits your discovery or enrichment workflow before you build an integration.

Coverage

  • 35M+ searchable channels: the self-service discovery index covers active YouTube channels with more than 500 subscribers.
  • 200M+ channels in the full database: custom bulk datasets and extended access are available for projects that need the broader database, including smaller channels.
  • 70+ search filters: filter by topic, location, language, channel size, engagement, growth, upload activity, video content, email availability, and other channel attributes.
  • 400+ AI subcategories: use the supported category values instead of relying only on free-text keywords.

The searchable index is refreshed daily. A daily refresh describes the index as a whole; the age and availability of individual fields can vary by channel.

Access

Create an account at platform.channelcrawler.com. Once your account is approved, create an API key from API Keys in the dashboard and buy credits from Billing. A subscription to the ChannelCrawler web app is not required.

Contact the ChannelCrawler team for the full 200M+ database, custom bulk datasets, higher-volume agreements, or account-specific limits.

Billing at a glance

ActionCost
Preview a searchFree
Return a channel summary0.1 credits per channel
Return a channel with an email using include_email: true1.0 credit per channel
Request an email but none is available0.1 credits for the returned channel summary

Use /v1/channels/search:preview to check the result volume and estimated cost before a billable search. See Credits and Billing for the other endpoints.

Limits and errors

The default per-IP limit for most endpoints is 60 requests per minute. Search preview also has a per-user limit of 30 requests per minute and 500 requests per day. Enterprise agreements can have different limits.

  • Treat 400 and 422 responses as request problems and correct the payload before retrying.
  • For 401 and 403, check the API key and account status.
  • For 429, slow down and retry with backoff.
  • For 500 or 503, retry transient failures with exponential backoff and a maximum retry count.

See Authentication and common errors for the full status table.

A practical evaluation sequence

  1. Run a free preview using the filters from a real customer brief.
  2. Request 25 channel summaries and assess relevance, field coverage, and freshness.
  3. Follow page.next_cursor through a second page to verify pagination in your client.
  4. Repeat the search with has_email: true and include_email: true on a small sample.
  5. Compare the response cost with the dashboard usage record.
  6. Test one invalid request and one throttled request so your integration handles errors before launch.

For a production decision, use several real briefs across the countries, channel sizes, and topics you expect to support.