Bark Real-Time Data

⚠️ Free-tier notice: on Apify free plans this Actor exports a small sample of results per run (2 rows by default). Upgrade to a paid Apify plan for full, unlimited exports.

Collect Bark.com directory data at scale: local service professionals and businesses by category and city — with full profile details and lead enrichment (business website, emails, social profiles). Structured JSON is streamed to your dataset in real time as each record is collected.

Bark is one of the largest local-services marketplaces, covering accountants, personal trainers, web designers, photographers, cleaners, DJs, dog trainers and 1,000+ more service categories across the US, UK, Canada, Ireland, Australia and beyond.

Who is this for?

• Lead-gen agencies and outreach teams — build local prospect lists by service category and city, with contact details for CRM import.
• Local SEO and directory researchers — track which businesses are listed, rated and badged in each market.
• Marketplaces and platforms — monitor competitor supply density per category per city.
• CRMs and data pipelines — stream every record to a webhook (Zapier, Make, Slack, Google Sheets) the moment it is collected.
• Franchise and sales teams — find under-served categories and cities.
• AI agents — connect via the Apify MCP server and query live directory data in natural language.

Features

Feature	Input toggle	What you get
🔎 Directory search	Directory search (default on)	Professionals by service category and city. One row per search task; category + location + per-task max results.
🔗 Profile URLs	Profile URLs	Full details for specific Bark profile URLs you already have (/company/... or /b/...).
🎯 Lead details	Enable lead details	Enriches every row in place: all listed categories, response time, hires on Bark, public reviews, business website, contact emails and social profiles when discoverable. Nothing is filtered — rows without leads are still exported.
🔔 Webhooks	Webhook URL + Webhook format	Each record POSTed to your URL in JSON or Slack format, fire-and-forget, in addition to the dataset.
🌐 Connection	Proxy settings	Apify residential proxy (US) enabled by default.

Directory search details

Each search task row takes:

• Category — any Bark service category, e.g. Accountants, Personal Trainers, Web Design, Wedding Photographers, Dog Training. Free text; the closest matching listing is used.
• Location (optional) — City, ST for the US (e.g. New York, NY, Austin, TX), or just City for other markets (e.g. London). Leave empty to search the category across all locations.
• Max results — cap for that one search task. The first number you should reach for.

A quick, useful first run: leave everything at defaults and click Start — you get 10 Accountants in New York, NY in seconds.

Input reference

Field	Type	Default	Notes
enableSearch	boolean	true	Master switch for directory search.
searchTasks	array	1 demo task	One row per category/location search.
searchTasks[].category	string	—	Service category (required per task).
searchTasks[].location	string	—	City, ST (US) or City. Optional.
searchTasks[].maxResults	integer	—	Per-task cap.
enableScrapeByUrl	boolean	false	Collect full details for specific profile URLs.
scrapeUrls	string[]	[]	Bark profile URLs.
enableLeadDetails	boolean	false	Enrich rows in place with full details + lead contacts. Adds a little extra time per record.
concurrency	integer	2	Parallel lead-details enrichments (1–4).
webhookUrl	string	""	Optional extra real-time push per record.
webhookFormat	select	json	json (full record) or slack (Slack message).
proxyConfiguration	proxy	Residential US	Apify proxy settings.

Realistic input examples

{
    "enableSearch": true,
    "searchTasks": [
        { "category": "Personal Trainers", "location": "Austin, TX", "maxResults": 25 },
        { "category": "Wedding Photographers", "location": "Chicago, IL", "maxResults": 25 }
    ],
    "enableLeadDetails": true,
    "concurrency": 3
}

{
    "enableSearch": true,
    "searchTasks": [
        { "category": "Accountants", "location": "London", "maxResults": 20 }
    ],
    "enableLeadDetails": false
}

{
    "enableScrapeByUrl": true,
    "scrapeUrls": [
        "https://www.bark.com/en/us/company/trans-america/ak0D1/"
    ],
    "enableLeadDetails": true
}

Output field reference

One dataset row per professional. All fields may be absent unless noted.

Field	Type	Description
type	string	Always "pro".
platform	string	Always "bark".
featureType	string	search or scrape_by_url.
name	string	Business / professional name.
profileUrl	string	Bark profile URL.
profileId	string	Short profile id from the URL.
category	string	Category this row was collected under.
description	string	Business description (card blurb, or full About text with lead details).
imageUrl	string	Logo/avatar image URL.
rating	number	Rating 0–5.
reviewCount	integer	Number of public reviews.
certificateOfExcellence	boolean	Bark Certificate of Excellence badge.
cardLocation	string	Location line as listed on the card.
city / state / country	string	Parsed location parts.
categories	string[]	Every service category listed on the profile (lead details).
responseTime	string	e.g. "20 min response time" (lead details).
hiresOnBark	integer	Completed hires on Bark (lead details).
servicesRemotely	boolean	Offers remote services (lead details).
cardReviews	array	Public review highlights: author, rating, date, text.
website	string	Business website (lead details, when discoverable).
email / emails	string / string[]	Contact emails from the business website (lead details).
socials	string[]	Social profile URLs (lead details).
instagram / facebook / linkedin / twitter	string	One handle per network (lead details).
searchLocation / searchTaskIndex / searchTaskLabel	mixed	Which search task produced this row.
leadDetails	boolean	Lead details pass ran for this row.
detailsFetched	boolean	Full profile details were fetched for this row.
scrapedAt	string	ISO timestamp of collection.

Run-level metadata (totals, duration, errors, spend/paywall status) is written to the OUTPUT key-value store entry.

Webhook guide

Set Webhook URL and each record is pushed to your URL the moment it is saved, in addition to the dataset.

JSON format — the full record object, exactly as stored in the dataset:

{
    "type": "pro",
    "platform": "bark",
    "featureType": "search",
    "name": "Lanyap Financial Services",
    "profileUrl": "https://www.bark.com/en/us/company/lanyap-financial-services/0mJlK/",
    "category": "Accountants",
    "rating": 5,
    "reviewCount": 7,
    "city": "New York",
    "scrapedAt": "2026-09-29T12:00:00.000Z"
}

Slack format — a ready-to-post Slack message:

{ "text": ":briefcase: *Lanyap Financial Services*\n*Category:* Accountants  •  *Location:* New York\n*Rating:* 5★ (7 reviews)\n<https://www.bark.com/en/us/company/lanyap-financial-services/0mJlK/|View profile>" }

Works with Slack incoming webhooks, Zapier, Make, n8n, Google Sheets apps and any custom receiver. Delivery failures never stop the run.

MCP / AI-agent usage

Connect the Apify MCP Server and ask:

"Find 10 accountants in New York with a 4.5+ rating and their websites, and put them in a table."

The agent runs this Actor with the matching search task and lead details enabled, then reads the dataset.

FAQ

Do I need my own proxies? No. Apify residential proxies (US) are used by default and are included in your platform usage. You can point the proxy settings at your own provider if you prefer.

How fresh is the data? Every run collects live directory data at the moment you press Start — nothing is cached between runs.

What do free Apify plans get? A small sample of results per run (2 rows by default). Paid plans get the full, unlimited export. The run summary always states whether a cap was applied.

Why do some rows have no website or email? Not every business publishes contact details on its profile or website. Rows are never filtered out — you always see every professional the search found, with whatever details are discoverable.

Does location have to be exact? Use City, ST for US cities (e.g. New York, NY) or a plain city name elsewhere (London). If a listing can't be found for a task, the run logs it clearly and moves on.