TikTok Place Info API

Endpoint facts

Method

GET

API path

/tiktok/mobile/place/info

Auth

apiKey

Credits

8 credits/request

Charged on

Successful 2xx responses only

Platform

TikTok

Execution

Managed browser rendering where the target needs it

Response schema

#/definitions/tiktokmobile.placeInfoResponseDoc

How this endpoint behaves

One place's compact record, keyed by the poi_id the place search endpoint returns. The upstream is TikTok's POI read GET /tiktok/poi/get/v1, captured from the running 47.4.3 app on the place detail screen and reproduced end-to-end against the live gateway. This is the record behind a place card — use it instead of the ~1 MB place detail page when you only need the place itself.

Typed fields plus the raw record. The response projects the fields callers key on (name, address, category, average_price, latitude/longitude, review_score with review_count and no_rating, video_count, favorite_count, opening_hours/opening_status, cover, share_url/share_desc, parent_poi, city_code/region_code) and also returns the upstream POI object unmodified in place, so a richer or newly added field is never lost.

Device-free. The route is not signature-value gated: the pure-Go placeholder signer returned the same record, so a deployment needs TIKTOK_MOBILE_PARAMS but not the device-backed signer (TIKTOK_MOBILE_SIGNER_URL). It answers on the core aggr16-normal.tiktokv.us / api16-normal-useast5.tiktokv.us pair (and also on aggr32/api32, so there is no required origin host like the slash detail page).

Query parameters:

• poi_id: required. The numeric place id from /api/v1/tiktok/mobile/search/place (poi_info rows).

Errors:

• 400 — poi_id is missing, non-numeric, or does not resolve. A nonexistent id answers the upstream business status 3009009 "poi not exist", which is a caller error here rather than an outage.
• 500 — the upstream failed.

Measured 2026-10-21 (placeholder/device-free signer, core pair):

Example request:

GET /api/v1/tiktok/mobile/place/info?poi_id=42203861086875992

Example response (truncated):

{
  "code": 200,
  "msg": "OK",
  "data": {
    "poi_id": "42203861086875992",
    "name": "Nam Coffee",
    "address": "304 Ord St, Los Angeles, CA 90012, USA",
    "category": "Coffee Shop",
    "average_price": "$",
    "latitude": "34.060090",
    "longitude": "-118.239007",
    "review_score": 4.7,
    "review_score_display": "4.7",
    "review_count": 2,
    "no_rating": false,
    "video_count": 11,
    "favorite_count": 1,
    "opening_hours": "8:00 AM – 5:00 PM",
    "opening_status": true,
    "cover": {"uri": "tiktok-obj/poi_detail_cover_3x.png", "url_list": ["..."]},
    "share_url": "https://www.tiktok.com/place/Nam-Coffee-42203861086875992",
    "share_desc": "Nam Coffee",
    "is_collected": false,
    "claim_store_status": false,
    "parent_poi": {"id": "22535796484723736", "keyword": "East Los Angeles", "scheme": "aweme://poi/detail"},
    "place": {"poi_name": "Nam Coffee", "collect_info": "{\"has_hours\":1,...}", "...": "the upstream POI object"},
    "host": "aggr16-normal.tiktokv.us",
    "fetched_at": "2026-10-21T16:22:08Z"
  }
}

Notes for callers:

• video_count is the app's own counter, not the length of the place video list: one measured place reported video_count: 0 while /api/v1/tiktok/mobile/place/videos returned 17 videos. Use the video list for the real set.
• opening_hours is the app's display string (OpeningHoursForPoiDetail); the structured flags live in the raw place.collect_info string and store_info.
• For the full place screen (top videos, posts, review preview, photo album nodes) use place detail; for just the photos use place photos.

Shared guides

Related