Flippa Listings Scraper avatar

Flippa Listings Scraper

Pricing

from $0.48 / 1,000 item extracteds

Go to Apify Store
Flippa Listings Scraper

Flippa Listings Scraper

Scrape public Flippa marketplace listings with prices, revenue, profit, verification flags, categories, seller badges, and deal URLs.

Pricing

from $0.48 / 1,000 item extracteds

Rating

0.0

(0)

Developer

Fetch Cat

Fetch Cat

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

3 hours ago

Last modified

Features

Limited permissions

Share

Export public Flippa marketplace listings for acquisition research and deal shortlists. Collect listing URLs, asking prices, available revenue and profit figures, and verification flags in a dataset you can download as CSV, JSON or Excel.

Start with a small property-type search. Public detail coverage varies. Search terms are forwarded to Flippa's keyword search.

Connection choice: the form explicitly selects the tested paid Apify residential proxy in Australia (AU). API inputs that omit proxy settings, and explicit useApifyProxy:false, stay direct and may be refused. There is no automatic paid fallback or migration of saved tasks. To use the recommended connection in an API call, explicitly include "proxyConfiguration":{"useApifyProxy":true,"apifyProxyGroups":["RESIDENTIAL"],"apifyProxyCountry":"AU"}. Startup billing may apply even when blocked; blocked requests produce no listing charges.

Quick start

  1. Choose a property type such as website or paste a Flippa listing URL.
  2. Review the explicitly selected paid AU residential connection, set maxItems to a small limit and run the Actor.
  3. Open the dataset to review the records and download your results.
{
"propertyTypes": ["website"],
"proxyConfiguration": {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "AU"},
"priceMax": 50000,
"maxItems": 10,
"includeDetails": true
}

Filters depend on Flippa's current support. A result limit is a ceiling, not a promise of that many matching listings.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

What you get

One row per unique saved public listing, with source identity, asking-price fields and available business figures or verification indicators. Detail failures retain useful rows with errors and fail the run; use includeDetails:false explicitly for search-only collection. Public financial and traffic values are source claims rather than independently audited figures.

Who is it for?

  • Acquisition researchers preparing a source-linked shortlist for manual review.
  • Marketplace analysts comparing public asset and asking-price samples.
  • Research agencies organizing available listing details for client review.
  • Data teams keeping dated marketplace observations in their own reports.

How you can use the data

  • Prepare a small website shortlist. Use the existing website filter and maximum asking price of 50,000 USD with a small item cap. Keep listingId, url, propertyType, currentPrice and available monthlyRevenue together, then inspect the published source claims.
  • Keep missing financial information visible. Review missingFields and errors beside revenue or profit values. Unavailable numeric values remain null rather than becoming zero.
  • Inspect a known listing directly. Supply its public listing URL. Search filters do not constrain direct lookup, and direct URLs always request details regardless of the search-enrichment setting.
  • Compare your own saved snapshots. Use listing IDs and source links with scrapedAt in your own reporting. The idSync mode skips extra search-detail visits but retains the same schema rather than producing IDs only. Search terms use Flippa's keyword matching, not local title-only matching.

Input settings

SettingJSON keyBehavior
Flippa start URLsstartUrlsSearch URLs with filter[...] parameters, or direct listing URLs. Ordinary category paths alone do not select a category.
Property typespropertyTypesProperty filters such as website, saas or ecommerce.
Maximum listingsmaxItemsSave at most this many unique listings, from 1 to 10,000. The form defaults to 10. API omission uses 25.
Include detailsincludeDetailsFor search results, request additional public details when available. Omission behaves as true. Direct listing URLs always request details.
Run modemodefull allows detail requests. idSync skips extra detail requests for search results but retains the same output fields. It is not an IDs-only export.
Price and revenue rangespriceMin, priceMax, revenueMin, revenueMaxPass price and monthly-revenue bounds in USD.
Status and sale methodsstatus, saleMethodsPass Flippa status and sale-method filters where supported.
Verified onlyverifiedOnlyKeep records whose public data indicates verified revenue or traffic. This can reduce results.
Sort ordersortPass Flippa's sort value. Results are not sorted locally. The form defaults to most_relevant. API omission adds no sort value.
Search termsqueriesForwarded as query[keyword] and saved as sourceQuery. Flippa controls matching.
Proxy configurationproxyConfigurationThe form explicitly selects paid RESIDENTIAL/AU. API omission or false stays direct without fallback and may be blocked. Explicit true honors supplied settings.

Supply at least one non-empty startUrls, queries or propertyTypes array. These are alternatives, not three required inputs. Form prefills are examples, not guaranteed API inputs. Search filters do not constrain a direct listing lookup.

For a smaller search snapshot without additional details:

{
"propertyTypes": ["website"],
"proxyConfiguration": {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "AU"},
"mode": "idSync",
"includeDetails": false,
"maxItems": 10
}

Output data

Each saved row represents one unique listing within the run. Availability depends on what Flippa exposes publicly. Detail failures can leave a useful search record with an errors entry.

