TikTok Trending Hashtags API docs

Open Playground →

Start building

Send your first request

Platform API endpoint with unified authentication and usage tracking.

Production API
Platform API endpoint
https://api.sandbase.ai/v1/api/tiktok/trending-hashtags
Authorization header
Authorization: Bearer $SANDBASE_API_KEY
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
  -X POST "https://api.sandbase.ai/v1/api/tiktok/trending-hashtags" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'SANDBASE_JSON'
{
  "limit": 3,
  "period": 7,
  "region": "US"
}
SANDBASE_JSON
)
printf '%s\n' "$result"

2. Authentication

Set your SandBase API key in your server environment. Requests use Bearer authentication.

API key environment variable
export SANDBASE_API_KEY="YOUR_API_KEY"

Keep your key on the server. Do not expose it in browser code.

3. Parameters

limitinteger

Maximum number of ranked hashtags to return, from 1 through 100 (default 3). TikTok publishes only the top 3 hashtags per board to anonymous callers, so 1 through 3 is served by the cheapest source; a higher limit routes to a dearer source that reads the full ranking.

Default: 3

periodinteger

Lookback window in days that the ranking and the popularity curve cover (default 7).

Default: 7

Possible values: 7, 30, 90

regionstring

Two-letter country code of the market whose hashtag ranking to read (default US). Each market is ranked independently, so US and DE return different boards.

Default: "US"

Possible values: US, FR, DE, IT, ES, GB, AR, AU, BR, CA, CO, EG, ID, IL, JP, KR, MY, MX, PH, SA, SG, ZA, TW, TH, TR, AE, VN

industrystring

Restrict the ranking to one industry. Omit for the all-industries board.

Possible values: apparel_accessories, baby_kids_maternity, beauty_personal_care, education, food_beverage, games, health, home_improvement, household_products, news_entertainment, pets, sports_outdoor, tech_electronics, travel, vehicle_transportation

requireFieldsarray

Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `industryIds`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a hashtag that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.

4. Response

Saved example response for this API; no live request is made when viewing it.

No saved response has been published. Run the API in Playground to inspect its response.