Douyin Creator Marketplace (Xingtu) Item Report Trends

Use this focused JustOneAPI skill for item Report Trends in Douyin Creator Marketplace (Xingtu). It targets GET /api/douyin-xingtu/gw/api/data_sp/item_report_trend/v1. Required non-token inputs are itemId. OpenAPI describes it as: Get Douyin Creator Marketplace (Xingtu) item Report Trend data, including time-based changes in item performance metrics, for creator evaluation, campaign planning, and marketplace research.

Endpoint Scope

• Platform key: douyin-xingtu
• Endpoint key: gw/api/data_sp/item_report_trend
• Platform family: Douyin Creator Marketplace (Xingtu)
• Skill slug: justoneapi-douyin-xingtu-gw-api-data-sp-item-report-trend

Inputs

Request body: none documented; send parameters through path or query arguments.

Version Choice

Use gwApiDataSpItemReportTrendV1 for the documented v1 endpoint. There are no alternate versions grouped in this skill.

Run This Endpoint

Supported operation IDs in this skill: gwApiDataSpItemReportTrendV1.

node {baseDir}/bin/run.mjs --operation "gwApiDataSpItemReportTrendV1" --token "$JUST_ONE_API_TOKEN" --params-json '{"itemId":"<itemId>"}'

Ask for any missing required parameter before calling the helper. Keep user-provided IDs, cursors, keywords, and filters unchanged.

Environment

• Required: JUST_ONE_API_TOKEN
• Pass the token with --token "$JUST_ONE_API_TOKEN"; do not paste token values into chat messages, screenshots, or logs.
• Get a token from Just One API Dashboard.
• Authentication details: Just One API Usage Guide.

Output Focus

• State the operation ID and endpoint path used, for example gwApiDataSpItemReportTrendV1 on /api/douyin-xingtu/gw/api/data_sp/item_report_trend/v1.
• Echo the required lookup scope (itemId) before summarizing results.
• Prioritize fields that support this endpoint purpose: Get Douyin Creator Marketplace (Xingtu) item Report Trend data, including time-based changes in item performance metrics, for creator evaluation, campaign planning, and marketplace research.
• Return raw JSON only after the short, endpoint-specific summary.
• If the backend errors, include the backend payload and the exact operation ID.