YouTube
YouTube channels, videos, Shorts, comments, community posts and search results.
- Unified
Account,Post,Comment,Publication- Soon
- Direct
- 47 endpoints from 3 vendor APIs
- Live
Unified
Ask for Account, Post and Comment
SoonYou name the data; AIsa answers from TikHub, DataForSEO or YouTube, whichever is fresh and working, and can switch between them without touching your code. Every value is tagged with its source, and you pay only when something comes back.
Planned calls
A first draft. None of these is callable yet, and names and fields may change.
| Call | Returns | Sources behind it | From | Direct paths |
|---|---|---|---|---|
| Account2 calls | ||||
| Look up an account | Account | TikHub, DataForSEO, YouTube | Soon | — |
| Followers of an account | Account[] | TikHub, DataForSEO, YouTube | Soon | — |
| Post2 calls | ||||
| Recent posts from an account | Post[] | TikHub, DataForSEO, YouTube | Soon | — |
| Search posts | Post[] | TikHub, DataForSEO, YouTube | Soon | — |
| Comment1 call | ||||
| Comments under a post | Comment[] | TikHub, DataForSEO, YouTube | Soon | — |
| Write1 call | ||||
| Publish a post | Publication | Your connected account | Soon | — |
Direct
Or call a vendor's endpoint yourself
LiveThe same YouTube data through each vendor's own paths and fields, on your AIsa key. You pick the vendor, and your code is written against its format, so switching later means rewriting the call.
TikHubfrom $0.0001
tikhub28 endpoints28 of its 954 endpoints cover YouTubeGET /apis/v1/tikhub/youtube/web/get_channel_infoReturns TikHub’s own JSONDataForSEOfrom $0.002dataforseo18 endpoints18 of its 489 endpoints cover YouTubeGET /apis/v1/dataforseo/serp/youtube/organic/task_postReturns DataForSEO’s own JSONYouTubefrom $0.0029youtube1 endpoint1 of its 3 endpoints cover YouTubeGET /apis/v1/youtube/searchReturns YouTube’s own JSONEvery YouTube endpoint
Read live from api.aisa.one. Metered prices start at the amount shown and vary with the request. A path opens its page in the docs.
| Method | Path | Name | Price |
|---|---|---|---|
| TikHub28 endpoints | |||
| GET | tikhub/youtube/web/get_channel_info | youtube get_channel_info | from $0.001 |
| GET | tikhub/youtube/web/get_channel_short_videos | youtube get_channel_short_videos | from $0.001 |
| GET | tikhub/youtube/web/get_channel_url | youtube get_channel_url | from $0.001 |
| GET | tikhub/youtube/web/get_relate_video | youtube get_relate_video | from $0.001 |
| GET | tikhub/youtube/web/get_trending_videos | youtube get_trending_videos | from $0.001 |
| GET | tikhub/youtube/web/search_channel | youtube search_channel | from $0.001 |
| GET | tikhub/youtube/web/search_video | youtube search_video | from $0.001 |
| GET | tikhub/youtube/web_v2/get_channel_community_posts | youtube get_channel_community_posts | from $0.001 |
| DataForSEO18 endpoints | |||
| GET | dataforseo/serp/youtube/languages | List of Youtube Languages for SERP | from $0.012 |
| GET | dataforseo/serp/youtube/locations | List of Youtube Locations for SERP | from $0.012 |
| GET | dataforseo/serp/youtube/organic/live/advanced | Live YouTube Organic Advanced | from $0.002 |
| GET | dataforseo/serp/youtube/organic/task_get/advanced/{id} | Get YouTube Organic Results by id | Metered |
| GET | dataforseo/serp/youtube/organic/task_post | Setting YouTube Organic Tasks | from $0.02 |
| GET | dataforseo/serp/youtube/organic/tasks_ready | Get Organic SERP Completed Tasks | from $0.012 |
| GET | dataforseo/serp/youtube/video_comments/live/advanced | Live YouTube Comments Advanced | from $0.004 |
| GET | dataforseo/serp/youtube/video_comments/task_get/advanced/{id} | Get YouTube Comments Results by id | Metered |
| YouTube1 endpoint | |||
| GET | youtube/search | Search Videos | from $0.0029 |
Which one to use
Unified
When you want fields that stay the same across vendors and platforms, a fallback when one source fails, and to pay only when something comes back.
Direct
When you need a parameter or field only one vendor has, or you've already built on that vendor's format.
The same Account and Post everywhere
An account on YouTube comes back with the same fields as one on X, so a prompt written for one platform works on the next.
