YouTube channel shorts

Server URLloading...

POST

/social/youtube_channel_shorts

Send

Authorization

Header

Body

Get a channel's Shorts (short-form vertical videos), separate from its long-form uploads. Use for short-form strategy questions. Shorts cards carry ONLY a view-count string — no date, likes or comments — so a date range or any totals means fetching each Short individually, one call each. Comment counts need with_comments (a second call per video); without it they come back absent, NOT zero.

For a date range pass since and until rather than a large item cap — plus tz, the user's timezone, so the days are cut on THEIR calendar. The walk pages back until it reaches that date, and the tool returns a totals block (posts, views, likes, comments, engagement_rate) computed over exactly that window. Quote those numbers; never add up the rows yourself. Before reporting a total, read these four fields — each one exists because ignoring it produced a wrong report:

• partial: true — the walk stopped early, so this is a FLOOR, not a measurement. Say so, or re-run; never present it as the period's total.
• overlaps — names a sibling feed returning the SAME pieces. Report one feed or the other; adding both counts every piece twice.
• views_metric — which upstream number views came from. Two feeds on one platform can report different values for the same piece, so only compare or combine totals whose views_metric matches.
• measured_at — when it was read. Live counts move fast; state it whenever you report a total, and never explain a difference between two runs as a mistake before checking whether the pieces simply gained views between them.

COVERING MORE THAN ONE ACCOUNT OR FEED: never add these totals in your head. Each result carries a receipt — a TSV block with the same five columns on every platform. Paste the receipts into run_code and total them there: dedupe on (platform, id) so a piece returned by two feeds is counted once, keep an empty field as missing rather than 0, and only add views across receipts whose views_metric matches. Report the code's number, not a retyped one, and hand back the per-piece list so the total can be checked by hand. For regular videos use youtube_channel_videos.

Header Parameters

Response Body

curl -X POST "https://example.com/social/youtube_channel_shorts" \  -H "Content-Type: application/json" \  -d '{    "organization_id": "string",    "input": {      "channel": "string"    }  }'

{  "operation": "instagram_profile",  "result": {    "summary": "string",    "channel": "string",    "count": -9007199254740991,    "totals": {      "window": {        "since": "string",        "until": "string",        "tz": "string"      },      "posts": -9007199254740991,      "views": 0,      "likes": 0,      "comments": 0,      "engagement_rate": 0,      "rows_without_views": -9007199254740991,      "rows_without_likes": -9007199254740991,      "rows_without_comments": -9007199254740991,      "views_metric": "string",      "measured_at": "string",      "partial": true,      "overlaps": "string",      "oldest": "string",      "newest": "string"    },    "receipt": "string",    "coverage": "string",    "videos": [      {        "id": "string",        "url": "string",        "title": "string",        "description": "string",        "channel": {          "id": "string",          "title": "string",          "handle": "string",          "url": "string"        },        "published_at": "string",        "published_text": "string",        "length": "string",        "view_count": 0,        "view_count_text": "string",        "like_count": 0,        "comment_count": 0,        "thumbnail": "string"      }    ]  },  "requests": 0,  "credits_charged": 0}