VK Posts Scraper - Walls, Media & Engagement avatar

VK Posts Scraper - Walls, Media & Engagement

Pricing

from $1.60 / 1,000 results

Go to Apify Store
VK Posts Scraper - Walls, Media & Engagement

VK Posts Scraper - Walls, Media & Engagement

Scrape public VK profile and community posts without login, browser, or proxy. Export text, authors, dates, reactions, comments, reposts, views, media metadata, and source URLs.

Pricing

from $1.60 / 1,000 results

Rating

0.0

(0)

Developer

Thirdwatch

Thirdwatch

Maintained by Community

Actor stats

0

Bookmarked

55

Total users

17

Monthly active users

3 days ago

Last modified

Features

Limited permissions

Share

VK Posts Scraper

What you get

Scrape public VK profile and community posts without a VK login, API key, browser, or proxy. Export clean post rows with text, authors, dates, reactions, comments, reposts, views, media metadata, and stable source URLs.

The Actor reads VK's server-rendered structured post payloads over HTTP. That keeps runs fast and inexpensive while avoiding brittle scraping of localized button labels.

Quick start

Use a handle, public profile/community URL, wall URL, or direct post URL:

{
"targets": ["durov", "https://vk.com/wall1_2442097"],
"maxPostsPerTarget": 20,
"maxTotalPosts": 40
}

No cookies, credentials, API token, or account setup is required.

Inputs

InputWhat it controlsDefault
targetsPublic VK handles, profiles, communities, walls, and direct post URLsdurov
maxPostsPerTargetMaximum eligible posts saved from each target20
maxTotalPostsGlobal result cap across the run100
publishedAfterInclusive lower publication-date boundnone
publishedBeforeInclusive upper publication-date boundnone
includeRepostsInclude posts with copy historytrue
includePinnedInclude pinned poststrue
maxPagesPerTargetOptional cap on wall pages read per target; about 20 posts/pageSized to your post limit (up to 250 with a date range)

Supported target examples:

  • durov
  • club22822305
  • https://vk.com/durov
  • https://vk.com/id1
  • https://vk.com/wall1?own=1
  • https://vk.com/wall-22822305
  • https://vk.com/wall1_2442097
  • https://vk.com/durov?w=wall1_2442097 (a post opened from a wall or feed)

Output

Each eligible public post is one dataset row and one billable result:

{
"recordType": "vk_post",
"target": "durov",
"targetType": "profile",
"ownerId": 1,
"postId": 2442097,
"wallOwnerId": 1,
"wallPostId": 2442097,
"coPublished": false,
"sourceUrl": "https://vk.com/wall1_2442097",
"text": "...",
"postedAt": "2018-05-08T18:59:24Z",
"editedAt": "2018-05-08T21:10:26Z",
"isPinned": false,
"author": {
"id": 1,
"name": "Pavel Durov",
"screenName": "durov",
"profileUrl": "https://vk.com/durov",
"photoUrl": "https://...",
"verified": true
},
"engagement": {
"likesCount": 242724,
"commentsCount": 0,
"repostsCount": 14837,
"viewsCount": 15729030,
"reactions": []
},
"media": [],
"mediaTypes": [],
"repost": null,
"scrapedAt": "2026-08-12T00:00:00Z"
}

Posts that several communities publish together appear on each co-author's wall. They are included with coPublished: true; ownerId/postId identify the original post and wallOwnerId/wallPostId identify where it appears on the wall you scraped.

Top-level authorName, likesCount, commentsCount, repostsCount, and viewsCount fields are also included for convenient spreadsheet exports. The nested objects retain richer structured data.

Common workflows

  • Monitor brand or community announcements on scheduled runs.
  • Compare engagement across public profiles and communities.
  • Archive public posts and media metadata for research.
  • Track a date-bounded campaign or news event.
  • Feed public VK content into dashboards, warehouses, or alerting workflows.

Deduplication uses VK's stable (ownerId, postId) pair. If multiple inputs find the same post, it is saved and charged once per run.

Limitations and troubleshooting

  • Public pages only. Private, deleted, age-gated, login-only, or geographically unavailable content is not bypassed.
  • VK can expose different fields for different post and attachment types; absent source fields remain null or empty.
  • Direct URLs work only while VK continues to expose the public post.
  • Very old history requires more wall pages and more run time; VK serves about 20 posts per page. Use publishedAfter to stop early. If a run nears its time limit it stops, keeps every post collected so far, and says so in the log.
  • An empty dataset usually means the target is private, deleted, or not found (the log names it), or no post matched the date, repost, or pinned filters. If VK returns no readable page for any target, the run fails instead of finishing empty.
  • Use Apify schedules for monitoring and compare postId plus engagement counts across runs.

This Actor collects public data only. Use the output lawfully and respect privacy, data-protection, and platform requirements that apply to your use case.

Use cases

  • Marketers monitoring social presence and engagement
  • Researchers building social-media datasets
  • Teams tracking public figures and trends

Last verified: 2026-11

More scrapers at thirdwatch.dev.