# 获取商单任务列表/Get mission task list ## OpenAPI Specification ```yaml openapi: 3.0.1 info: title: '' description: '' version: 1.0.0 paths: /api/v1/douyin/creator/fetch_mission_task_list: get: summary: 获取商单任务列表/Get mission task list deprecated: false description: >- # [中文] ### 用途: - 获取抖音创作者平台的商单任务列表 - 支持多种筛选条件，包括行业分类、付费类型、平台渠道等 ### 重要参数使用说明: #### 行业分类组合规则: - **industry_lv1=-1 (全部)**: 当选择全部一级行业时，industry_lv2参数将被忽略，无需设置 - **industry_lv1=具体值**: 当选择具体一级行业时，可配合industry_lv2进行二级筛选 - industry_lv2=-1: 该一级行业下的所有二级分类 - industry_lv2=具体值: 该一级行业下的具体二级分类 #### 可选参数 (选择"全部"时无需传入): - **platform_channel**: 不传入表示全部平台渠道 - **pay_type**: 不传入表示全部付费类型 - **greater_than_cost_progress**: 不传入表示不限制成本进度 - **publish_time_start**: 不传入表示不限制发布时间 - **quick_selector_scene**: 不传入表示不使用快速筛选 - **keyword**: 不传入表示不进行关键词搜索 ### 参数详解: - cursor: 游标，用于分页，0表示第一页 - limit: 每页返回的任务数量，建议24 - mission_type: 任务类型，通常为1 - tab_scene: 场景类型 - 1: 可投稿 (可以直接投稿的任务) - 2: 可报名 (需要报名审核的任务) - 3: 好物测评 (商品测评类任务) - industry_lv1/lv2: 行业分类 (建议先调用fetch_industry_category_config获取完整分类) - -1: 全部行业 - 具体数值: 对应具体行业类别 (如1913=游戏, 1903=食品饮料) - platform_channel: 平台渠道 (可选) - 1: 抖音视频 - 2: 抖音直播 - 3: 抖音图文 - pay_type: 付费类型 (可选) - 1: 视频等级 (按粉丝量等级定价) - 2: 自定义 (商家自定义价格) - 3: 按转化付费 (按转化效果付费) - 4: 按有效播放量 (按播放量付费) - 5: 按销售量 (按商品销售量付费) - 9: 按核销量 (按核销数量付费) - 14: 按付费分佣 (按分佣比例付费) - greater_than_cost_progress: 成本进度筛选 (可选) - 20: 高于20%成本进度的任务 - 50: 高于50%成本进度的任务 - 80: 高于80%成本进度的任务 - publish_time_start: 发布开始时间过滤 (可选，时间戳格式) - quick_selector_scene: 快速筛选场景 (可选) - 1: 高收益任务 - 4: 保底收入任务 - 5: 曾经合作过的商家 - keyword: 关键词搜索 (可选，支持任务名称或任务ID) ### 使用示例: ``` # 获取全部行业的可投稿任务 GET /fetch_mission_task_list?industry_lv1=-1&tab_scene=1 # 获取游戏行业休闲游戏分类的按播放量付费任务 GET /fetch_mission_task_list?industry_lv1=1913&industry_lv2=191301&pay_type=4 # 获取高收益的抖音视频任务 GET /fetch_mission_task_list?platform_channel=1&quick_selector_scene=1 ``` ### 返回: - 返回符合条件的商单任务列表 - 包含任务详情、报酬信息、要求等 # [English] ### Purpose: - Get mission task list from Douyin Creator platform - Supports multiple filtering conditions including industry classification, payment type, platform channel, etc. ### Important Parameter Usage Guidelines: #### Industry Classification Combination Rules: - **industry_lv1=-1 (All)**: When selecting all primary industries, industry_lv2 parameter will be ignored, no need to set - **industry_lv1=specific value**: When selecting specific primary industry, can be combined with industry_lv2 for secondary filtering - industry_lv2=-1: All secondary categories under the primary industry - industry_lv2=specific value: Specific secondary category under the primary industry #### Optional Parameters (No need to pass when selecting "All"): - **platform_channel**: Not passing means all platform channels - **pay_type**: Not passing means all payment types - **greater_than_cost_progress**: Not passing means no cost progress restriction - **publish_time_start**: Not passing means no publish time restriction - **quick_selector_scene**: Not passing means no quick filtering - **keyword**: Not passing means no keyword search ### Parameter Details: - cursor: Cursor for pagination, 0 for first page - limit: Number of tasks per page, recommended 24 - mission_type: Mission type, usually 1 - tab_scene: Scene type - 1: Submittable (tasks that can be submitted directly) - 2: Registrable (tasks that require registration and approval) - 3: Product Review (product evaluation tasks) - industry_lv1/lv2: Industry classification (recommend calling fetch_industry_category_config first) - -1: All industries - Specific values: Corresponding to specific industry categories (e.g., 1913=Gaming, 1903=Food&Beverage) - platform_channel: Platform channel (optional) - 1: Douyin Video - 2: Douyin Live - 3: Douyin Image&Text - pay_type: Payment type (optional) - 1: Video Level (pricing by follower level) - 2: Custom (merchant custom pricing) - 3: Conversion-based (pay by conversion effect) - 4: Valid Views (pay by view count) - 5: Sales Volume (pay by product sales) - 9: Verification Volume (pay by verification count) - 14: Commission-based (pay by commission ratio) - greater_than_cost_progress: Cost progress filter (optional) - 20: Tasks with more than 20% cost progress - 50: Tasks with more than 50% cost progress - 80: Tasks with more than 80% cost progress - publish_time_start: Publish start time filter (optional, timestamp format) - quick_selector_scene: Quick filter scene (optional) - 1: High revenue tasks - 4: Guaranteed income tasks - 5: Previously collaborated merchants - keyword: Keyword search (optional, supports task name or task ID) ### Usage Examples: ``` # Get submittable tasks from all industries GET /fetch_mission_task_list?industry_lv1=-1&tab_scene=1 # Get tasks from gaming industry casual games category with view-based payment GET /fetch_mission_task_list?industry_lv1=1913&industry_lv2=191301&pay_type=4 # Get high-revenue Douyin video tasks GET /fetch_mission_task_list?platform_channel=1&quick_selector_scene=1 ``` ### Return: - Returns mission task list matching the conditions - Contains task details, compensation info, requirements, etc. operationId: >- fetch_mission_task_list_api_v1_douyin_creator_fetch_mission_task_list_get tags: - Douyin-Creator-API - Douyin-Creator-API parameters: - name: cursor in: query description: 游标/Cursor (分页) required: false example: 0 schema: type: integer minimum: 0 description: 游标/Cursor (分页) default: 0 title: Cursor - name: limit in: query description: 每页数量/Items per page required: false example: 24 schema: type: integer maximum: 100 minimum: 1 description: 每页数量/Items per page default: 24 title: Limit - name: mission_type in: query description: 任务类型/Mission type required: false example: 1 schema: type: integer description: 任务类型/Mission type default: 1 title: Mission Type - name: tab_scene in: query description: 场景类型/Scene type (1=可投稿, 2=可报名, 3=好物测评) required: false example: 1 schema: type: integer description: 场景类型/Scene type (1=可投稿, 2=可报名, 3=好物测评) default: 1 title: Tab Scene - name: industry_lv1 in: query description: 一级行业/Primary industry (-1=全部) required: false example: 1913 schema: type: integer description: 一级行业/Primary industry (-1=全部) default: -1 title: Industry Lv1 - name: industry_lv2 in: query description: 二级行业/Secondary industry (-1=全部) required: false example: 191301 schema: type: integer description: 二级行业/Secondary industry (-1=全部) default: -1 title: Industry Lv2 - name: platform_channel in: query description: 平台渠道/Platform channel (1=抖音视频, 2=抖音直播, 3=抖音图文) required: false example: '1' schema: anyOf: - type: integer - type: 'null' description: 平台渠道/Platform channel (1=抖音视频, 2=抖音直播, 3=抖音图文) title: Platform Channel - name: pay_type in: query description: >- 付费类型/Pay type (1=视频等级, 2=自定义, 3=按转化付费, 4=按有效播放量, 5=按销售量, 9=按核销量, 14=按付费分佣) required: false example: '4' schema: anyOf: - type: integer - type: 'null' description: >- 付费类型/Pay type (1=视频等级, 2=自定义, 3=按转化付费, 4=按有效播放量, 5=按销售量, 9=按核销量, 14=按付费分佣) title: Pay Type - name: greater_than_cost_progress in: query description: 成本进度/Cost progress (20=高于20%, 50=高于50%, 80=高于80%) required: false example: '20' schema: anyOf: - type: integer - type: 'null' description: 成本进度/Cost progress (20=高于20%, 50=高于50%, 80=高于80%) title: Greater Than Cost Progress - name: publish_time_start in: query description: 发布开始时间/Publish start time (时间戳) required: false example: '1757097636' schema: anyOf: - type: integer - type: 'null' description: 发布开始时间/Publish start time (时间戳) title: Publish Time Start - name: quick_selector_scene in: query description: 快速选择场景/Quick selector (1=高收益, 4=保底收入, 5=合作过) required: false schema: anyOf: - type: integer - type: 'null' description: 快速选择场景/Quick selector (1=高收益, 4=保底收入, 5=合作过) title: Quick Selector Scene - name: keyword in: query description: 关键词/Keyword (任务名称或ID) required: false schema: anyOf: - type: string - type: 'null' description: 关键词/Keyword (任务名称或ID) title: Keyword 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: xFY5rdukpmz0Wfdx688sY schemeIds: - HTTPBearer required: true use: id: xFY5rdukpmz0Wfdx688sY scopes: xFY5rdukpmz0Wfdx688sY: HTTPBearer: [] x-apifox-folder: Douyin-Creator-API x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-346680211-run components: schemas: 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: [] ```