logo
EN

TikTok User Video List

Submit a TikTok username and retrieve its collected video records after the collection task finishes

Data collectionSocial MediaTikTokVideos
Developer
hello_moto
Pricing
From $0.002 / 35 records
Last updated
2026-10-12

Overview

Want a structured list of videos associated with a TikTok user? Give it a TikTok username and a target collection count, and it returns the video records produced by the completed collection task, including content IDs, collection time, username, keyword type, and task metadata.

Data notes

The target count is a collection target rather than a strict cap, so the actual number of returned records may differ. Results are retrieved through the upstream service's paginated video-list endpoint. Fields that the upstream service cannot provide for a record may be empty, and task metadata indicates the source item and whether no data was found.

What the results look like

Each record represents one collected TikTok video:

Video content IDCollection timeTikTok usernameKeyword typeTask itemNo data
76841770720124306122026-09-21T12:03:12snaiksevenaccountsnaiksevenfalse

Use cases

  • Build a TikTok account content inventory using Video content ID and Collection time.
  • Compare account-level collection results using TikTok username and Keyword type.
  • Identify empty or unavailable account results with Task item and No data.

Scope and boundaries

One TikTok username per task; crawlNum is a target count rather than a strict cap, and results are retrieved in pages of up to 1,000 records.

  • Good for
  • When you need a structured list of videos associated with a TikTok user account for analysis or monitoring.
  • Do not use for
  • When you need a synchronous single-video lookup or private account data that the upstream service cannot collect.

Failure handling

Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.

  1. 1If the task fails or expires, resubmit the same username after checking the account input.
  2. 2If fewer records than the target are returned, treat the result as the upstream collection outcome rather than retrying solely to force the target count.

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

  • TikTok usernameaccountRequiredstring
    TikTok username to collect videos from.
    Examplesnaikseven
  • Target video countcrawl_numOptionalinteger
    Target number of videos to collect. This is a target, not a strict upper limit; the actual returned count may differ.
    Example50

Output

Field structure of a single record, generated from the output.schema in manifest.json.

  • Video content IDcontent_idstring
    Unique identifier of the TikTok video when available.
    Example7684177072012430612
  • Collection timecrawl_timestring
    Time when the video record was collected, when available.
    Example2026-09-21T12:03:12
  • TikTok usernamekeywordstring
    TikTok username associated with the collected record, when available.
    Examplesnaikseven
  • Keyword typekeyword_typestring
    Type of the collection keyword reported by the upstream service.
    Exampleaccount

Sample data

Generated from output.schema. Fields without a sample value use structural placeholders.

output.example
{
  "content_id": "7684177072012430612",
  "crawl_time": "2026-09-21T12:03:12",
  "keyword": "snaikseven",
  "keyword_type": "account",
  "task_meta": "<task_meta>"
}

Integration

This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.

With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.

Client config

Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=hello_moto/tiktok-user-video-list",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}
View my API Keys →

Let AI set it up for you

Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (The prompt asks the AI to request your API key from you, so credentials never end up in chat history or shared configs.)

detail.access.mcp.composeHint

Pricing

Submit one collection task

Charged once per submitted run, regardless of how many records are returned.

$0.0001/ run
Return 35 video record

Charged by the number of records successfully returned. Failed runs are not charged. Billed in units of 35 records; any partial unit is rounded up to 35 records.

$0.002/ 35 records

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
From $0.002 / 35 records