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
| Name | Type | Description |
|---|---|---|
days | integer | Number of days to look back (1–365). Default: 90 |
interpolate | boolean | Fill 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
| Name | Type | Description |
|---|---|---|
channel_id | string | The unique YouTube channel ID. |
count | integer | Number of snapshots returned in snaps[]. |
days | integer | Actual span of returned data in days. This may be less than requested and is 0 when no data is returned. |
snaps | array | List of historical snapshots for the channel. |
cost.total | number | Credits charged for this response. |
snaps[] Fields
| Name | Type | Description |
|---|---|---|
time | string (ISO) | Timestamp of the snapshot (e.g. 2025-10-07T00:00:00Z). |
subscribers | integer | Total number of subscribers at that time. |
videos | integer | Total number of uploaded videos at that time. |
views | integer | Total 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 Days | Credits Charged |
|---|---|
| 1–90 | 0.5 credits |
| 91–180 | 1.0 credits |
| 181–270 | 1.5 credits |
| 271–365 | 2.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-creditsheader. The JSON response also includes it ascost.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