> ## Documentation Index
> Fetch the complete documentation index at: https://aisa.one/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Search API

> Search API

Search API

**Pricing** — billed per successful call; the final charge scales by your plan multiplier. Charged only when the upstream response body `code` is `200`.

<Note>
  Response structure is not yet fully documented — **refer to the actual API response**.
</Note>

## Example

```bash theme={null}
curl "https://api.aisa.one/apis/v1/tikhub/pipixia/app/fetch_search?keyword=See API documentation" \
  -H "Authorization: Bearer YOUR_API_KEY"
```


## OpenAPI

````yaml openapi/tikhub.json GET /tikhub/pipixia/app/fetch_search
openapi: 3.0.0
info:
  title: TikHub API
  description: >-
    Multi-platform social media data — Douyin, TikTok, Bilibili, Kuaishou,
    Weibo, Xiaohongshu, Zhihu, and commercial (Xingtu/Huahuo/Billboard)
    endpoints.
  version: 1.0.0
servers:
  - url: https://api.aisa.one/apis/v1
security:
  - bearerAuth: []
paths:
  /tikhub/pipixia/app/fetch_search:
    get:
      tags:
        - TikHub - Pipixia
      summary: Search API
      description: >-
        Pipixia (app).


        ### Purpose:

        - Search API, support search user, post, etc.

        ### Parameters:

        - keyword: Search keyword.

        - offset: Page cursor, default is 0, get the corresponding value from
        the `offset` Key in the previous page.

        - search_type: Search type, available values are as follows:
            - 1: Comprehensive
            - 8: Hot
            - 9: Fresh
            - 2: Video
            - 3: Photo
            - 4: User
            - 5: Hashtag
        ### Return:

        - Search result
      operationId: get_tikhub_pipixia_app_fetch_search
      parameters:
        - name: keyword
          in: query
          required: true
          schema:
            type: string
            title: Keyword
            description: Search keyword
          description: Search keyword
          example: Pipixia
        - name: offset
          in: query
          required: false
          schema:
            type: string
            description: >-
              Page cursor, default is 0, get the corresponding value from the
              `offset` Key in the previous page.
            default: '0'
            title: Offset
          description: >-
            Page cursor, default is 0, get the corresponding value from the
            `offset` Key in the previous page.
          example: '0'
        - name: search_type
          in: query
          required: false
          schema:
            type: string
            description: |-
              Search type, available values are as follows:
                  - 1: Comprehensive
                  - 8: Hot
                  - 9: Fresh
                  - 2: Video
                  - 3: Photo
                  - 4: User
                  - 5: Hashtag
            default: '1'
            title: Search Type
          description: |-
            Search type, available values are as follows:
                - 1: Comprehensive
                - 8: Hot
                - 9: Fresh
                - 2: Video
                - 3: Photo
                - 4: User
                - 5: Hashtag
          example: '1'
      responses:
        '200':
          description: >-
            Successful response. The outer object follows `ResponseModel`; the
            endpoint-specific payload is in `data`.


            ### Return

            - Search result
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ResponseModel'
components:
  schemas:
    ResponseModel:
      properties:
        code:
          type: integer
          title: Code
          description: HTTP status code
          default: 200
        request_id:
          title: Request Id
          description: Unique request identifier
          nullable: true
          type: string
        message:
          type: string
          title: Message
          description: Response message (EN-US)
          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:
          title: Docs
          description: Link to the API Swagger documentation for this endpoint
          nullable: true
          type: string
        cache_message:
          title: Cache Message
          description: Cache message (EN-US)
          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.
          nullable: true
          type: string
        cache_message_zh:
          title: Cache Message Zh
          description: Cache message (ZH-CN)
          default: >-
            本次响应已缓存，可通过下方 URL 直接查看，有效期 24
            小时，访问缓存链接无额外费用。缓存仅用于请求溯源，不影响接口数据的时效性，也不会再次通过接口返回。
          nullable: true
          type: string
        cache_url:
          title: Cache Url
          description: The URL to access the cached result
          nullable: true
          type: string
        router:
          type: string
          title: Router
          description: The endpoint that generated this response
          default: ''
        params:
          title: Params
          description: The parameters used in the request
          default: {}
        data:
          title: Data
          description: >-
            Endpoint-specific response payload. The official shared model does
            not declare a fixed type or field set. Use the operation's
            documented return fields or response example; an operation-specific
            schema, when present, describes the documented fields. Undocumented
            fields must be read from the actual response rather than assumed.
          nullable: true
      type: object
      title: ResponseModel
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: AIsa API key. Get yours at https://aisa.one

````