TikHub Complete (149 Endpoints) icon

TikHub Complete (149 Endpoints)

Access ALL 149 TikHub social media data endpoints for TikTok (64), Instagram (56), YouTube (16), and X/Twitter (13)

Actions64

Overview

This node, named "TikHub Complete (149 Endpoints)," provides unified access to a wide range of social media data endpoints across four major platforms: TikTok, Instagram, YouTube, and X/Twitter. It supports 64 TikTok endpoints, 56 Instagram endpoints, 16 YouTube endpoints, and 13 X/Twitter endpoints, enabling users to retrieve diverse data such as videos, user profiles, analytics, posts, stories, reels, channels, tweets, timelines, and search results.

The specific operation "Get music search results of specified keywords" under the "Default" resource allows users to perform keyword-based searches for music-related content on TikTok. This is useful for marketers, content creators, analysts, or developers who want to gather trending music data, analyze popular sounds, or integrate music search capabilities into their workflows.

Practical examples:

  • A marketer searching for trending TikTok music clips related to a campaign keyword.
  • A developer building an app that recommends TikTok songs based on user input keywords.
  • An analyst tracking the popularity and spread of certain music tracks on TikTok over time.

Properties

Name Meaning
Platform Select the social media platform to work with. Options: TikTok, Instagram, YouTube, X/Twitter
关键词/Keyword The keyword(s) to search for music content on TikTok. Required.
偏移量/Offset Offset for pagination in search results. Optional; minimum 1, maximum 1000. Default is 20.
数量/Number Number of results to return. Optional; minimum 1, maximum 1000. Default is 20.
排序类型/Sort type Sort type parameter to order the search results. Optional; numeric value between 1 and 1000.
发布时间/Publish time Filter results by publish time. Optional; numeric value between 1 and 1000.
根据粉丝数排序/Sort by number of followers Sort results based on the number of followers of the user. Optional string.
根据账号类型排序/Sort by account type Sort results based on the account type. Optional string.
根据其他偏好排序/Sort by other preferences Sort results based on other user-defined preferences. Optional string.

Note: All properties except "Platform" and "Keyword" are optional and mostly relate to filtering, sorting, and pagination of the search results.

Output

The node outputs JSON data representing the search results returned from the TikHub API for the specified music keyword search on TikTok. The output structure corresponds directly to the API response's data field, which typically includes arrays of music items matching the search criteria along with metadata such as counts, offsets, and possibly pagination tokens.

If the API returns binary data (not indicated here), it would be handled accordingly, but this operation primarily deals with JSON search result data.

Each item in the output array is enriched with execution metadata linking it back to the input item index for traceability within n8n workflows.

Dependencies

  • Requires an API key credential for the TikHub service to authenticate requests.
  • The node uses the TikHub API base URL: https://api.tikhub.io.
  • No additional external dependencies beyond the TikHub API and standard n8n workflow helpers.

Troubleshooting

  • Unknown operation error: If the operation name does not match any known endpoint, the node throws an error indicating an unknown operation for the selected platform. Ensure the operation parameter is correctly set to "searchresult" for this use case.
  • Missing required parameters: The "Keyword" property is mandatory. Omitting it will likely cause the API request to fail or return no results.
  • API rate limits or authentication errors: If the API key is invalid or rate limits are exceeded, the node will throw errors. Verify the API key credential and monitor usage.
  • Empty or unexpected results: Check the offset, count, and filter parameters to ensure they are within valid ranges and logically consistent.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion