# 获取作品观看趋势分析/Fetch item watch trend analysis ## OpenAPI Specification ```yaml openapi: 3.0.1 info: title: '' description: '' version: 1.0.0 paths: /api/v1/douyin/creator_v2/fetch_item_watch_trend: post: summary: 获取作品观看趋势分析/Fetch item watch trend analysis deprecated: false description: >- # [中文] ### 用途: - 获取抖音作品的观看趋势分析数据 - 了解用户在观看作品时的行为模式 - 帮助创作者优化视频内容结构和节奏 - **此接口需要用户提供有效的抖音创作者平台Cookie** - **使用 POST 方法，Cookie 在请求体中传输，更安全** ### 请求体参数: - cookie: 用户的抖音创作者平台Cookie（必填，在请求体中传输） - item_id: 作品ID（必填） - analysis_type: 分析类型（可选，默认为1） - **1**: 留存分析 - 显示用户在各个时间点的留存情况 - **2**: 点赞分析 - 显示用户在各个时间点的点赞情况 - **7**: 跳出分析 - 显示用户在各个时间点的跳出情况 ### 分析类型说明: - **留存分析 (analysis_type=1)**: - 展示观众在视频各时间点的留存比例 - 留存率越高，说明该时间段内容越吸引人 - **注意**: 播放量超过200后，数据更准确 - 适合分析：哪些片段吸引观众持续观看 - **点赞分析 (analysis_type=2)**: - 展示观众在视频各时间点的点赞比例 - 点赞率高的时间点说明该片段特别受欢迎 - 适合分析：哪些片段最能引发用户互动 - **跳出分析 (analysis_type=7)**: - 展示观众在视频各时间点的跳出比例 - 跳出率高的时间点可能存在内容问题 - 适合分析：哪些片段导致观众离开 ### 返回数据说明: - analysis_trend: 趋势分析数据 - current_item: 当前作品的数据点列表 - key: 时间点（格式：mm:ss，如 "00:05" 表示第5秒） - value: 该时间点的比例值（0-1之间的小数） - similar_author: 同类作者的平均数据（用于对比） - key: 时间点 - value: 同类作者在该时间点的平均比例 ### 数据价值: - **内容优化**: 识别观众流失的关键时间点 - **节奏调整**: 优化视频的起承转合节奏 - **对比分析**: 与同类作者对比，找出差距和优势 - **A/B测试**: 测试不同版本的内容效果 ### Cookie 获取方式: 1. 登录抖音创作者平台 (https://creator.douyin.com) 2. 打开浏览器开发者工具（F12） 3. 切换到 Network 标签 4. 刷新页面或进行操作 5. 找到任意请求，复制 Cookie 请求头的值 # [English] ### Purpose: - Get Douyin item watch trend analysis data - Understand user behavior patterns while watching the item - Help creators optimize video content structure and pacing - **This API requires users to provide valid Douyin Creator Platform Cookie** - **Use POST method, Cookie is transmitted in request body, more secure** ### Request Body Parameters: - cookie: User's Douyin Creator Platform Cookie (required, transmitted in request body) - item_id: Item ID (required) - analysis_type: Analysis type (optional, default is 1) - **1**: Retention Analysis - Shows user retention at each time point - **2**: Like Analysis - Shows user like behavior at each time point - **7**: Bounce Analysis - Shows user bounce rate at each time point ### Analysis Type Description: - **Retention Analysis (analysis_type=1)**: - Shows viewer retention rate at various video time points - Higher retention means more engaging content at that moment - **Note**: Data is more accurate when views exceed 200 - Good for: Identifying which segments keep viewers watching - **Like Analysis (analysis_type=2)**: - Shows viewer like rate at various video time points - Higher like rate indicates particularly popular segments - Good for: Identifying segments that drive user engagement - **Bounce Analysis (analysis_type=7)**: - Shows viewer bounce rate at various video time points - High bounce rate indicates potential content issues - Good for: Identifying segments that cause viewers to leave ### Return Data Description: - analysis_trend: Trend analysis data - current_item: Data points for current item - key: Time point (format: mm:ss, e.g., "00:05" for 5 seconds) - value: Proportion at this time point (decimal between 0-1) - similar_author: Average data from similar authors (for comparison) - key: Time point - value: Average proportion at this time point ### Data Value: - **Content Optimization**: Identify key drop-off points - **Pacing Adjustment**: Optimize video rhythm and flow - **Comparative Analysis**: Compare with similar creators to find gaps - **A/B Testing**: Test different content versions ### How to get Cookie: 1. Login to Douyin Creator Platform (https://creator.douyin.com) 2. Open browser developer tools (F12) 3. Switch to Network tab 4. Refresh page or perform operations 5. Find any request and copy the Cookie header value # [示例/Example] ```json { "cookie": "Your_Cookie_Here", "item_id": "7559536212910853422", "analysis_type": 1 } ``` ### 返回数据示例/Response Example: ```json { "analysis_trend": { "current_item": [ { "key": "00:00", "value": 0.2653 }, { "key": "00:01", "value": 0.2653 }, { "key": "00:05", "value": 0.0272 }, { "key": "00:10", "value": 0.1429 } ], "similar_author": [ { "key": "00:00", "value": 0.1594 }, { "key": "00:01", "value": 0.2229 } ] }, "status_code": 0, "status_msg": "" } ``` ### 数据解读/Data Interpretation: **留存分析 (Retention)**: - value 值表示该时间点的留存比例 - 数值越高表示越多观众看到这个时间点 - 对比 current_item 和 similar_author 可以看出作品表现 - 留存曲线下降陡峭说明内容吸引力不足 **点赞分析 (Like)**: - value 值表示该时间点的点赞比例 - 数值越高表示该时间段内容越能引发点赞 - 点赞高峰通常出现在高潮、反转、笑点等位置 - 可以帮助识别最有价值的内容片段 **跳出分析 (Bounce)**: - value 值表示该时间点的跳出比例 - 数值越高表示越多观众在此时离开 - 跳出率高的时间点需要重点优化 - 开头几秒的跳出率尤其重要 ### 优化建议/Optimization Suggestions: 1. **前3秒黄金法则**: 确保开头吸引眼球，降低初期跳出 2. **节奏把控**: 在留存率下降前插入高潮或转折 3. **时长优化**: 根据留存曲线调整视频时长 4. **点赞热点**: 在点赞率高的时间段前后放置核心内容 5. **对标学习**: 参考 similar_author 数据优化内容 6. **持续测试**: 不同类型内容的最佳节奏不同 ### 注意事项/Notes: - 播放量超过 200 后，留存分析数据更准确 - 数据可能有延迟，建议作品发布一段时间后查看 - 结合其他指标（完播率、互动率）综合分析 operationId: >- fetch_item_watch_trend_api_v1_douyin_creator_v2_fetch_item_watch_trend_post tags: - Douyin-Creator-V2-API - Douyin-Creator-V2-API parameters: [] requestBody: content: application/json: schema: $ref: '#/components/schemas/ItemWatchTrendRequest' description: 作品观看趋势分析请求参数/Item watch trend analysis request parameters example: cookie: Your_Cookie_Here item_id: '7559536212910853422' analysis_type: 1 responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/ResponseModel' headers: {} x-apifox-name: OK '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' headers: {} x-apifox-name: Unprocessable Entity security: - HTTPBearer: [] x-apifox: schemeGroups: - id: zkhm2Ymi1Tgld9xrud3Zn schemeIds: - HTTPBearer required: true use: id: zkhm2Ymi1Tgld9xrud3Zn scopes: zkhm2Ymi1Tgld9xrud3Zn: HTTPBearer: [] x-apifox-folder: Douyin-Creator-V2-API x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-359719864-run components: schemas: ItemWatchTrendRequest: properties: cookie: type: string title: Cookie description: 用户Cookie/User Cookie examples: - Your_Cookie_Here item_id: type: string title: Item Id description: 作品ID/Item ID examples: - '7559536212910853422' analysis_type: type: integer title: Analysis Type description: '分析类型/Analysis type: 1=留存分析(Retention), 2=点赞分析(Like), 7=跳出分析(Bounce)' default: 1 examples: - 1 type: object required: - cookie - item_id title: ItemWatchTrendRequest description: |- 作品观看趋势分析请求模型 Item Watch Trend Analysis Request Model x-apifox-orders: - cookie - item_id - analysis_type x-apifox-ignore-properties: [] x-apifox-folder: '' ResponseModel: properties: code: type: integer title: Code description: HTTP status code | HTTP状态码 default: 200 request_id: anyOf: - type: string - type: 'null' title: Request Id description: Unique request identifier | 唯一请求标识符 message: type: string title: Message description: Response message (EN-US) | 响应消息 (English) default: Request successful. This request will incur a charge. message_zh: type: string title: Message Zh description: Response message (ZH-CN) | 响应消息 (中文) default: 请求成功，本次请求将被计费。 support: type: string title: Support description: Support message | 支持消息 default: 'Discord: https://discord.gg/aMEAS8Xsvz' time: type: string title: Time description: The time the response was generated | 生成响应的时间 time_stamp: type: integer title: Time Stamp description: The timestamp the response was generated | 生成响应的时间戳 time_zone: type: string title: Time Zone description: The timezone of the response time | 响应时间的时区 default: America/Los_Angeles docs: anyOf: - type: string - type: 'null' title: Docs description: >- Link to the API Swagger documentation for this endpoint | 此端点的 API Swagger 文档链接 cache_message: anyOf: - type: string - type: 'null' title: Cache Message description: Cache message (EN-US) | 缓存消息 (English) default: >- This response is cached and accessible via the URL below for 24 hours at no extra cost. The cache is for request tracing only — it doesn't affect the API's data freshness and won't be returned through the API again. cache_message_zh: anyOf: - type: string - type: 'null' title: Cache Message Zh description: Cache message (ZH-CN) | 缓存消息 (中文) default: >- 本次响应已缓存，可通过下方 URL 直接查看，有效期 24 小时，访问缓存链接无额外费用。缓存仅用于请求溯源，不影响接口数据的时效性，也不会再次通过接口返回。 cache_url: anyOf: - type: string - type: 'null' title: Cache Url description: The URL to access the cached result | 访问缓存结果的 URL router: type: string title: Router description: The endpoint that generated this response | 生成此响应的端点 default: '' params: type: string data: anyOf: - type: string - type: 'null' title: Data description: The response data | 响应数据 type: object title: ResponseModel x-apifox-orders: - code - request_id - message - message_zh - support - time - time_stamp - time_zone - docs - cache_message - cache_message_zh - cache_url - router - params - data x-apifox-ignore-properties: [] x-apifox-folder: '' HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError x-apifox-orders: - detail x-apifox-ignore-properties: [] x-apifox-folder: '' ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError x-apifox-orders: - loc - msg - type x-apifox-ignore-properties: [] x-apifox-folder: '' securitySchemes: HTTPBearer: type: bearer description: > ---- #### API Token Introduction: ##### Method 1: Use API Token in the Request Header (Recommended) - **Header**: `Authorization` - **Format**: `Bearer {token}` - **Example**: `{"Authorization": "Bearer your_token"}` - **Swagger UI**: Click on the `Authorize` button in the upper right corner of the page to enter the API token directly without the `Bearer` keyword. ##### Method 2: Use API Token in the Cookie (Not Recommended, Use Only When Method 1 is Unavailable) - **Cookie**: `Authorization` - **Format**: `Bearer {token}` - **Example**: `Authorization=Bearer your_token` #### Get API Token: 1. Register and log in to your account on the TikHub website. 2. Go to the user center, click on the API token menu, and create an API token. 3. Copy and use the API token in the request header. 4. Keep your API token confidential and use it only in the request header. ---- #### API令牌简介: ##### 方法一：在请求头中使用API令牌（推荐） - **请求头**: `Authorization` - **格式**: `Bearer {token}` - **示例**: `{"Authorization": "Bearer your_token"}` - **Swagger UI**: 点击页面右上角的`Authorize`按钮，直接输入API令牌，不需要`Bearer`关键字。 ##### 方法二：在Cookie中使用API令牌（不推荐，仅在无法使用方法一时使用） - **Cookie**: `Authorization` - **格式**: `Bearer {token}` - **示例**: `Authorization=Bearer your_token` #### 获取API令牌: 1. 在TikHub网站注册并登录账户。 2. 进入用户中心，点击API令牌菜单，创建API令牌。 3. 复制并在请求头中使用API令牌。 4. 保密您的API令牌，仅在请求头中使用。 scheme: bearer servers: - url: https://api.tikhub.io description: Production Environment security: [] ```