Nexscope

ET TikTok Category Trend

Read one page of TikTok category daily trends for a region and date range, optionally filtered by first, second or third-level category IDs.

CostAt least 10 credits / call
Try online
POST · https://api.nexscope.ai/et/category/trendMCP · nexscope_data_et_category_trend

What this API does

Read one page of TikTok category daily trends for a region and date range, optionally filtered by first, second or third-level category IDs. The request accepts categoryId, categoryL2Id, categoryL3Id, region, startDate. Its documented result includes errcode.

ET TikTok Category Trend API use cases

Shortlist a market segment

To shortlist a market segment, a marketplace analyst submits categoryId and categoryL2Id to ET TikTok Category Trend. The returned errcode help identify categories or products worth further market research.

Compare ranked products or categories

A marketplace analyst uses ET TikTok Category Trend with categoryId and categoryL2Id to compare ranked products or categories. The returned errcode help compare candidates within the requested ranking scope.

Investigate candidates before sourcing

For this workflow, a marketplace analyst calls ET TikTok Category Trend with categoryId and categoryL2Id to investigate candidates before sourcing. The result helps choose products to investigate before contacting suppliers.

ET TikTok Category Trend API FAQ

What does the ET TikTok Category Trend API return?

Read one page of TikTok category daily trends for a region and date range, optionally filtered by first, second or third-level category IDs. The documented output includes errcode. It corresponds to the supplied categoryId, categoryL2Id, categoryL3Id, region, startDate. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the ET TikTok Category Trend API cost?

The current documented cost is At least 10 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the ET TikTok Category Trend API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/et/category/trend with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_data_et_category_trend. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/et/category/trend
MCP method
nexscope_data_et_category_trend

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx
Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/et/category/trend

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/et/category/trend' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "endDate": "2026-11-07",
  "region": "US",
  "startDate": "2026-11-01"
}'

Code example

{
  "endDate": "2026-11-07",
  "region": "US",
  "startDate": "2026-11-01"
}

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.
All categories/ TikTok Intelligence ET
POSThttps://api.nexscope.ai/et/category/trend

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/et/category/trend
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
categoryIdstringoptional
Optional category ID.
categoryL2Idstringoptional
Optional category ID.
categoryL3Idstringoptional
Optional category ID.
regionstringrequired
Two-letter uppercase region.
Example: US
startDatestringrequired
Start date, yyyy-MM-dd.
Example: 2026-11-01
endDatestringrequired
End date, yyyy-MM-dd.
Example: 2026-11-07
pageNumintegeroptional
One page per call.
pageSizeintegeroptional
Records per page, at most 10.

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

No response example is published for this API. Refer to the response fields below.

Response fields

Response field reference (2 fields)

NameTypeRequiredDescription
dataarrayoptional
-
errcodeintegerrequired
-

Responses

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json
Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_data_et_category_trend",
    "arguments": {
      "endDate": "2026-11-07",
      "region": "US",
      "startDate": "2026-11-01"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

How can I inspect TikTok category trends?

AI answer

Workflow example: choose a region and date range, optionally narrow by first-, second-, or third-level category ID, and request pages within a fixed limit. Daily values and pagination must be read from the actual response. No verified trend result is published for this page.

Practical use cases:

  1. Review category daily trends — Show daily TikTok category trends in [REGION] from [START_DATE] to [END_DATE]. Return the available daily values for the first page.
  2. Narrow trends by category level — Show the daily trend in [REGION] for [CATEGORY_PATH] over [DATE_RANGE]. Use the matching first-, second-, or third-level IDs that I provide and keep each level distinct.
  3. Review a bounded trend period — Review at most [PAGE_LIMIT] pages of daily category trends in [REGION] over [DATE_RANGE]. Stop when the returned pagination ends, and do not describe one page as the full period.

Related APIs