YouTube post API
YouTube post data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.
- 1 documented endpoints
- GET /v1/youtube/posts/{id}
Contract summary (English): Get a normalized YouTube video (capability youtube.post)
- Normalized response entity
- youtube/post
- capability
- youtube.post
Every response also carries freshness (cache / default / live) and billing metadata.
Use cases
- Feed content-analysis pipelines with structured {{platform}} posts: text, metrics, timestamps and media references.
- Power moderation, research and monitoring workflows that need the original content plus engagement counts.
- Archive {{platform}} content as stable, normalized JSON instead of brittle page scraping.
Response fields
YouTube Video Post (normalized)
Normalized YouTube video. Provider-private fields MUST NOT appear. Metric names are frozen (views/likes/comments — 观播放/赞/评); hidden counts normalize to 0. `title` is the platform extension field (the video headline — text carries the description). author and created_at are nullable: search/list cards may omit the channel block and the web surface sometimes ships only relative publish-time text ("2 weeks ago" — lossy, never fabricated into an instant; a present-but-unparsable timestamp still fails).
| Field | Type | Required | Description |
|---|---|---|---|
| id | string | Required | Video id. |
| platform | "youtube" | Required | — |
| type | "post" | Required | — |
| author.id | string | Required | Channel id (UC…). |
| author.username | string | Required | Channel @handle; the channel id when no handle exists. |
| author.display_name | string | null | Optional | Channel title. |
| author.verified | boolean | Optional | — |
| title | string | null | Optional | The video headline. |
| text | string | null | Optional | The video description. |
| created_at | string | null | Required | Publish time, UTC RFC3339; null when the card ships only relative text. |
| metrics.views | integer | Required | View (play) count. |
| metrics.likes | integer | Required | Like count; 0 when hidden. |
| metrics.comments | integer | Required | — |
| attachments | object[] | Optional | The video attachment (thumbnail preview + duration when exposed). |
| fetched_at | string | Required | — |
Field notes are shown in the contract's original English.
Response meta
| Field | Type | Required | Description |
|---|---|---|---|
| mode | cache | default | live | Required | Effective mode after merging param > max_age > source policy (D-004). |
| age_seconds | integer | null | Optional | Age of served data; null when unknown. |
| source_layer | cache | db | upstream | Required | Which layer served the response (PRD §10). |
| stale | boolean | Optional | True when stale data was served under stale_if_error / SWR (D-004). |
| billing.amount_credits | integer | Required | Micro-USD (1e-6 USD) actually charged for this request. |
| billing.cache_hit | boolean | Required | — |
Field notes are shown in the contract's original English.
Example request & response
/v1/youtube/posts/{id}curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
"https://api.fetchpi.com/v1/youtube/posts/1842951234567890123"{
"data": {
"id": "wSimVideo0001",
"platform": "youtube",
"type": "post",
"author": {
"id": "UCsim0000000000000000777",
"username": "creatordev",
"display_name": "Creator Dev",
"verified": true
},
"title": "One API for every platform.",
"text": "One API for every platform.",
"created_at": "2026-09-17T12:34:56Z",
"metrics": {
"views": 154203,
"likes": 864,
"comments": 42
},
"attachments": [
{
"type": "video",
"preview_image_url": "https://cdn.example.com/thumb.jpg",
"duration_ms": 212000
}
],
"fetched_at": "2026-09-18T07:30:00Z"
},
"meta": {
"request_id": "req_01HTXQ8Z9HTQ",
"freshness": {
"mode": "default",
"age_seconds": 3600,
"source_layer": "cache",
"stale": false
},
"billing": {
"amount_credits": 0,
"cache_hit": true
}
}
}Free demo
Create a free account, grab an API key and call this endpoint from the browser-based Playground.
Try it in the PlaygroundParameter tables, error codes and response semantics for this endpoint live in the API documentation.
Open the endpoint referenceFrequently asked questions
Which content fields are included?
The normalized content entity — text, author, timestamps, engagement metrics and media references — as documented in the field table below, plus freshness and billing metadata.
Can I try this endpoint for free?
Yes — register an account, grab an API key and call it from the Playground in the console.
How is the post capability billed?
Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.
Pricing
Per-request credit billing with cache/live freshness options — current prices live on the pricing page.