FieldsMeaning and limitations
listingId, url, title, summaryListing identity, deal link and public description.
propertyName, propertyType, industry, category, monetizationAsset classification when available.
currentPrice, displayPrice, buyItNowPrice, currencyPublic price fields. displayPrice may be text or a number. Currency is labelled USD.
monthlyRevenue, monthlyProfit, pageViewsPerMonthPublic business figures when available. Not independently audited.
hasVerifiedRevenue, hasVerifiedTrafficVerification indicators supplied by Flippa.
saleMethod, status, bidCount, endsAt, establishedAtSale context and timing. establishedAt preserves the source value as text, not necessarily a date.
hostname, externalUrl, countryName, thumbnailUrlOptional public website, location and image fields.
badges, sellerBadges, integrations, confidential, earlyAccessAvailable public flags and lists. Coverage varies by source.
sourceUrl, sourceQuery, scrapedAtRequest provenance, optional query label and collection timestamp.
missingFields, errorsSelected missing-source indicators and detail-request errors. Not a complete validation report.

Missing numeric values are null; rounded figures on search cards may become more precise when public details are available. The legacy annualOrganicTraffic field contains a monthly unique-visitor value when present, not annual organic traffic. authorityScore is currently always null. Do not use either field as a verified annual-traffic or authority metric.

Shape-only excerpt, not an observed listing or a complete row:

{
"listingId": "12345678",
"url": "https://flippa.com/12345678",
"title": null,
"monthlyRevenue": null,
"hasVerifiedRevenue": null,
"authorityScore": null,
"sourceQuery": null,
"missingFields": ["average_revenue", "average_profit", "page_views_per_month"],
"errors": []
}

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing uses a one-time start event after input validation and an item event for each saved listing. Rows with detail-error diagnostics still count as saved items. There are no separate paid status rows.

Use the item cap and review your run charge limit to bound collection. Check the Pricing tab for current amounts and plan discounts.

Tips for best results

  • Use property, keyword and price filters for a focused sample. Numeric bounds are also checked locally; other filters depend on Flippa's support.
  • Choose full details or idSync deliberately. The latter skips extra search-detail requests without changing the output fields.
  • Keep direct lookups separate from filter assumptions. A supplied listing URL is not constrained by search filters.
  • Inspect missing fields and errors with business figures. Missing values remain null, and verification flags are supplied by Flippa.
  • Read outcomes before interpreting an empty sample. Check run messages and SUMMARY rather than assuming no marketplace listings exist.

Limits and caveats

Only available public listing data is exported. No-match searches and verification filtering can yield an empty dataset, while access or extraction failures can fail the run. Source errors alone do not prove that a listing is private or deleted.

Property, price, revenue, status and sale-method filters depend on Flippa support. Queries use Flippa's keyword search; ordinary category paths do not select a category, and there is no local sorting. Search filters do not constrain a direct listing lookup.

Detail failures retain useful search rows with error notes and fail the run when details were requested. A run can stop at its configured timeout, and already-saved rows remain available if a later step fails. The result cap is not a guaranteed matching count.

Revenue, profit and traffic figures and verification indicators are not independently audited. Missing numeric values stay null. The legacy annualOrganicTraffic field holds a monthly unique-visitor value when present, while authorityScore remains null. Neither is a verified annual-traffic or authority measure, and the Actor does not calculate a business valuation.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~flippa-listings-scraper/runs' \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H 'Content-Type: application/json' \
--data @- <<'JSON'
{
"propertyTypes": [
"website"
],
"priceMax": 50000,
"maxItems": 10,
"includeDetails": true,
"proxyConfiguration": {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "AU"}
}
JSON

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"
],
"priceMax": 50000,
"maxItems": 10,
"includeDetails": true,
"proxyConfiguration": {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "AU"}
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/flippa-listings-scraper').call(run_input={'propertyTypes': ['website'], 'priceMax': 50000, 'maxItems': 10, 'includeDetails': True, 'proxyConfiguration': {'useApifyProxy': True, 'apifyProxyGroups': ['RESIDENTIAL'], 'apifyProxyCountry': 'AU'}})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API and AI-agent use notes

The REST request starts an asynchronous run. Wait for completion, then retrieve items from its defaultDatasetId.

MCP and AI agents

You can ask your AI assistant to collect data with Flippa Listings Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Flippa Listings Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

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

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Flippa Listings Scraper by Fetch Cat, or give it the identifier fetch_cat/flippa-listings-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

  • “Use Fetch Cat’s Flippa Listings Scraper to collect up to 5 website listings with a maximum asking price of 50000 USD. Show listing links, asking prices and available monthly revenue alongside missing-field and error notes.”
  • “Collect at most 5 ecommerce property listings in idSync mode with extra search details off. Keep listing IDs, source links and available fields without assuming an IDs-only schema or keyword filtering.”
  • “Retrieve one public Flippa listing from the direct URL I provide. Show available price, revenue, profit and verification indicators as source-reported claims, not audited values or an independent valuation.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does this access private financial documents or seller contacts?

No. It does not use Flippa credentials, private deal rooms, messages, watchlists or account-only documents.

Does an empty dataset prove there are no listings?

No. No matches and verification filtering can produce an empty result. Access or extraction failures can also fail a run. Inspect the run messages and the SUMMARY key-value record before drawing conclusions. Source errors alone do not prove that a listing is private or deleted.

Does ID sync detect changes or send alerts?

No. It collects another snapshot using the same output schema. Compare datasets by listingId in your own workflow. There is no built-in change detector or alerting service.

Can I get every listing or guarantee keyword matches?

No. Public availability, Flippa filters and the run limit determine coverage. queries uses Flippa's keyword search, which may match fields beyond the title. No completeness, ordering or valuation guarantee is provided.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