Firefox Add-ons · Unique Developer Emails

Export unique Firefox Add-ons (AMO) primary developers — public support email, homepage, AMO profile and extension portfolio — one publisher per row, not one row per listing.

No login. No API key. No Mozilla account.

Who is this for?

You are…	Typical goal	Suggested setup
Browser / security SaaS	Publishers already shipping Firefox extensions in your niche	Search privacy or category Privacy & Security, Require email = Yes
DevTools / productivity vendor	Co-marketing and partnership lists	Category Web Development or keyword tabs
Agency selling to extension makers	CRM-ready inbox + site	Developers — Outreach view, CSV
Market research	Who publishes several AMO listings	Raise Max unique developers; sort export by addonCount
Same ICP as Chrome Web Store outreach	Expand beyond CWS	Mirror your CWS keyword here

What you get by default: unique primary author (first author on the listing), public support inbox when listed, homepage, AMO profile, sample listing users/rating — only fields AMO already shows.

Typical fill (public niches, Aug 2026): roughly half to six in ten listings expose a support email before dedupe. With Require public email = Yes (default) you only pay for rows that have an inbox.

Primary author only: co-authors are not exported as separate rows. Two extensions from the same primary developer collapse to one charge.

How to scrape Firefox Add-ons developers

1. Open this Actor in Apify Console.
2. Step 1 — Mode: leave Search (a niche) or switch to Full catalog (unique developers across every Firefox extension category, paid).
3. Step 2 — Search (Search mode only): keep privacy, or paste an AMO listing URL. Optionally pick a category.
4. Leave Max unique developers at 20 for a first run, then raise it.
5. Click Start. Download JSON / CSV / Excel. Use Developers — Outreach for the inbox; Overview for portfolio size.

In Search mode, keyword/URL or category is required. Full catalog is paid Apify plans only.

Ready-made examples (published tasks)

Example	What you get
Find Firefox privacy extension publishers with emails	Unique Privacy & Security developers, public inbox, CRM-ready
Export Firefox productivity add-on vendors for CRM	Tabs / workflow niche, one primary developer per row
Refresh Firefox developer contacts from an add-on URL	Paste a listing URL, get the primary developer row
Firefox AI extension publishers for cold outreach	AI / assistant keyword niche, outreach view

What data can this Firefox Add-ons scraper extract?

Field	Why it matters for ICP
developerEmail, emails	Public support inbox on the listing
developerWebsite, developerDomain	Company site + clean host for CRM match
developerName, developerUsername, developerProfileUrl	Primary author identity on AMO
supportUrl	Another public way in
categories, addonCount, addonNames	Portfolio in this run
sampleAddonName, sampleUsers, sampleRating, listingUrl	Qualify before outreach
sourceQuery, scrapedAt	Run metadata

Not extracted (and not invented): private Mozilla Hub contacts, guessed emails from the marketing site, co-author rows.

How much does it cost to scrape Firefox Add-ons developers?

This Actor uses pay-per-event pricing. Actor start is $0.00005. You only pay per unique primary developer written to the dataset — not per extension listing. Paid Apify plans get a lower price per developer.

Free plan: a run stops at 20 unique developers — enough to test. Search: paid plans can raise Max unique developers up to 2,000. Full catalog (paid only) goes up to 5,000.

	Free	Bronze	Silver	Gold	Platinum	Diamond
Per unique developer	$0.0015	$0.00135	$0.0012	$0.00105	$0.0009	$0.00075
20 developers (Try)	$0.03	$0.03	$0.02	$0.02	$0.02	$0.02
1,000 developers	$1.50	$1.35	$1.20	$1.05	$0.90	$0.75

Totals include the $0.00005 start. Live AMO scrapers on Apify often charge per listing (~$1–$4 / 1k rows). Here two extensions from the same primary developer are one charge.

Set Max unique developers and, on Apify, a max total charge so a run cannot exceed your budget.

Default memory is 512 MB (HTTP only, no browser).

Is it legal to scrape Firefox Add-ons?

This Actor only accesses data that Mozilla makes publicly available on addons.mozilla.org (support email, homepage, author profile the publisher chose to show). As with any data containing personal information, ensure your use complies with GDPR and relevant regulations. Do not scrape personal data unless you have a legitimate reason to do so. Not affiliated with or endorsed by Mozilla.

Input

Field	Required	Notes
Mode	yes	Search (default) or Full catalog (paid)
Keyword or AMO add-on URL	Search	privacy, or a /addon/… URL
Firefox category	Search	Optional. Combine with a keyword or use alone
Max unique developers	no	Default 20. Cap 2,000 (search) / 5,000 (catalog)
Require public email	no	Default yes
Exclude consumer inboxes	no	Default no — set Yes to drop Gmail/Yahoo/Outlook/etc.
Listing type	no	Extensions (default), Themes, or All
Min users (sample listing)	no	Empty → 0 in Search, 100 in Full catalog

API-only: proxyConfiguration, minDelayMs, maxRequestRetries, language, verboseLogs.

Output example

{
  "developerName": "Bitwarden Inc.",
  "developerUsername": "bitwarden",
  "developerId": "12533945",
  "developerProfileUrl": "https://addons.mozilla.org/en-US/firefox/user/12533945/",
  "developerWebsite": "https://bitwarden.com",
  "developerDomain": "bitwarden.com",
  "developerEmail": "hello@bitwarden.com",
  "emails": ["hello@bitwarden.com"],
  "supportUrl": "https://bitwarden.com/help/",
  "categories": ["privacy-security"],
  "addonCount": 1,
  "sampleAddonName": "Bitwarden Password Manager",
  "sampleUsers": 935888,
  "sampleRating": 4.5,
  "listingUrl": "https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/",
  "sourceQuery": "privacy",
  "scrapedAt": "2026-08-17T12:00:00.000Z"
}

Important / limitations

• Primary author only — first author on the AMO listing; co-authors are skipped.
• Email = public support_email on the listing, not a guessed personal inbox.
• Full catalog walks every public Firefox extension category, then keeps unique primary developers. You are charged once per developer even if they publish many add-ons or an add-on sits in several categories.
• Themes are off by default (set Listing type if you need them).

Also available

• Chrome Web Store Unique Emails — unique CWS publishers ($2.50 / 1k).
• Slack Marketplace Unique Developer Emails — unique Slack app publishers ($1 / 1k).

Local development

npm install
apify run --purge --input-file=./input.json

Default .actor/INPUT.json matches Console Try (privacy, 20 unique developers). Root input.json is merged locally; KV / CLI input wins on overlap.

Support

Contact corentin@outreacher.fr if you need a custom scraper or tailored automation.