Flippa Listings Scraper

Extract public Flippa marketplace listings for acquisition research, deal monitoring, broker analysis, and online-business intelligence. The Actor saves structured listing records with prices, revenue/profit metrics, verification flags, categories, seller/listing badges, and direct deal URLs.

Use it when you need repeatable Flippa data collection with CSV, JSON, Excel, API, MCP, or webhook workflows.

At a glance

• Primary job: Collect public Flippa listings for websites, ecommerce stores, SaaS assets, apps, domains, and content businesses.
• Input: Use Flippa search/category URLs, direct listing URLs, property filters, price/revenue ranges, or monitoring mode.
• Output: One dataset row per unique public listing, keyed by listingId and url.
• Best for: Acquisition sourcing, valuation research, daily listing syncs, market maps, and investor/broker dashboards.

Common workflows

• Acquisition sourcing: Search websites, SaaS, or ecommerce listings under a budget and export revenue/profit metrics.
• Deal monitoring: Schedule small ID-sync runs and compare fresh listing IDs with previous datasets.
• Broker research: Build lists of public Flippa opportunities by category, status, verification, and asking price.
• Data enrichment: Feed Flippa listing URLs and hostnames into CRMs, spreadsheets, BI tools, or other Apify Actors.
• Automation: Trigger webhooks or API jobs when a matching deal appears.

Input recipes

Use these recipes before public Store examples are created.

Websites under $50k

{
  "propertyTypes": ["website"],
  "priceMax": 50000,
  "maxItems": 25,
  "includeDetails": true
}

SaaS revenue listings

{
  "propertyTypes": ["saas"],
  "revenueMin": 1000,
  "maxItems": 25,
  "includeDetails": true
}

Direct listing detail audit

{
  "startUrls": [{ "url": "https://flippa.com/13526433" }],
  "maxItems": 1,
  "includeDetails": true
}

Daily ID sync for a saved category

{
  "propertyTypes": ["website"],
  "mode": "idSync",
  "includeDetails": false,
  "maxItems": 50
}

What data can you extract?

Example input

{
  "propertyTypes": ["website"],
  "maxItems": 10,
  "includeDetails": true,
  "verifiedOnly": false,
  "sort": "most_relevant"
}

Example output

{
  "listingId": "13526433",
  "url": "https://flippa.com/13526433-recipe-blog-on-wordpress-w-hbagency-and-adsense-income-ai-content-system-and-free-pinterest-traffic-260-mo-revenue-only-10-mo-35-yr-costs",
  "title": "Recipe blog on WordPress w/ HBAgency and AdSense income",
  "propertyName": "Kitch Recipes",
  "propertyType": "content_site",
  "industry": "food-and-drink",
  "saleMethod": "auction",
  "status": "open",
  "currentPrice": 2200,
  "displayPrice": 2800,
  "buyItNowPrice": 3000,
  "monthlyRevenue": 159,
  "monthlyProfit": 147,
  "hasVerifiedRevenue": true,
  "hasVerifiedTraffic": true,
  "hostname": "kitchrecipes.com",
  "confidential": false,
  "sourceUrl": "https://flippa.com/13526433",
  "scrapedAt": "2026-07-26T08:33:11.135Z",
  "missingFields": [],
  "errors": []
}

Tips for best results

• Start small: Use maxItems: 10-25 until your filters return the right type of deal.
• Use Flippa URLs: Direct listing URLs are best for detail audits; search/category URLs are best for sourcing.
• Keep monitoring runs focused: Use idSync with includeDetails: false for cheap daily change detection.
• Review empty runs: A true zero-result run is valid only when Flippa reports no matching listings.
• Do not add credentials: This Actor is designed for public marketplace data only.

API usage

Node.js:

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor("fetch_cat/flippa-listings-scraper").call({
  propertyTypes: ["website"],
  maxItems: 10,
  includeDetails: true
});
console.log(run.defaultDatasetId);

Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("fetch_cat/flippa-listings-scraper").call(run_input={
    "propertyTypes": ["website"],
    "maxItems": 10,
    "includeDetails": True,
})
print(run["defaultDatasetId"])

cURL:

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~flippa-listings-scraper/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"propertyTypes":["website"],"maxItems":10,"includeDetails":true}'

MCP and AI agents

Use this Actor from MCP-compatible tools through the official Apify MCP Server.

claude mcp add --transport http apify "https://mcp.apify.com?tools=fetch_cat/flippa-listings-scraper"

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/flippa-listings-scraper"
    }
  }
}

Example prompt: "Run Flippa Listings Scraper for website listings under $50k and summarize verified revenue opportunities."

Limits and caveats

• Public data only: The Actor does not use Flippa credentials, private deal rooms, messages, watchlists, or account-only documents.
• Marketplace variability: Some listings hide metrics, mark fields confidential, or omit optional values.
• Source changes: Flippa can change filters, field names, or availability; row diagnostics help identify missing optional fields.
• Not valuation advice: Use output as research data, not as financial, legal, tax, or investment advice.

Legality and responsible use

Process only public data you are allowed to access. Follow Flippa's terms, Apify's terms, and applicable laws. Respect confidentiality flags and do not attempt to bypass access controls.

Support

Open an issue from the Actor page if a run fails or output looks wrong. Include the run ID or run URL, input JSON, expected output, actual output, and a reproducible public URL from Flippa.