Skip to navigation

Where to get Douyin videos, comments and account data

Where you get Douyin data depends on whose videos you study. For your own videos, start in Creator Center. For an app that reads a user’s videos, check the account grant and the app’s approved permissions in the Douyin developer console. For public videos from other creators, open known links or search one page with BeatAPI’s douyin.search.fetch_general_search_v2, then fetch comments for the videos you choose.

Start with account analytics or app authorization

  • Owned account. In Douyin Creator Center, select the account and the time window, open the video analytics, and check how each report defines plays and engagement. For attribution, use the Xingtu campaign report you can access, and keep the project and the attribution window with the numbers. Douyin Creator Center · Xingtu campaign reports
  • Application reading an authorized account. In the developer console, check the application type, the approved capabilities and the user’s grant. The official docs describe an authorized-account video list; interaction metrics and comment management are separate capabilities, so check each capability. Test with one video published by the authorized account, and record the response status, item identifier, fields and access scope. Authorized video list · Video comment management
  • Public keyword search. Douyin’s search product page takes applications for a search beta, and Douyin’s developer guide describes search as experimental. Check your application’s eligibility, approval and scope in the console. Comment access for videos found by keyword search is a separate permission; check the comment permission separately. Douyin search product · Developer search guide · Keyword video comments

For the app test, use the identifier from the official app response. For BeatAPI public research, use the aweme_id the chosen BeatAPI action requires. Keep the official identifier and the BeatAPI identifier in separate columns.

Use a public sample to understand user questions

To search public videos, POST to https://api.beatapi.io/v1/social-data/call with Authorization: Bearer <BEATAPI_API_KEY> and Content-Type: application/json. The example below searches the first page of videos about rental storage from the past week.

{"action":"douyin.search.fetch_general_search_v2","params":{"keyword":"租房收纳","cursor":0,"sort_type":"0","publish_time":"7","filter_duration":"0","content_type":"1","search_id":"","backtrace":""}}

From a successful response, check which videos actually match the topic. Record the search term, the filters, the video identifiers and the request ID. Save one video’s source and read the video’s top-level comments; open replies when context matters. Report the questions the sample supports, and list the videos and comment pages you checked.

If a teammate shares one public video, save the link and request comments by the video’s post ID. If you start from an account list, verify each account ID and decide which publication period to review. For keyword discovery, save the query and filters with each batch, so every lead can be traced back to the search that found the lead.

Decide what one row of your export represents

OutputOne row representsWhere to start
Creator inventoryA post with its ID, publish time and available metricsPost CSV and XLSX
Viewer questionsA comment with its video and relevant reply contextComments and export
Keyword shortlistA selected video with query and selection reasonPython search and comments
Creator comparisonA candidate account and selected partnership examplesCreator and campaign research
Topic trendsAn observation for a term or topicTrends and search indices

Keep the original responses with each sheet. In a home-organization review, join the creator inventory to the viewer-question table by post ID. Keep creator profiles by account, and keep index snapshots by observation date.

Example: What renter storage video should you make next week?

  1. In your own report, choose one week and check the publication dates and reporting windows of two related videos.
  2. In public search, select two videos that actually cover renter storage. Save the two video IDs and read the comments to see where viewers get stuck.
  3. If both videos have questions about storage without drilling holes, include two original comments with the videos’ links and suggest a no-drill storage tutorial.
  4. Record the number of videos and comment pages reviewed, so someone can expand the sample next week.

If the search mostly returns product promotions, search a more specific phrase about rental storage without drilling. Save both search terms so readers can see how you selected the examples.

Use owned analytics to report performance, and use the public sample to find content opportunities. Keep each source’s metric labels and observation times. Search pages and comment requests are priced separately. Search and comments workflow · BeatAPI pricing