ChannelCrawler API
API Reference

Channels — Timestamps

Retrieve historical snapshots for a channel with optional interpolation.

GET /v1/channels/:channel_id/timestamps

Get historical growth snapshots for a YouTube channel, including subscribers, views, and video count over time.

Query Parameters

NameTypeDescription
daysintegerNumber of days to look back (1–365). Default: 90
interpolatebooleanFill gaps between snapshots. Default: false

Example Request

curl -sS \
  -H "Authorization: Bearer $CC_API_KEY" \
  -H "Accept: application/json" \
  "https://api.channelcrawler.com/v1/channels/$CHANNEL_ID/timestamps?days=365&interpolate=true"

Response

Response Fields

NameTypeDescription
channel_idstringThe unique YouTube channel ID.
countintegerNumber of snapshots returned in snaps[].
daysintegerActual span of returned data in days. This may be less than requested and is 0 when no data is returned.
snapsarrayList of historical snapshots for the channel.
cost.totalnumberCredits charged for this response.

snaps[] Fields

NameTypeDescription
timestring (ISO)Timestamp of the snapshot (e.g. 2025-10-07T00:00:00Z).
subscribersintegerTotal number of subscribers at that time.
videosintegerTotal number of uploaded videos at that time.
viewsintegerTotal cumulative views at that time.

Returns historical data points with the following structure:

{
  "channel_id": "UCxxxxxxxxxxxxxxx",
  "count": 2,
  "days": 30,
  "snaps": [
    {
      "time": "2025-09-01T00:00:00Z",
      "subscribers": 14300,
      "views": 350000,
      "videos": 210
    },
    {
      "time": "2025-10-01T00:00:00Z",
      "subscribers": 15200,
      "views": 370000,
      "videos": 211
    }
  ],
  "cost": {
    "total": 0.5
  }
}

Billing

Span DaysCredits Charged
1–900.5 credits
91–1801.0 credits
181–2701.5 credits
271–3652.0 credits
  • Billed based on actual span of returned data.
  • 0 credits if no data is returned.
  • REST responses include the charge in the x-cost-credits header. The JSON response also includes it as cost.total, including when this endpoint is called through MCP.

Why use timestamp data?

  • Spot subscriber or view spikes that suggest viral moments
  • Evaluate consistent growth over time — not just one-time hits
  • Track video uploads in context of audience changes
  • Train internal models or power charts with time-series data