# Likee Scraper - Video & Profile Data (`leadsbrary/likee-video-scraper`) Actor

Likee scraper for public videos and creator profiles: views, likes, comments, shares, captions, music and follower counts. Input profile URLs or usernames. Export JSON, CSV or Excel from $1/1,000 results.

- **URL**: https://apify.com/leadsbrary/likee-video-scraper.md
- **Developed by:** [Alexandre Manguis](https://apify.com/leadsbrary) (community)
- **Categories:** Social media, Videos, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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

## Likee Scraper - Video & Profile Data

Scrape public **Likee** (likee.video) videos and creator profiles in bulk. Give it profile URLs or plain usernames and get one flat row per video (or per profile) with play/like/comment/share counts, captions, hashtags, music, follower counts and cover-image URLs — ready to export as JSON, CSV or Excel. Pricing starts at **$1.00 per 1,000 results** (paid tiers), with no browser and no login required.

### Who it's for / use cases

- **Influencer vetting**: export all public videos of a list of Likee creators with engagement counts.
- **Trend spotting**: pull the latest videos of a watchlist of creators to spot trending sounds, captions and formats.
- **Creator shortlists**: build outreach lists with follower counts, bio, country and profile links.
- **Scheduled tracking**: re-run on a schedule to follow a creator's engagement over time.
- **BI feeds**: push Likee metrics into dashboards or spreadsheets via the Apify dataset API.

### Features

- Accepts full profile URLs (`https://likee.video/@username`) **and** plain usernames in the same run.
- Three result modes: `videos` (one row per video), `profiles` (one row per creator), or `both`.
- Hard `maxResults` cap enforced before billing — never overshoot your budget.
- Explicit, unbilled error rows for inputs that cannot be resolved (bad handle, private/removed content) — never a silent gap.
- One documented, stable schema: ISO 8601 dates, explicit `null` instead of empty strings.

#### What this Actor does **not** do

- **Video share links** (`likee.video/v/<id>`, `l.likee.video/...`) as input: Likee does not expose a working way to resolve these to a profile/video, so they return an unbilled `VIDEO_LINK_UNSUPPORTED` error row. Use the profile URL or username instead.
- **Hashtag input**: Likee's own hashtag/topic endpoints are broken on Likee's side at the time of writing, so any hashtag returns an unbilled `HASHTAG_UNSUPPORTED` error row. This field is reserved for when Likee's endpoint works again.
- No login, no account creation, no CAPTCHA solving, no access to private/removed/age-restricted content, no engagement actions (likes, follows, comments) and no re-hosting of video files — only the public URLs Likee itself publishes.

### Input

| Field | Type | Required | Description |
|---|---|---|---|
| `startUrls` | array | No | Likee profile URLs, e.g. `https://likee.video/@username`. Video share links are **not** supported and produce an unbilled `VIDEO_LINK_UNSUPPORTED` error row. |
| `usernames` | array | No | Likee handles without the `@` — a convenience alternative to `startUrls`. |
| `hashtags` | array | No | Reserved for future support, **not functional today**: produces an unbilled `HASHTAG_UNSUPPORTED` error row. |
| `resultType` | string | No | `videos` (default), `profiles` or `both`. |
| `maxResults` | integer | **Yes** | Hard cap on billed results for the whole run (default 100, prefill 10). |
| `maxVideosPerInput` | integer | No | Max videos collected per profile before moving to the next input (default 100). |
| `includeVideoUrls` | boolean | No | Include the direct media URLs Likee publishes (time-limited CDN links). Cover images come back; **direct MP4 links do not** — Likee's media endpoint refuses every video we tested, so `videoFileUrl` is `null` in practice today. Default `true`. |
| `proxyConfiguration` | object | No | Apify Proxy settings. Apify datacenter proxy is the default and is sufficient for this target. |

At least one of `startUrls`, `usernames` or `hashtags` must be provided.

### Output

One flat JSON object per result row. Key fields:

| Field | Type | Notes |
|---|---|---|
| `videoId` | string|null | Likee's own video/post id. |
| `videoUrl` | string|null | Best-effort public page URL built from Likee's own pattern (`likee.video/@user/video/id`). Likee's web frontend redirects plain HTTP requests to this pattern (even for known-valid videos) to a generic page regardless of client, so this URL is **not independently verifiable by an automated HTTP check** — open it in a browser/app, and prefer `shareUrl` when Likee populates it. |
| `shareUrl` | string|null | Share link returned directly by Likee's API; `null` when Likee leaves it empty (the common case observed in testing). |
| `caption` | string|null | Caption/title text. |
| `hashtags` | array | Hashtags parsed from the caption, without `#`. |
| `playCount`, `likeCount`, `commentCount`, `shareCount` | number|null | Public engagement counters. |
| `postedAt` | string|null | ISO 8601 UTC. |
| `musicTitle` | string|null | Sound/music title. |
| `coverImageUrl`, `videoFileUrl` | string|null | Cover thumbnail (populated) and direct MP4 CDN link (time-limited). `videoFileUrl` is only attempted when `includeVideoUrls` is true and is `null` in practice today: Likee's media endpoint returns an error for every video we tested. Do not buy this Actor for MP4 links. |
| `authorUsername`, `authorNickname`, `authorId`, `authorProfileUrl` | string|null | Creator identity. |
| `authorFollowerCount`, `authorFollowingCount`, `authorTotalLikes` | number|null | Creator stats. |
| `authorBio`, `authorCountry`, `authorAvatarUrl` | string|null | `authorCountry` is only populated on video rows; always `null` on profile rows. |
| `sourceInput` | string | The exact input that produced this row. |
| `sourceType` | string | `video`, `profile` or `hashtag`. |
| `scrapedAt` | string | ISO 8601 UTC extraction timestamp. |
| `error` | string|null | Present only on error rows (e.g. `PROFILE_NOT_FOUND`, `VIDEO_LINK_UNSUPPORTED`, `HASHTAG_UNSUPPORTED`); error rows are never billed. |

#### Sample output row (real run, 2026-10-02)

Copied from an actual run (`test/production-sample.json`). The only edit: the expiring `auth-token=` part of `authorAvatarUrl` is shortened to `...` — a real run returns the full signed URL.

```json
{
  "videoId": "7692116355021042996",
  "videoUrl": "https://likee.video/@Likee_Russia/video/7692116355021042996",
  "shareUrl": null,
  "caption": "Различие шаурмы за 100 и за 1000? 🌯 @Danya Bran 💥",
  "hashtags": [],
  "playCount": 15029,
  "likeCount": 420,
  "commentCount": 35,
  "shareCount": 15,
  "postedAt": "2026-10-02T17:00:02.000Z",
  "musicTitle": "Likee Russia",
  "coverImageUrl": "https://video.like.video/eu_live/9u1/01wySW3qmPVN_4.jpg?wmk_sdk=1",
  "videoFileUrl": null,
  "authorUsername": "Likee_Russia",
  "authorNickname": "Likee Russia",
  "authorId": "30004",
  "authorProfileUrl": "https://likee.video/@Likee_Russia",
  "authorFollowerCount": 109077616,
  "authorFollowingCount": 3539,
  "authorTotalLikes": 82058192,
  "authorBio": null,
  "authorCountry": "RU",
  "authorAvatarUrl": "https://img.like.video/asia_live/4hb/0tQMTk_4.png?type=20&auth-token=...",
  "sourceInput": "https://likee.video/@Likee_Russia",
  "sourceType": "video",
  "scrapedAt": "2026-10-02T21:24:09.714Z",
  "error": null
}
```

Measured on a 5-item production run (run `Jt5gOrkPDLaoLasPd`): 100% fill rate on `sourceInput`, `sourceType`, `scrapedAt`, `videoId`, `videoUrl`, `caption`, the four engagement counters, `postedAt`, `coverImageUrl` and the author fields; 0 duplicates, 0 schema errors. `shareUrl` and `videoFileUrl` were `null` on all 5 rows (see the notes above — Likee leaves `shareUrl` empty on the accounts we tested and returns no MP4 link), and `authorBio` was empty on this account.

### How to use via API

#### cURL

```bash
curl "https://api.apify.com/v2/acts/YOUR_USERNAME~likee-video-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "usernames": ["Likee_Russia"],
    "resultType": "videos",
    "maxResults": 10
  }'
```

#### JavaScript (apify-client)

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

const client = new ApifyClient({ token: 'YOUR_TOKEN' });

const run = await client.actor('YOUR_USERNAME/likee-video-scraper').call({
    usernames: ['Likee_Russia'],
    resultType: 'videos',
    maxResults: 10,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

#### Python (apify-client)

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")

run = client.actor("YOUR_USERNAME/likee-video-scraper").call(run_input={
    "usernames": ["Likee_Russia"],
    "resultType": "videos",
    "maxResults": 10,
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)
```

### Pricing

Pay-per-result (`PAY_PER_EVENT`, billing event = `result`). Only successfully delivered, non-error rows are billed — error rows (unresolved input, unsupported link/hashtag, private content) are free.

| Plan | Price per 1,000 results |
|---|---|
| Free | $1.50 |
| Paid (Bronze/Silver/Gold and above) | from $1.15 down to **$1.00** |

### Troubleshooting

- **A username returns an error row (`PROFILE_NOT_FOUND`)**: the handle is misspelled, renamed, banned or region-restricted. Double-check the handle on likee.video.
- **A `startUrls` entry returns `VIDEO_LINK_UNSUPPORTED`**: you passed a video share link; use the creator's profile URL or plain username instead.
- **A hashtag returns `HASHTAG_UNSUPPORTED`**: hashtag collection is not functional today because Likee's own hashtag endpoint is broken; this is not a bug in the Actor.
- **`videoFileUrl` is `null`**: expected. Likee's media endpoint (`getVideoInfo`) answers with an error code for every video we tested, so no direct MP4 link is available today; use `coverImageUrl` for the thumbnail. It is also `null` when `includeVideoUrls` is `false`.
- **Run ends with a validation error and nothing billed**: provide at least one of `startUrls`, `usernames` or `hashtags`.

### FAQ

**Does Likee have an official public API?**
No. Likee has no official, publicly documented data API, which is why this Actor reads Likee's own public page payloads/JSON endpoints — the same ones your browser loads when you visit likee.video, without logging in.

**Can I scrape private or follower-only profiles?**
No. Only data Likee makes visible to anonymous visitors is collected; private, removed or age-restricted content returns an error row, never a bypass attempt.

**Is a proxy required?**
Apify's datacenter proxy is enabled by default and is sufficient for this target.

**What counts as a billable result?**
Each successfully delivered video or profile row. Error rows (bad input, unsupported link/hashtag, not-found content) are never billed.

### Keywords

likee scraper, likee video scraper, likee profile scraper, likee api, likee data export, likee creator analytics, scrape likee.video, likee video metadata, likee follower count export, likee trending videos

### Hashtags

\#likee #likeescraper #webscraping #socialmedia #shortvideo #influencermarketing #datascraping #apify #creatoreconomy

# Changelog

This Actor's version history is a separate document: https://apify.com/leadsbrary/likee-video-scraper/changelog.md

# Actor input Schema

## `startUrls` (type: `array`):

Likee profile URLs, e.g. https://likee.video/@<username>. Video share links (likee.video/v/<id>) are not supported yet and produce an error row.

## `usernames` (type: `array`):

Likee usernames/handles without the @ — a convenience alternative to startUrls.

## `hashtags` (type: `array`):

Reserved for future support. Likee's hashtag/topic endpoints are currently broken on Likee's side, so any hashtag here produces a HASHTAG_UNSUPPORTED error row and is never billed.

## `resultType` (type: `string`):

What to emit per input: one row per video, one row per creator profile, or both.

## `maxResults` (type: `integer`):

Hard cap on billed results for the whole run; protects your spending.

## `maxVideosPerInput` (type: `integer`):

Maximum videos collected per profile before moving to the next input.

## `includeVideoUrls` (type: `boolean`):

Include the media URLs Likee publishes (time-limited CDN links). Cover images are returned; direct MP4 links are not available today — Likee's media endpoint refuses every video we tested, so videoFileUrl stays null.

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

Apify datacenter proxy is the default and proven sufficient for this target.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://likee.video/@Likee_Russia"
    }
  ],
  "usernames": [],
  "hashtags": [],
  "resultType": "videos",
  "maxResults": 10,
  "maxVideosPerInput": 10,
  "includeVideoUrls": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (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 = {
    "startUrls": [
        {
            "url": "https://likee.video/@Likee_Russia"
        }
    ],
    "usernames": [],
    "hashtags": [],
    "resultType": "videos",
    "maxResults": 10,
    "maxVideosPerInput": 10,
    "includeVideoUrls": true,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("leadsbrary/likee-video-scraper").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 = {
    "startUrls": [{ "url": "https://likee.video/@Likee_Russia" }],
    "usernames": [],
    "hashtags": [],
    "resultType": "videos",
    "maxResults": 10,
    "maxVideosPerInput": 10,
    "includeVideoUrls": True,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("leadsbrary/likee-video-scraper").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 '{
  "startUrls": [
    {
      "url": "https://likee.video/@Likee_Russia"
    }
  ],
  "usernames": [],
  "hashtags": [],
  "resultType": "videos",
  "maxResults": 10,
  "maxVideosPerInput": 10,
  "includeVideoUrls": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call leadsbrary/likee-video-scraper --silent --output-dataset

```

## MCP server setup

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

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/WyAbyrvofGurt9UOa/builds/RH8VvipnnqybWDFRi/openapi.json