# Weibo Scraper Pro \[From $1.50/1K💰] | Posts (`ahmed_jasarevic/weibo-scraper-pro`) Actor

Scrape Weibo hot search, posts, comments, user profiles, fans, followers, likes and topics without login. Get text, authors, media and engagement metrics. From $1.50 per 1,000 records.

- **URL**: https://apify.com/ahmed_jasarevic/weibo-scraper-pro.md
- **Developed by:** [Ahmed Jasarevic](https://apify.com/ahmed_jasarevic) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 fans

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Weibo Scraper Pro – Posts, Comments, Users & Hot Search

Collect public **Weibo** hot search, rankings, posts, reposts, comments, topics, user profiles, fans, following and likers in one Actor. Get Chinese-language text, authors, media URLs, timestamps and engagement metrics as clean, flat records. **From $1.50 per 1,000 records.**

### Weibo Data For Social Listening And Research

Weibo is China’s largest microblogging platform and a leading source of public opinion, entertainment trends and brand conversation. This Actor turns public Weibo surfaces into one normalized dataset for monitoring, analysis and AI workflows.

- **Brand and reputation monitoring** — track keywords, topics and hot search.
- **Social listening** — follow public sentiment around events and campaigns.
- **Influencer research** — compare profiles, followers and engagement.
- **Audience analysis** — map fans, following and post likers.
- **Market and academic research** — export Chinese social posts with metadata.
- **Trend monitoring** — capture hot search and ranking boards over time.

### How It Works

![How Weibo Scraper Pro works: collect hot search, posts, comments, profiles and audience data in one dataset.](https://api.apify.com/v2/key-value-stores/oeuA0kLOyhbRM4fzt/records/how-it-works-weibo-scraper-pro.webp)

Choose the surfaces you need: hot search, rankings, the hot timeline, keyword and media search, topics, user search, profiles, relationships, posts, reposts or comments. The Actor writes one dataset with a `recordType` field so you can filter or split records downstream.

- One dataset for every record type.
- Works without a Weibo account for most public surfaces.
- Optional comments and replies.
- Optional only-new mode for scheduled monitoring.

### Supported Weibo Surfaces

- **Hot search and rankings** — realtime hot, entertainment, social events, tech, life, sport, game and recommendation boards.
- **Search** — keyword, advanced, picture, video and user search.
- **Topics** — matching posts and the topic card when available.
- **Profiles** — public user details and timelines.
- **Relationships** — fans, following and post likers.
- **Posts** — post details, user timelines and reposts.
- **Comments** — top-level comments and optional replies.

Some deeper relationship pages and repost timelines may require a valid Weibo cookie. The Actor reports a warning instead of failing the whole run when a surface is unavailable.

### Input – Configure A Weibo Run

| Field | Type | Default | Notes |
|---|---|---|---|
| `hotSearch` | boolean | `true` | Collect the realtime hot search board |
| `hotTimeline` | boolean | `false` | Collect the discovery feed |
| `rankingCategories` | array | `["realtimehot"]` | Ranking board categories |
| `searchQueries` | array | `[]` | Keyword searches |
| `advancedSearchQueries` | array | `[]` | Advanced searches with optional media type and dates |
| `topicQueries` | array | `[]` | Topic names, with or without `#` |
| `pictureSearchQueries` | array | `[]` | Picture search terms |
| `videoSearchQueries` | array | `[]` | Video search terms |
| `userSearchQueries` | array | `[]` | User discovery terms |
| `userIds` | array | `[]` | Numeric UIDs or profile URLs |
| `fanUserIds` | array | `[]` | Users whose fans to collect |
| `followingUserIds` | array | `[]` | Users whose following list to collect |
| `postUrls` | array | `[]` | Post URLs or numeric IDs |
| `likerPostUrls` | array | `[]` | Posts whose likers to collect |
| `repostPostUrls` | array | `[]` | Posts whose reposts to collect |
| `maxPosts` | integer | `200` | Target for post-producing sources |
| `fillToMaxPosts` | boolean | `true` | Request extra pages until `maxPosts` is reached |
| `maxSearchPages` | integer | `3` | Initial search result pages |
| `maxProfilePages` | integer | `3` | Initial profile timeline pages |
| `maxPagesPerTarget` | integer | `3` | Pages for topics, media, users, fans, following, likers and reposts |
| `maxItemsPerTarget` | integer | `100` | Items per relationship or engagement target |
| `maxHotTimelinePages` | integer | `1` | Hot timeline pages |
| `advancedSearchIncludeType` | string | `""` | `pic`, `video` or all posts |
| `advancedSearchSince` | string | `""` | Start date in `YYYY-MM-DD` |
| `advancedSearchUntil` | string | `""` | End date in `YYYY-MM-DD` |
| `includeComments` | boolean | `false` | Add comments |
| `maxCommentsPerPost` | integer | `20` | Comments per post |
| `maxCommentPages` | integer | `3` | Comment pages per post |
| `includeReplies` | boolean | `false` | Add replies to comments |
| `maxRepliesPerComment` | integer | `5` | Replies per comment |
| `maxReplyPages` | integer | `2` | Reply pages per comment |
| `includeUserProfiles` | boolean | `true` | Add user records for profiles and user search |
| `includeFullText` | boolean | `true` | Expand truncated long posts |
| `onlyNewItems` | boolean | `false` | Skip items seen in earlier runs |
| `stateKey` | string | `weibo-pro-monitor` | State key for only-new mode |
| `stateStoreName` | string | `weibo-monitor` | Key-value store for only-new state |
| `weiboCookie` | string | `""` | Optional cookie for login-gated surfaces |
| `proxyConfiguration` | object | On | Optional connection settings |
| `requestDelayMillis` | integer | `700` | Pause between requests |
| `maxRequestRetries` | integer | `3` | Retries for network, 403/429 and server errors |

### Output – One Dataset, Seven Record Types

Filter by `recordType`: `hot_search`, `ranking`, `post`, `repost`, `topic`, `user` or `comment`.

| Record type | Main fields |
|---|---|
| `hot_search` | `rank`, `keyword`, `section`, `heat`, `label`, `badgeIcon`, `isPinned`, `categoryId`, `url`, `createdAt` |
| `ranking` | `rank`, `keyword`, `category`, `heat`, `isPinned`, `url`, `createdAt` |
| `post` | `id`, `url`, `text`, `createdAt`, `authorId`, `authorName`, `authorFollowers`, `authorVerified`, `repostsCount`, `commentsCount`, `likesCount`, `imageUrls`, `videoUrl`, `mediaUrls`, `isRetweet`, `retweetedFrom`, `regionName`, `query`, `source` |
| `repost` | Post fields plus `repostOfId`, `repostOfUrl` |
| `topic` | `id`, `topicId`, `title`, `description`, `postsCount`, `followersCount`, `query`, `url` |
| `comment` | `id`, `parentId`, `rootId`, `text`, `createdAt`, `authorId`, `authorName`, `likesCount`, `repliesCount`, `floorNumber`, `isReply`, `url`, `query` |
| `user` | `id`, `authorName`, `authorDescription`, `authorFollowers`, `authorFollowing`, `authorPosts`, `authorVerified`, `authorVerifiedReason`, `authorLocation`, `authorAvatar`, `relation`, `relatedTo`, `query`, `url` |

Posts also include `textHtml`, `authorAvatar`, `authorGender`, `linkUrl`, `sourceLabel` and `isLongText`. Comments include `textHtml`, `authorAvatar`, `authorFollowers` and `sourceLabel`. Liker records include `createdAt` when Weibo exposes the like date.

### Example Input – Hot Search And Keyword Search

```json
{
  "hotSearch": true,
  "rankingCategories": ["realtimehot", "socialevent"],
  "searchQueries": ["人工智能", "新能源汽车"],
  "maxPosts": 200,
  "maxSearchPages": 3,
  "includeComments": false
}
```

### Example Output – Keyword Post

```json
{
  "recordType": "post",
  "id": "5360179932829399",
  "url": "https://m.weibo.cn/detail/5360179932829399",
  "text": "#人工智能##前沿观察# 人工智能知名学者称，LLM可能是人工智能走错了路。",
  "createdAt": "2026-10-31T12:32:26.000Z",
  "authorName": "青青虫的微博",
  "authorFollowers": 11539000,
  "authorVerified": true,
  "likesCount": 3,
  "commentsCount": 6,
  "repostsCount": 0,
  "mediaUrls": ["https://wx3.sinaimg.cn/..."],
  "query": "人工智能",
  "source": "search"
}
```

### Export And Monitor On A Schedule

Download JSON, CSV, Excel or HTML, or use the Apify API. Enable `onlyNewItems` with a unique `stateKey` and `stateStoreName` for daily brand or topic monitors. Send new records to Google Sheets, Make, Zapier, n8n or a webhook.

### Related Actors

- [Twitter/X Scraper](https://apify.com/apify/twitter-scraper) — compare public conversation across platforms
- [Reddit Scraper](https://apify.com/trudax/reddit-scraper) — add community discussion data
- [TikTok Scraper](https://apify.com/clockworks/tiktok-scraper) — collect short-video trends
- [Google Search Scraper](https://apify.com/ahmed_jasarevic/google-search-scraper) — research brand and event coverage

### FAQ

#### Do I need a Weibo account?

No for most public data. Hot search, rankings, hot timeline, search, topics, media search, user search, profiles, likers and first-page fans/following work without login. Repost timelines and deeper following pages may require a cookie.

#### Can I collect multiple pages of search results?

Yes. With `fillToMaxPosts` enabled by default, the Actor keeps paging until `maxPosts` is reached or results end. Some profile timelines are indexed up to roughly 1,000 posts.

#### Can I get replies?

Yes. Enable `includeReplies`; the Actor checks comments with replies and inspects up to `maxReplyPages` per comment. Coverage depends on what Weibo exposes.

#### Why are reposts empty?

Weibo often asks for login on repost timelines. Add a valid `weiboCookie` or retry later; the Actor records a warning in `SUMMARY`.

#### Does it translate Chinese text?

No. Text is returned as published in UTF-8. Translate downstream if needed.

#### Can I monitor only new posts?

Yes. Enable `onlyNewItems` and use a unique `stateKey` and `stateStoreName` for each independent monitor.

#### How much does it cost?

Pay-per-event: hot search or ranking row **$0.003**, keyword/media/advanced-search/hot-timeline post **$0.0025**, topic, fan or following **$0.0015**, user timeline, repost or user search **$0.0025**, post detail or profile **$0.008**, comment or reply **$0.003**, liker **$0.0035**, plus a **$0.005** Actor Start event. A hot-search-only run is very cheap.

### For AI Agents & LLM Apps

Returns one flat dataset of public Weibo records. Filter by `recordType` before processing.

Minimal working input:

```json
{ "hotSearch": true, "searchQueries": ["人工智能"], "maxPosts": 20 }
```

Output fields: `recordType, id, url, text, textHtml, createdAt, authorId, authorName, authorFollowers, authorVerified, authorDescription, authorFollowing, authorPosts, authorLocation, authorAvatar, likesCount, commentsCount, repostsCount, imageUrls, videoUrl, mediaUrls, isRetweet, retweetedFrom, regionName, query, source, rank, keyword, section, heat, label, category, isPinned, topicId, title, description, postsCount, followersCount, parentId, rootId, repliesCount, floorNumber, isReply, relation, relatedTo, repostOfId, repostOfUrl, scrapedAt`.

Behaviors an agent should know:

- Every row has `recordType`: `hot_search`, `ranking`, `post`, `repost`, `topic`, `user` or `comment`.
- `hotSearch` defaults to true; set it false when collecting only another surface.
- Comments are off by default; enable `includeComments` and set limits.
- Reposts and deeper following pages may need `weiboCookie`.
- `onlyNewItems` requires a stable `stateKey` and `stateStoreName`.
- Free users get a 10-record preview.

Billing: per-event, from **$0.0015 per topic/fan/following** up to **$0.008 per post detail or profile**, plus a **$0.005** Actor Start event.

### Legal & Compliance Disclaimer

This Actor is an independent tool. It is not affiliated with, endorsed by or sponsored by Weibo or Sina.

It collects publicly available posts, profiles, trends and engagement data. A cookie is optional and is used only to access public surfaces that require logged-in access. Users are responsible for complying with Weibo’s terms, robots.txt, copyright, privacy and data-protection law. Do not use the data for harassment, surveillance, doxxing or prohibited content. Nothing here is legal advice.

### SEO Keywords

weibo scraper, weibo posts, weibo comments, weibo profiles, weibo hot search, weibo rankings, weibo fans, weibo following, weibo topics, chinese social media, china social listening, weibo api, weibo data, social media scraper, influencer research, audience analysis, brand monitoring, public opinion

# Actor input Schema

## `hotSearch` (type: `boolean`):

Collect the live Weibo hot search board with rank, keyword, heat and topic URL.

## `hotTimeline` (type: `boolean`):

Collect the Weibo discovery/hot timeline feed. These posts are separate from the ranked hot-search board.

## `rankingCategories` (type: `array`):

Collect one or more s.weibo.com ranking boards. Accepted values: realtimehot, entrank, socialevent, tech, life, sport, game, recommend. Uses a separate weibo.com visitor session; retry or use a proxy if Sina shows a visitor challenge.

## `searchQueries` (type: `array`):

Keywords or phrases to search on Weibo. Anonymous runs can paginate through multiple result pages.

## `advancedSearchQueries` (type: `array`):

Keywords searched through the weibo.com advanced search endpoint with hot sorting and optional media/date filters.

## `topicQueries` (type: `array`):

Topic names such as 人工智能. The Actor wraps the value in #...#, returns matching posts and the topic card when available.

## `pictureSearchQueries` (type: `array`):

Keywords searched in Weibo's picture channel. Returns posts that contain pictures.

## `videoSearchQueries` (type: `array`):

Keywords searched in Weibo's video channel. Returns posts that contain video.

## `userSearchQueries` (type: `array`):

Keywords used to discover Weibo accounts. Returns user records with bio, followers, verification and profile URL.

## `userIds` (type: `array`):

Numeric Weibo UIDs or profile URLs such as https://weibo.com/u/2803301701. The actor returns the profile plus recent posts.

## `fanUserIds` (type: `array`):

Numeric UIDs or profile URLs whose fans/followers should be collected.

## `followingUserIds` (type: `array`):

Numeric UIDs or profile URLs whose following list should be collected.

## `postUrls` (type: `array`):

Post URLs such as https://m.weibo.cn/detail/5360224274749386 or bare numeric post IDs. The actor returns the post and optionally its comments.

## `likerPostUrls` (type: `array`):

Post IDs or URLs. Returns the accounts that liked each post. Anonymous access works for public posts.

## `repostPostUrls` (type: `array`):

Post IDs or URLs. Returns repost records. Weibo usually requires a logged-in cookie for repost timelines.

## `maxPosts` (type: `integer`):

Target number of post records across search, profile, topic, media, advanced-search and hot-timeline targets (0 = unlimited). Hot search, reposts, users and comments are counted separately.

## `fillToMaxPosts` (type: `boolean`):

Automatically request extra search and profile pages until Max posts is reached, even beyond the page limits below. Disable to use the page limits strictly.

## `maxSearchPages` (type: `integer`):

Initial result-page limit per keyword. With Fill to max posts enabled, the Actor extends this automatically when needed. Higher values can increase runtime.

## `maxProfilePages` (type: `integer`):

Initial timeline-page limit per profile. With Fill to max posts enabled, the Actor extends this automatically when needed. Weibo exposes up to about 100 indexed pages.

## `maxPagesPerTarget` (type: `integer`):

Page limit for topics, media searches, user searches, fans, following, likers and reposts.

## `maxItemsPerTarget` (type: `integer`):

Maximum users, likes, reposts or topics collected for each additional target.

## `maxHotTimelinePages` (type: `integer`):

How many hot-timeline batches to request. The default of 1 is usually enough for a trending snapshot.

## `advancedSearchIncludeType` (type: `string`):

Optional media filter for advanced searches. Leave empty for all posts.

## `advancedSearchSince` (type: `string`):

Optional start date in YYYY-MM-DD format. Used only when both start and end dates are set.

## `advancedSearchUntil` (type: `string`):

Optional end date in YYYY-MM-DD format. Used only when both start and end dates are set.

## `includeComments` (type: `boolean`):

Fetch top-level comments for every collected post. This adds requests and dataset rows.

## `maxCommentsPerPost` (type: `integer`):

Maximum new top-level comments to collect per post. In monitoring mode, already seen comments do not count toward this limit.

## `maxCommentPages` (type: `integer`):

Maximum comment pages inspected per post. Useful for finding new comments on posts that were already collected.

## `includeReplies` (type: `boolean`):

Fetch replies under collected comments. This can multiply the number of requests.

## `maxRepliesPerComment` (type: `integer`):

Maximum new replies to collect for each top-level comment. In monitoring mode, already seen replies do not count toward this limit.

## `maxReplyPages` (type: `integer`):

Maximum reply pages inspected per inline comment. Applies only when replies are enabled.

## `includeUserProfiles` (type: `boolean`):

Push a user record with bio, followers, verification and location when loading profiles or user search results.

## `includeFullText` (type: `boolean`):

Use Weibo's long-text endpoint when a post is truncated. Disable to reduce requests.

## `onlyNewItems` (type: `boolean`):

Skip posts and comments seen in previous runs. Useful for scheduled brand monitoring. Hot search and user profiles are always returned.

## `stateKey` (type: `string`):

Key-value store key used to remember seen IDs when Only new posts and comments is enabled. Use a different key for each independent monitor.

## `stateStoreName` (type: `string`):

Named key-value store that persists seen IDs across runs. Change it to keep independent monitors fully isolated.

## `weiboCookie` (type: `string`):

Optional browser Cookie header for logged-in-only data. Search, profile timelines and public comments work anonymously; leave empty for normal runs. Treat this value as a secret.

## `proxyConfiguration` (type: `object`):

Apify Proxy is enabled by default because Weibo can block direct Apify cloud egress. Disable it for local runs or if direct access works. Residential proxies are recommended for large or repeated runs.

## `requestDelayMillis` (type: `integer`):

Minimum delay between Weibo requests. Keep at least 500 ms to avoid rate limits.

## `maxRequestRetries` (type: `integer`):

How many times to retry network errors, HTTP 403/429 and server errors.

## Actor input object example

```json
{
  "hotSearch": true,
  "hotTimeline": false,
  "rankingCategories": [],
  "searchQueries": [
    "人工智能"
  ],
  "advancedSearchQueries": [],
  "topicQueries": [],
  "pictureSearchQueries": [],
  "videoSearchQueries": [],
  "userSearchQueries": [],
  "userIds": [
    "2803301701"
  ],
  "fanUserIds": [],
  "followingUserIds": [],
  "postUrls": [],
  "likerPostUrls": [],
  "repostPostUrls": [],
  "maxPosts": 10,
  "fillToMaxPosts": true,
  "maxSearchPages": 3,
  "maxProfilePages": 3,
  "maxPagesPerTarget": 3,
  "maxItemsPerTarget": 100,
  "maxHotTimelinePages": 1,
  "advancedSearchIncludeType": "",
  "advancedSearchSince": "",
  "advancedSearchUntil": "",
  "includeComments": false,
  "maxCommentsPerPost": 20,
  "maxCommentPages": 3,
  "includeReplies": false,
  "maxRepliesPerComment": 5,
  "maxReplyPages": 2,
  "includeUserProfiles": true,
  "includeFullText": true,
  "onlyNewItems": false,
  "stateKey": "weibo-pro-monitor",
  "stateStoreName": "weibo-monitor",
  "weiboCookie": "",
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "requestDelayMillis": 700,
  "maxRequestRetries": 3
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "rankingCategories": [],
    "searchQueries": [
        "人工智能"
    ],
    "advancedSearchQueries": [],
    "topicQueries": [],
    "pictureSearchQueries": [],
    "videoSearchQueries": [],
    "userSearchQueries": [],
    "userIds": [
        "2803301701"
    ],
    "fanUserIds": [],
    "followingUserIds": [],
    "postUrls": [],
    "likerPostUrls": [],
    "repostPostUrls": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("ahmed_jasarevic/weibo-scraper-pro").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "rankingCategories": [],
    "searchQueries": ["人工智能"],
    "advancedSearchQueries": [],
    "topicQueries": [],
    "pictureSearchQueries": [],
    "videoSearchQueries": [],
    "userSearchQueries": [],
    "userIds": ["2803301701"],
    "fanUserIds": [],
    "followingUserIds": [],
    "postUrls": [],
    "likerPostUrls": [],
    "repostPostUrls": [],
}

# Run the Actor and wait for it to finish
run = client.actor("ahmed_jasarevic/weibo-scraper-pro").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "rankingCategories": [],
  "searchQueries": [
    "人工智能"
  ],
  "advancedSearchQueries": [],
  "topicQueries": [],
  "pictureSearchQueries": [],
  "videoSearchQueries": [],
  "userSearchQueries": [],
  "userIds": [
    "2803301701"
  ],
  "fanUserIds": [],
  "followingUserIds": [],
  "postUrls": [],
  "likerPostUrls": [],
  "repostPostUrls": []
}' |
apify call ahmed_jasarevic/weibo-scraper-pro --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ahmed_jasarevic/weibo-scraper-pro"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/PD2kwlPVNPsgdQyjz/builds/ssQdUkGKUh7wW0wj0/openapi.json