# 获取用户主页作品数据V2/Get user homepage video data V2 ## OpenAPI Specification ```yaml openapi: 3.0.1 info: title: '' description: '' version: 1.0.0 paths: /api/v1/bilibili/web/fetch_user_post_videos_v2: get: summary: 获取用户主页作品数据V2/Get user homepage video data V2 deprecated: false description: >- # [中文] ### 用途: - 获取用户发布的视频数据，并可按关键词在该用户的作品内搜索。 - 与 `/fetch_user_post_videos` 的区别见下方「与V1的区别」。 ### 参数: - uid: 用户UID - pn: 页码，无上限；超出末页返回空的 `data.archives` - ps: 每页数量，取值 1~100 - keyword: 关键词，留空表示不过滤，返回该用户全部作品 - 仅支持单个词，请勿包含空格。 ### 与V1的区别: - **无分页上限**：V1 最多只能取到第 5000 个作品，本接口可一直翻到该用户最早的一条投稿。作品数超过 5000 时请使用本接口。 - **关键词生效**：本接口支持在该用户的作品内按关键词搜索，V1 不支持。 - **字段更精简**：返回 `aid`/`bvid`/`title`/`pubdate`/`pic`/`duration`/`desc`/`stat.view` 等；不含评论数、分区等字段。需要这些字段请用 V1，或用 `/fetch_one_video` 按 `bvid` 补齐。 - 排序固定为发布时间倒序，不支持 `order` 参数。 ### 返回: - 用户发布的视频数据，作品列表在 `data.archives`，总数在 `data.page.total` # [English] ### Purpose: - Get user post video data, optionally searching by keyword within that user's works. - See "Differences from V1" below for how this compares to `/fetch_user_post_videos`. ### Parameters: - uid: User UID - pn: Page number, no cap; past the last page `data.archives` comes back empty - ps: Page size, 1~100 - keyword: Keyword, empty returns all works of the user - Single word only; do not include spaces. ### Differences from V1: - **No pagination cap**: V1 reaches at most 5000 works; this endpoint pages all the way back to the user's earliest upload. Use this one when a user has more than 5000 works. - **Keyword works**: this endpoint supports searching within the user's works; V1 does not. - **Leaner fields**: returns `aid`/`bvid`/`title`/`pubdate`/`pic`/`duration`/`desc`/`stat.view` and similar; no comment count or category fields. Use V1 for those, or fill them in per `bvid` via `/fetch_one_video`. - Ordering is fixed to newest-first by publish time; no `order` parameter. ### Return: - User posted video data; the list is in `data.archives`, the total in `data.page.total` # [示例/Example] uid = "178360345" pn = 1 ps = 30 keyword = "" operationId: >- fetch_user_post_videos_v2_api_v1_bilibili_web_fetch_user_post_videos_v2_get tags: - Bilibili-Web-API - Bilibili-Web-API parameters: - name: uid in: query description: 用户UID required: true example: '178360345' schema: type: string description: 用户UID title: Uid - name: pn in: query description: 页码，无上限/Page number, no cap required: false schema: type: integer minimum: 1 description: 页码，无上限/Page number, no cap default: 1 title: Pn - name: ps in: query description: 每页数量，最大100/Page size, max 100 required: false schema: type: integer maximum: 100 minimum: 1 description: 每页数量，最大100/Page size, max 100 default: 30 title: Ps - name: keyword in: query description: 关键词，留空返回全部/Keyword, empty returns all required: false schema: type: string description: 关键词，留空返回全部/Keyword, empty returns all default: '' title: Keyword responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/ResponseModel' headers: {} x-apifox-name: '' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' headers: {} x-apifox-name: '' security: - HTTPBearer: [] x-apifox: schemeGroups: - id: cLejs3qmEAUL76r0b4Yu8 schemeIds: - HTTPBearer required: true use: id: cLejs3qmEAUL76r0b4Yu8 scopes: cLejs3qmEAUL76r0b4Yu8: HTTPBearer: [] x-apifox-folder: Bilibili-Web-API x-apifox-status: released x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-501036600-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 input: type: string ctx: type: object title: Context x-apifox-orders: [] properties: {} x-apifox-ignore-properties: [] type: object required: - loc - msg - type title: ValidationError x-apifox-orders: - loc - msg - type - input - ctx 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: [] ```