VK Community Scraper – Groups & Public Pages

Collect public information about VK groups, public pages, and event communities from their screen names. VK Community Scraper returns descriptions, member and content counts, websites, images, published contacts, locations, and available business or event details.

Use it to build a community directory, research organizations, or compare the public presence of known brands. Every unique processed community becomes one row with its details in the same table and JSON export.

At a glance	Details
📥 Input	Plain VK community screen names, such as vk
📤 Output	Identity, description, counts, images, contacts, links, and available business or event fields
🏢 Coverage	Publicly exposed group, public-page, and event-community data
🔐 Login required	No VK credentials or cookies
💾 Delivery	One row per unique processed screen name

What the VK community scraper extracts 🏢

Available community data includes:

• ID, screen name, name, community URL, type, and activity category
• Description, status text, website, and membership or content counts
• Avatar sizes, cover images, and image dimensions
• City, country, address, and coordinates when published
• Public contact entries and named links
• Verification, closure, age-limit, and access indicators
• Event start, finish, and status fields when supplied
• Available market, business, action-button, channel, address, and menu details

These are community-level fields. Use Community Posts Scraper when you need individual wall posts or a paginated content collection.

How to scrape VK community details 🚀

1. Add community screen names such as vk.
2. Omit the @ prefix and full VK links.
3. Start the Actor and review success and failed rows.
4. Export the dataset or connect it to your community-research workflow.

{
  "inputList": [
    "vk"
  ]
}

Screen names are normalized to lowercase and duplicate names are processed once. The Actor verifies that the target is a community; user profiles belong in Profile Details Scraper.

VK community fields and output 📦

Field group	Included data
Community identity	ID, screen name, name, type, activity, URL, avatar, and cover
Description and audience	Description, status, website, member count, and content totals
Public contact and place	Contacts, named links, city, country, address, and coordinates
Community settings	Verification, closure, age, membership, and access indicators
Event details	Start and finish timestamps, dates, and event status
Additional sections	Market, business, action button, channel, addresses, and menu

Complete illustrative output item with all 77 fields. The community and values below are fictional examples, not a live result:

{
  "input": "sample.workshop",
  "status": "success",
  "avatar_url": "https://example.com/community-400.jpg",
  "community_url": "https://vk.ru/sample.workshop",
  "id": 12345678,
  "username": "sample.workshop",
  "name": "Example Photography Workshop",
  "type": "page",
  "activity": "Photography",
  "description": "Public photography workshops and community events.",
  "community_status": "New workshop dates are available",
  "website": "https://example.com/workshops",
  "members_count": 8200,
  "friends_count": 0,
  "posts_count": 250,
  "photos_count": 680,
  "videos_count": 22,
  "clips_count": 14,
  "articles_count": 8,
  "topics_count": 5,
  "docs_count": 2,
  "addresses_count": 1,
  "avatar_thumbnails.size": [
    "100",
    "400_orig"
  ],
  "avatar_thumbnails.url": [
    "https://example.com/community-100.jpg",
    "https://example.com/community-400.jpg"
  ],
  "cover_url": "https://example.com/community-cover.jpg",
  "cover_images.url": [
    "https://example.com/community-cover.jpg"
  ],
  "cover_images.width": [
    1590
  ],
  "cover_images.height": [
    400
  ],
  "city.id": 1,
  "city.name": "Moscow",
  "country.id": 1,
  "country.name": "Russia",
  "address": "Workshop studio",
  "latitude": "55.75",
  "longitude": "37.62",
  "contacts.user_id": [
    123456789
  ],
  "contacts.name": [
    "Alex Morgan"
  ],
  "contacts.description": [
    "Workshop coordinator"
  ],
  "contacts.phone": [
    ""
  ],
  "contacts.email": [
    "workshops@example.com"
  ],
  "links.id": [
    42
  ],
  "links.name": [
    "Workshop schedule"
  ],
  "links.description": [
    "Dates and registration"
  ],
  "links.url": [
    "https://example.com/workshops"
  ],
  "links.photo_url": [
    "https://example.com/workshop-thumbnail.jpg"
  ],
  "is_verified": false,
  "is_closed": false,
  "closed_type": 0,
  "is_member": false,
  "is_advertiser": false,
  "is_no_index": false,
  "age_limits": 0,
  "main_section": 0,
  "member_status": 0,
  "can_access_closed": true,
  "can_message": false,
  "can_post": false,
  "can_see_all_posts": true,
  "can_upload_doc": false,
  "can_upload_video": false,
  "start_at": 0,
  "start_date": "",
  "finish_at": 0,
  "finish_date": "",
  "event_status": "",
  "market.path": [
    "/enabled"
  ],
  "market.value": [
    false
  ],
  "business_data.path": [
    "/company_name"
  ],
  "business_data.value": [
    "Example Photography Workshop"
  ],
  "action_button.path": [
    "/type",
    "/url"
  ],
  "action_button.value": [
    "open_url",
    "https://example.com/workshops"
  ],
  "community_channel.path": [],
  "community_channel.value": [],
  "addresses.path": [
    "/main_address/id",
    "/main_address/address"
  ],
  "addresses.value": [
    1,
    "Workshop studio"
  ],
  "menu.path": [],
  "menu.value": []
}

