---
title: "Search live upper api bilibili huahuo"
description: "Run job:api.bilibili.huahuo.search-live-upper through the looot API: 1 provider, from $0.01 per call. Inputs, prices, output shape and code for curl, JavaScript and Python."
sidebar:
  hidden: true
---

{/* Generated by scripts/generate-api-reference.mjs from data/api-reference.json. Do not edit. */}

Search live upper api bilibili huahuo.

Job id `api.bilibili.huahuo.search-live-upper`, in Ads intelligence (Bilibili). As of 2026-10-01, 1 provider serve it through 1 tool. Run `job:api.bilibili.huahuo.search-live-upper` and looot picks one of them; with `fallback` on, a miss moves on to the next. See [Jobs](/concepts/jobs).

## Inputs

This job has one tool, so it takes that tool's fields. Any key you send passes through unchanged.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `fans_age_tag` | string | no | Fan age tag |
| `fans_gender_tag` | string | no | Fan gender tag |
| `fans_region_tag` | string | no | Fan region tag |
| `gender` | string | no | Streamer gender |
| `high_potential_type` | string | no | Onboarding status |
| `is_brand_live` | string | no | Live type: 1=content live, 0=live commerce. Available filters differ by type |
| `live_audience_h_avg_30d_max` | string | no | Maximum hourly average viewer count, last 30 days |
| `live_audience_h_avg_30d_min` | string | no | Minimum hourly average viewer count, last 30 days |
| `live_danmu_h_avg_30d_max` | string | no | Maximum hourly average danmaku (bullet comment) count, last 30 days |
| `live_danmu_h_avg_30d_min` | string | no | Minimum hourly average danmaku (bullet comment) count, last 30 days |
| `live_good_category` | string | no | Main product category, 0 = all, values from live_good_category |
| `live_good_gmv` | string | no | GMV tier over the last 90 days, 0=all |
| `live_guild_id` | string | no | Live guild, values from live_guild_drop |
| `live_subarea_id` | string | no | Live category (level 2), values from live_area_list |
| `max_fans_num` | string | no | Maximum fan count |
| `max_popularity` | string | no | Maximum average peak popularity per stream, last 30 days |
| `mids` | string | no | Exact match on a batch of UIDs |
| `min_fans_num` | string | no | Minimum fan count |
| `min_popularity` | string | no | Minimum average peak popularity per stream, last 30 days |
| `nickname_or_mids` | string | no | Search by creator nickname or UID |
| `order_by` | string | no | Sort field |
| `page` | string | no | Page number, starting at 1, fixed 20 items per page |
| `partition_id` | string | no | Content category (level 1) |
| `region_id` | string | no | Streamer home region (level 1) |
| `second_partition_id` | string | no | Content category (level 2) |
| `second_region_id` | string | no | Streamer home region (level 2) |
| `sort` | string | no | Sort direction: desc or asc |

## Providers and prices

| Provider | Tool | Price |
| --- | --- | --- |
| [TikHub](/providers/tikhub) | [`tikhub-api-bilibili-huahuo-search-live-upper`](/reference/tools/tikhub-api-bilibili-huahuo-search-live-upper) | $0.01 per call |

A call that fails at the provider costs $0. See [What's free](/money/free-and-failures).

## Output

The run's `result` holds the provider's answer. Signed in, `looot inspect tikhub-api-bilibili-huahuo-search-live-upper` prints its fields.

## Run it

Every call needs your API token in `LOOOT_TOKEN`; [Sign in](/get-started/sign-in#use-the-token-in-scripts-and-agents) shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With `wait: 30` the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll `GET /v1/runs/<runId>`.

Example input with placeholder values:

<CodeGroup>

```bash curl
curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"job:api.bilibili.huahuo.search-live-upper","input":{"mids":"<mids>"},"wait":30}'
```

```js JavaScript
const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "job:api.bilibili.huahuo.search-live-upper",
    input: {
      mids: "<mids>",
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
```

```python Python
import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "job:api.bilibili.huahuo.search-live-upper",
        "input": {
            "mids": "<mids>",
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))
```

</CodeGroup>

To pin one provider, send its tool id as `endpointId` instead of `job:api.bilibili.huahuo.search-live-upper`.