# 获取创作者账号违规记录列表/Get Creator Account Violation Record List

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/tiktok/creator/get_account_violation_list:
    post:
      summary: 获取创作者账号违规记录列表/Get Creator Account Violation Record List
      deprecated: false
      description: >-
        # [中文]

        ### 用途:

        - 获取 TikTok Shop 创作者账号的违规记录信息，用于了解账号在运营期间的违规历史和处理情况。

        - 返回的违规记录包含违规类型、违规时间、违规原因、违规处理措施、申诉状态、是否可申诉等信息。

        - 支持分页查询，可按时间顺序获取多条违规记录。

        - 适用于创作者账号违规风险管理、账号健康监控和数据合规审计。


        ### 备注:

        - 此接口仅适用于 TikTok Shop 创作者账号。

        - 支持分页查询，每次默认返回最新的违规记录。


        ### 参数:

        - cookie: 用户 Cookie 字符串（用于身份认证）

        - page: 整数类型，页码，默认为第 1 页

        - proxy: 可选 HTTP 代理地址，如不使用可省略
            - 示例格式: `http://username:password@host:port`

        ### 返回:

        - `records`（违规记录列表）:
          - `record_id`: 违规记录 ID
          - `violation_time`: 违规发生时间（Unix 时间戳）
          - `violation_info`:
            - `violation_reason`: 违规原因描述
            - `violation_detail`: 违规详情描述
            - `violation_suggestion`: 平台提供的整改建议
            - `policy_url`: 相关政策链接
            - `violation_type`: 违规类别（如视频违规）
          - `record_status`: 记录状态（1 表示有效）
          - `appeal_status`: 申诉状态（0=未申诉，1=已申诉）
          - `enforcement_title`: 平台针对违规采取的执行措施描述（例如扣分、佣金冻结等）
          - `appeal_valid_time`: 申诉有效截止时间（Unix 时间戳）
          - `can_appeal`: 是否允许发起申诉（布尔值）
        - `total`: 总违规记录数

        - `has_more`: 是否还有更多数据

        - `start_time`: 查询起始时间

        - `end_time`: 查询结束时间

        - `creator_status`: 创作者账号状态码（如 0=正常）


        # [English]

        ### Purpose:

        - Retrieve the violation history of a TikTok Shop creator account,
        providing details about past violations and corresponding enforcement
        actions.

        - The returned violation records include violation type, violation time,
        violation reasons, enforcement actions, appeal status, and eligibility
        for appeal.

        - Pagination is supported to retrieve multiple records in chronological
        order.

        - Suitable for creator account risk management, health monitoring, and
        compliance auditing.


        ### Notes:

        - This API is available only for TikTok Shop creator accounts.

        - Pagination is supported; by default, it retrieves the latest violation
        records.


        ### Parameters:

        - cookie: User's Cookie string for authentication

        - page: Integer, page number (default is `1`)

        - proxy: Optional HTTP proxy address, can be omitted if not needed
            - Example format: `http://username:password@host:port`

        ### Response:

        - `records`: List of violation records:
          - `record_id`: Unique ID of the violation record
          - `violation_time`: Time when the violation occurred (Unix timestamp)
          - `violation_info`:
            - `violation_reason`: Reason for the violation
            - `violation_detail`: Detailed description (may be empty)
            - `violation_suggestion`: Recommended corrective action
            - `policy_url`: Link to the related policy
            - `violation_type`: Type of violation (e.g., Video violation)
          - `record_status`: Record status (1 = active)
          - `appeal_status`: Appeal status (0 = not appealed, 1 = appealed)
          - `enforcement_title`: List of enforcement actions taken (e.g., point assignment, commission withholding)
          - `appeal_valid_time`: Deadline for submitting an appeal (Unix timestamp)
          - `can_appeal`: Whether the record is eligible for appeal (boolean)
        - `total`: Total number of violation records

        - `has_more`: Whether there are more records to fetch

        - `start_time`: Query start time

        - `end_time`: Query end time

        - `creator_status`: Creator account status code (e.g., 0 = normal)


        # [示例/Example]

        ```json

        {
            "cookie": "your_cookie_here",
            "page": 1
        }

        ```
      operationId: >-
        get_account_violation_list_api_v1_tiktok_creator_get_account_violation_list_post
      tags:
        - TikTok-Creator-API
        - TikTok-Creator-API
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/GetViolationRecordRequest'
      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: r-SKbpZ00SZspdOqcW-cw
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: r-SKbpZ00SZspdOqcW-cw
            scopes:
              r-SKbpZ00SZspdOqcW-cw:
                HTTPBearer: []
      x-apifox-folder: TikTok-Creator-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-289437012-run
components:
  schemas:
    GetViolationRecordRequest:
      properties:
        cookie:
          type: string
          title: Cookie
          description: 用户 Cookie 字符串/User Cookie String
          default: Your_Cookie_String
        proxy:
          anyOf:
            - type: string
            - type: 'null'
          title: Proxy
          description: 可选 HTTP 代理地址/Optional HTTP Proxy Address
          default: ''
        page:
          type: integer
          title: Page
          description: 页码/Page Number
          default: 1
      type: object
      title: GetViolationRecordRequest
      x-apifox-orders:
        - cookie
        - proxy
        - page
      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: []

```