Each community occupies one row in one table. JSON keys such as city.name match the table columns. Contact, link, avatar, and cover lists align by position within each group.

Variable sections use paired lists such as business_data.path and business_data.value. Each path identifies a field and matches the value at the same list position. For example, /company_name identifies the published business name. Market, action-button, channel, address, and menu fields follow the same pattern.

Successful rows can contain empty strings, empty lists, 0, or false when VK omits values. Empty event dates on a regular public page are expected. Failed rows retain input, set status to failed, and use null for the other fields.

Input requirements and community coverage ⚙️

Parameter	Type	Required	Rules
inputList	array of strings	Yes	At least one VK community screen name

Screen names must contain 1–64 letters, digits, underscores, or periods. Surrounding whitespace is trimmed. Accepted: vk. Rejected: @vk, https://vk.ru/vk, or a name containing spaces.

The resolved target must be a community rather than a user. Groups, public pages, and event communities can have different optional fields. Closed communities may expose some public details or be unavailable; closure and access indicators do not provide access to hidden content.

There is no pagination setting. Membership and content counts are aggregate values, not lists of members, photos, or posts.

VK community data use cases 🎯

Community directories

Collect names, categories, descriptions, websites, and public contact entries for a known list of communities.

Brand-presence research

Compare member counts, activity categories, links, and content totals across public brand pages.

Public business enrichment

Add published addresses, action links, and business details to organization records when those fields are exposed.

Event-community research

Collect public event timing, status, description, and location fields without assuming every community is an event.

Pricing and billable community rows 💰

Check the Actor's Pricing tab for the current charging model and rate.

Under dataset-item pricing, each saved success or failed row can count as one result. Duplicate screen names are normally processed once, and automatic retries do not independently add rows.

Contacts, links, images, and variable business sections remain in the community row. They are not additional dataset items.

VK community API and integrations 🔌

Use the Actor ID shown in the API tab for $ACTOR_ID and your Apify token for $APIFY_TOKEN:

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["vk"]}'

Run the Actor through REST, Apify client libraries, schedules, or webhooks. Send the default dataset to a spreadsheet, directory, Make, Zapier, CRM enrichment workflow, or your own reporting service.

Reliability and public community limits ⚠️

The Actor processes up to five requests concurrently and retries temporary request failures. Invalid names, unavailable communities, and user profiles submitted as communities produce failed rows while other targets continue.

VK may omit member counts, contacts, business sections, or access flags. Missing counts can default to zero and omitted indicators to false; do not treat these defaults as independently verified facts. Viewer-related membership and permission fields describe the public response.

Community names, settings, and public availability can change. Image URLs may expire, and binary files are not downloaded. An inability to save the dataset can stop a run.

Frequently asked questions ❓

Does it work with groups and public pages?

Yes. It collects the community data VK exposes for groups, public pages, and event communities. Optional fields vary by community type.

Can I enter a full VK link?

Enter only the screen name. For https://vk.ru/vk, submit vk.

Does it return community members or posts?

It returns counts and community details. Use Community Posts Scraper for individual wall posts; this Actor does not collect member lists.

Are contacts and addresses always available?

They appear only when VK supplies them publicly. A successful community row can have empty contact, location, or business fields.

Why are event dates empty?

Regular groups and public pages may have no event dates. Event communities can also omit timing fields in the public response.

How are variable business fields represented?

Match each path to the value at the same list position. These paired columns keep the details in one community row without a JSON object in a cell.

Support, responsible use, and related actors 🛟

For a reproducible issue, share the run ID, a public community screen name, and the expected field or behavior through the Actor's support channel.

Use public community data in accordance with applicable privacy, contractual, copyright, and platform requirements.