---
title: "Fetch topic search api weibo web v2"
description: "Run job:api.weibo.web-v2.fetch-topic-search through the looot API: 1 provider, from $0.001 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. */}

Fetch topic search api weibo web v2.

Job id `api.weibo.web-v2.fetch-topic-search`, in [Social data](/catalog/social) (Weibo). As of 2026-10-01, 1 provider serve it through 1 tool. Run `job:api.weibo.web-v2.fetch-topic-search` 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 |
| --- | --- | --- | --- |
| `page` | integer | no | Page number |
| `query` | string | yes | Search keyword |

## Providers and prices

| Provider | Tool | Price |
| --- | --- | --- |
| [TikHub](/providers/tikhub) | [`tikhub-api-weibo-web-v2-fetch-topic-search`](/reference/tools/tikhub-api-weibo-web-v2-fetch-topic-search) | $0.001 per call |

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

## Output

Shape of the run's `result`, the expected shape, not yet checked against real answers:

```txt
{ code, data: { parsed_data: { count, items: { ... }[], parse_success } }, docs, time, params: { page, query }, router, message, support, cache_url, time_zone, message_zh, request_id, time_stamp, cache_message, cache_message_zh }
```

## 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.weibo.web-v2.fetch-topic-search","input":{"query":"<query>"},"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.weibo.web-v2.fetch-topic-search",
    input: {
      query: "<query>",
    },
    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.weibo.web-v2.fetch-topic-search",
        "input": {
            "query": "<query>",
        },
        "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.weibo.web-v2.fetch-topic-search`.