Threads
Threads profiles, posts, replies, reposts and profile search.
- Unified
Account,Post,Comment,Publication- Soon
- Direct
- 8 endpoints from 1 vendor API
- Live
Unified
Ask for Account, Post and Comment
SoonYou name the data; AIsa answers from TikHub today and can add or switch sources 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 | Soon | — |
| Followers of an account | Account[] | TikHub | Soon | — |
| Post2 calls | ||||
| Recent posts from an account | Post[] | TikHub | Soon | — |
| Search posts | Post[] | TikHub | Soon | — |
| Comment1 call | ||||
| Comments under a post | Comment[] | TikHub | Soon | — |
| Write1 call | ||||
| Publish a post | Publication | Your connected account | Soon | — |
Direct
Or call a vendor's endpoint yourself
LiveThe same Threads 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.
Every Threads 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 |
|---|---|---|---|
| tikhub/threads/web/8 endpoints | |||
| GET | tikhub/threads/web/fetch_post_comments | threads fetch_post_comments | from $0.002 |
| GET | tikhub/threads/web/fetch_post_detail | threads fetch_post_detail | from $0.002 |
| GET | tikhub/threads/web/fetch_user_info | threads fetch_user_info | from $0.002 |
| GET | tikhub/threads/web/fetch_user_info_by_id | threads fetch_user_info_by_id | from $0.002 |
| GET | tikhub/threads/web/fetch_user_posts | threads fetch_user_posts | from $0.002 |
| GET | tikhub/threads/web/fetch_user_replies | threads fetch_user_replies | from $0.002 |
| GET | tikhub/threads/web/fetch_user_reposts | threads fetch_user_reposts | from $0.002 |
| GET | tikhub/threads/web/search_profiles | threads search_profiles | from $0.002 |
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 Threads comes back with the same fields as one on X, so a prompt written for one platform works on the next.
