# 获取行业分类配置/Get industry category config ## OpenAPI Specification ```yaml openapi: 3.0.1 info: title: '' description: '' version: 1.0.0 paths: /api/v1/douyin/creator/fetch_industry_category_config: get: summary: 获取行业分类配置/Get industry category config deprecated: false description: >- # [中文] ### 用途: - 获取抖音创作者平台的行业分类配置 - 返回所有可用的行业分类层级结构 - **建议在调用商单任务列表接口前先调用此接口获取完整的行业分类信息** ### 重要说明: - 此接口已优化为Redis缓存，首次调用后数据将缓存30天 - 缓存键: `douyin_creator:industry_categories` - 数据结构包含一级行业和二级行业的完整映射关系 ### 数据结构: ```json { "status_code": 0, "status_msg": "success", "data": { "industry_categories": [ {"key": "-1", "label": "全部"}, {"key": 1901, "label": "3C及电器"}, {"key": 1913, "label": "游戏"}, ... ], "industry_subcategories": { 1913: [ {"key": "-1", "label": "全部"}, {"key": 191301, "label": "休闲游戏"}, {"key": 191302, "label": "棋牌桌游"}, ... ], ... } } } ``` ### 在商单任务筛选中的使用: 1. **获取全部行业任务**: `industry_lv1=-1` (此时industry_lv2无需设置) 2. **获取特定一级行业**: `industry_lv1=1913` (游戏行业) 3. **获取特定二级行业**: `industry_lv1=1913&industry_lv2=191301` (游戏-休闲游戏) ### 性能优化: - 首次调用时从本地JSON文件读取并缓存到Redis - 后续调用直接从Redis缓存读取，大幅提升响应速度 - 缓存有效期30天，确保数据时效性 ### 返回: - 返回完整的行业分类树结构 - 包含32个一级行业分类和对应的二级行业分类 - 每个分类包含分类ID(key)和名称(label) # [English] ### Purpose: - Get industry category configuration from Douyin Creator platform - Returns all available industry classification hierarchy - **Recommend calling this API first before using mission task list API to get complete industry classification info** ### Important Notes: - This API is optimized with Redis caching, data will be cached for 30 days after first call - Cache key: `douyin_creator:industry_categories` - Data structure contains complete mapping relationship between primary and secondary industries ### Data Structure: ```json { "status_code": 0, "status_msg": "success", "data": { "industry_categories": [ {"key": "-1", "label": "All"}, {"key": 1901, "label": "3C & Electronics"}, {"key": 1913, "label": "Gaming"}, ... ], "industry_subcategories": { 1913: [ {"key": "-1", "label": "All"}, {"key": 191301, "label": "Casual Games"}, {"key": 191302, "label": "Board Games"}, ... ], ... } } } ``` ### Usage in Mission Task Filtering: 1. **Get all industry tasks**: `industry_lv1=-1` (industry_lv2 not needed) 2. **Get specific primary industry**: `industry_lv1=1913` (Gaming industry) 3. **Get specific secondary industry**: `industry_lv1=1913&industry_lv2=191301` (Gaming-Casual Games) ### Performance Optimization: - First call reads from local JSON file and caches to Redis - Subsequent calls read directly from Redis cache, significantly improving response speed - Cache validity period of 30 days ensures data timeliness ### Return: - Returns complete industry classification tree structure - Contains 32 primary industry categories and corresponding secondary industry categories - Each category contains category ID(key) and name(label) operationId: >- fetch_industry_category_config_api_v1_douyin_creator_fetch_industry_category_config_get tags: - Douyin-Creator-API - Douyin-Creator-API parameters: [] responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/ResponseModel' headers: {} x-apifox-name: OK security: - HTTPBearer: [] x-apifox: schemeGroups: - id: i_kkP5RtPm0clLCsm6GDV schemeIds: - HTTPBearer required: true use: id: i_kkP5RtPm0clLCsm6GDV scopes: i_kkP5RtPm0clLCsm6GDV: HTTPBearer: [] x-apifox-folder: Douyin-Creator-API x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-346680212-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: '' 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: [] ```