# 获取作品弹幕分析/Fetch item bullet analysis ## OpenAPI Specification ```yaml openapi: 3.0.1 info: title: '' description: '' version: 1.0.0 paths: /api/v1/douyin/creator_v2/fetch_item_danmaku_analysis: post: summary: 获取作品弹幕分析/Fetch item bullet analysis deprecated: false description: >- # [中文] ### 用途: - 获取抖音作品的弹幕分析数据 - 了解观众在视频各个时间点的弹幕互动情况 - 帮助创作者识别视频中的热点片段和观众反应 - **此接口需要用户提供有效的抖音创作者平台Cookie** - **使用 POST 方法，Cookie 在请求体中传输，更安全** ### 请求体参数: - cookie: 用户的抖音创作者平台Cookie（必填，在请求体中传输） - item_id: 作品ID（必填） ### 返回数据说明: 返回作品的弹幕分析数据，包括： - bullet_distribution: 弹幕分布数据 - time_point: 时间点（秒） - count: 该时间点的弹幕数量 - percentage: 该时间点弹幕占总弹幕的百分比 - hot_words: 热门弹幕词汇 - word: 弹幕词汇 - count: 出现次数 - sentiment: 情感倾向（正面/负面/中性） - total_count: 弹幕总数 - peak_time: 弹幕高峰时间点 **注意**: 如果返回空数据或弹幕数量为0，说明该作品目前没有弹幕数据，可能原因： - 作品刚发布，还没有观众发送弹幕 - 作品类型不适合弹幕互动 - 弹幕功能未开启 ### 数据价值: - **热点识别**: 识别观众最感兴趣的视频片段 - **情感分析**: 了解观众对内容的情感反应 - **互动优化**: 在高弹幕区域优化内容呈现 - **内容改进**: 根据弹幕反馈调整后续内容 ### 应用场景: 1. **内容优化**: 找出观众最喜欢的片段，在后续视频中强化类似内容 2. **节奏调整**: 弹幕密集的时间点说明内容吸引人，可以延长类似内容时长 3. **情感把控**: 通过弹幕情感分析了解观众真实反应 4. **互动设计**: 在弹幕高峰处设计互动环节，提升参与度 ### Cookie 获取方式: 1. 登录抖音创作者平台 (https://creator.douyin.com) 2. 打开浏览器开发者工具（F12） 3. 切换到 Network 标签 4. 刷新页面或进行操作 5. 找到任意请求，复制 Cookie 请求头的值 # [English] ### Purpose: - Get Douyin item bullet (danmaku) analysis data - Understand audience bullet interaction at various video time points - Help creators identify hot segments and audience reactions - **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) ### Return Data Description: Returns item bullet analysis data, including: - bullet_distribution: Bullet distribution data - time_point: Time point (seconds) - count: Number of bullets at this time point - percentage: Percentage of bullets at this time point - hot_words: Popular bullet words - word: Bullet word - count: Occurrence count - sentiment: Sentiment orientation (positive/negative/neutral) - total_count: Total bullet count - peak_time: Peak time point for bullets **Note**: If empty data or zero bullets returned, it means there is currently no bullet data for this item, possible reasons: - Item was just published and no viewers have sent bullets yet - Item type is not suitable for bullet interaction - Bullet feature is not enabled ### Data Value: - **Hot Spot Identification**: Identify video segments with highest audience interest - **Sentiment Analysis**: Understand audience emotional reactions to content - **Interaction Optimization**: Optimize content presentation in high-bullet areas - **Content Improvement**: Adjust future content based on bullet feedback ### Application Scenarios: 1. **Content Optimization**: Find favorite segments and reinforce similar content 2. **Pacing Adjustment**: Dense bullet areas indicate engaging content, extend similar segments 3. **Emotion Control**: Understand genuine audience reactions through bullet sentiment 4. **Interaction Design**: Design interactive elements at bullet peaks to boost engagement ### 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" } ``` ### 返回数据示例/Response Example: ```json { "bullet_distribution": [ { "time_point": 5, "count": 328, "percentage": 15.2 }, { "time_point": 12, "count": 562, "percentage": 26.1 }, { "time_point": 18, "count": 445, "percentage": 20.6 } ], "hot_words": [ { "word": "哈哈哈", "count": 156, "sentiment": "positive" }, { "word": "精彩", "count": 98, "sentiment": "positive" }, { "word": "学到了", "count": 76, "sentiment": "positive" } ], "total_count": 2156, "peak_time": 12, "status_code": 0, "status_msg": "" } ``` ### 数据解读/Data Interpretation: - **弹幕分布 (Bullet Distribution)**: - time_point 显示哪个时间点弹幕最密集 - count 越高表示该片段越引起观众共鸣 - percentage 帮助识别弹幕集中度 - 多个弹幕高峰说明视频有多个精彩片段 - **热门词汇 (Hot Words)**: - 高频正面词汇（如"精彩"、"学到了"）说明内容质量好 - 负面词汇可能揭示内容问题点 - 疑问词汇（如"为什么"）可能是用户困惑点 - **总弹幕数 (Total Count)**: - 弹幕数量反映视频互动热度 - 相对播放量的弹幕率可以衡量内容吸引力 - 持续增长说明内容有长尾效应 ### 优化建议/Optimization Suggestions: 1. **强化高峰**: 在弹幕高峰时间点前后强化内容质量 2. **延长精彩**: 延长弹幕密集片段的时长，满足观众期待 3. **回应反馈**: 根据热门词汇调整内容方向 4. **引导互动**: 在弹幕较少的时间点添加引导性内容 5. **情感共鸣**: 多设计能引发正面情感的片段 6. **问题解答**: 针对疑问类弹幕在后续视频中解答 ### 注意事项/Notes: - 弹幕数据可能有延迟，建议作品发布一段时间后查看 - 弹幕分析需要一定的样本量才准确，新作品可能数据不足 - 结合其他指标（互动率、完播率）综合分析效果更好 - 不同类型内容的弹幕特点不同，需要针对性分析 operationId: >- fetch_item_danmaku_analysis_api_v1_douyin_creator_v2_fetch_item_danmaku_analysis_post tags: - Douyin-Creator-V2-API - Douyin-Creator-V2-API parameters: [] requestBody: content: application/json: schema: $ref: '#/components/schemas/ItemBulletAnalysisRequest' description: 作品弹幕分析请求参数/Item bullet analysis request parameters example: cookie: Your_Cookie_Here item_id: '7559536212910853422' 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: ApRJu3cU1qUPthH7LhMoB schemeIds: - HTTPBearer required: true use: id: ApRJu3cU1qUPthH7LhMoB scopes: ApRJu3cU1qUPthH7LhMoB: 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-359719865-run components: schemas: ItemBulletAnalysisRequest: 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' type: object required: - cookie - item_id title: ItemBulletAnalysisRequest description: |- 作品弹幕分析请求模型 Item Bullet Analysis Request Model x-apifox-orders: - cookie - item_id 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: [] ```