Platforms, unified entities, vendor APIs, endpoints and connectors.
commerce.live_streamUnifiedSoonOne shoppable live session: the creator, the products on sale and what it sold.
key platform + live IDSame as Post4 planned calls3 Direct endpoints today
Calls from commerce API design 0.1.0-draft, written as REST paths. Each call returns this entity in one shape on the platforms it lists, and none is deployed yet.
/ v1/ e-commerce/ tiktok-shop/ livestreams/ {livestreamId}One past live sessionTikTok ShopFields pending/ v1/ e-commerce/ tiktok-shop/ livestreams/ searchFilter past live sessionsTikTok ShopFields pending/ v1/ e-commerce/ tiktok-shop/ livestreams/ rankingsLive sessions in the source's own order, not a platform rankingTikTok ShopFields pending/ v1/ e-commerce/ tiktok-shop/ livestreams/ trendsSnapshots of one live session over timeTikTok ShopFields pendingThe design reserves the paths; the fields come in a later draft.
The fields of LiveStream are not designed yet. Only the paths of the calls above are reserved.
Vendor endpoints that already return this kind of object, in the vendor's own format. Your code names the vendor, so switching vendors means changing it.
3 endpoints from 1 API · from $0.001
| API | Method | Path | Endpoint | Price |
|---|---|---|---|---|
| TikHub | GET | tikhub/tiktok/app/v3/fetch_live_room_info | tiktok fetch_live_room_info | from $0.001 |
| TikHub | GET | tikhub/tiktok/web/fetch_user_live_detail | tiktok fetch_user_live_detail | from $0.001 |
| TikHub | GET | tikhub/tiktok/app/v3/fetch_live_room_product_list | tiktok fetch_live_room_product_list | from $0.001 |
Each link is a field you can ask for in the same call.