TikTok Creator Recommendations API

Endpoint facts

Method

GET

API path

/tiktok/mobile/user/recommendations

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.userRecommendationsResponseDoc

How this endpoint behaves

Creator discovery: the suggested accounts the mobile app shows on its Following page, each with up to three recent videos. The route was captured from the running app (GET /aweme/v1/following/page/user/recommend/ with recommend_reason_type=combined first in the query) and then reproduced end-to-end against the live gateway, so the request and the response shape are measured.

user_list is not a bare id list. Every entry is {user, aweme_list}: the full creator projection in user (uid, sec_uid, nickname, signature, avatars, follower_count/following_count, verification and privacy flags — 46 keys measured) and up to three recent videos in aweme_list (full item objects, measured 0–3 per entry). That makes this a creator-discovery surface rather than another video feed.

No paging. The measured envelope carries no cursor, no has_more and no max_time; the route returns one page of 13–17 creators. Recommendations differ between calls, so the server draws a fresh set per request.

Device-free. Unlike the profile/posts/video/search-item routes, this route is not signature-value gated: the same request signed with the pure-Go placeholder signer returned the same real data, so the deployment does not need the device-backed signer (TIKTOK_MOBILE_SIGNER_URL) for this endpoint.

Query parameters:

• count: optional. Requested page size, sanity-bounded at 50 and forwarded only when set. The gateway was measured to ignore it: count=5 returned 16 creators and count=30 returned 17, i.e. the same page as the app's own call, which carries no count at all. Treat it as shape parity, not a page-size control.

Measured 2026-10-21 against the live gateway (aggr16-normal.tiktokv.us edge / api16-normal-useast5.tiktokv.us origin):

One measured variant matters for the contract: without recommend_reason_type=combined the same route answers 44 bare users whose aweme_list is empty (4,006,767 B in one measurement). This endpoint always sends the app's combined value, because the app itself never calls the route without it and the video-bearing form is the product surface.

Notable response behavior:

• Rows are opaque ([]any), so a richer creator or video object never loses fields to an incomplete schema.
• The 3.9 MB measured body is the largest single page this family returns outside the catalogue routes and stays well under the family's 8 MiB response cap.
• A non-zero upstream status_code surfaces as a typed upstream error rather than an empty page.

Example request:

GET /api/v1/tiktok/mobile/user/recommendations

Example response (truncated):

{
  "code": 200,
  "msg": "OK",
  "data": {
    "user_list": [
      {
        "user": {
          "uid": "7534288336598008838",
          "sec_uid": "MS4wLjABAAAA...",
          "nickname": "example creator",
          "signature": "example bio",
          "follower_count": 1200,
          "following_count": 34
        },
        "aweme_list": [
          {"aweme_id": "7516855864041540878", "desc": "recent video one"},
          {"aweme_id": "7516855864041540879", "desc": "recent video two"},
          {"aweme_id": "7516855864041540880", "desc": "recent video three"}
        ]
      }
    ],
    "extra": {"logid": "20261021052839295FD62E359E0309373B", "now": 1792560520000},
    "log_pb": {"impr_id": "20261021052839295FD62E359E0309373B"},
    "status_code": 0,
    "status_msg": ""
  }
}

Shared guides

Related