# Brazil E-commerce CNPJ Scraper - Online Seller Contacts (`scrapersdelight/br-decreto7962-ecommerce-contact-scraper`) Actor

Brazilian online-shop domains in, one seller per row out: razão social, check-digit-verified CNPJ, inscrição estadual, address, email, phone, WhatsApp and SAC, plus the Receita Federal register status. Billed only for rows with the seller's own CNPJ. $4.00 per 1,000 sellers.

- **URL**: https://apify.com/scrapersdelight/br-decreto7962-ecommerce-contact-scraper.md
- **Developed by:** [Scrapers Delight](https://apify.com/scrapersdelight) (community)
- **Categories:** Lead generation, E-commerce, Business
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 per brazilian online seller returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 🇧🇷 Brazil E-commerce CNPJ Scraper — Online Seller CNPJ, Razão Social & Contacts

Paste a list of Brazilian online-shop domains and get back **one row per seller**, read off the seller
block every Brazilian store prints on its own site — the **razão social**, the **CNPJ verified with both
check digits**, the **inscrição estadual**, the **physical address** (CEP, city, UF), the **email**, the
**phone and WhatsApp** numbers and the **SAC** (customer-service) channel — each with the URL it was
found on, plus the **Receita Federal register's own answer** for that CNPJ: status, registered name,
main CNAE, company size, Simples / MEI.

- **Contact fields first:** on held-out Brazilian shop lists, **95.3 %** of billed rows carry an email,
  phone or WhatsApp — **83.2 %** an email, **89.7 %** a phone or WhatsApp number.
- **The CNPJ is the seller's own:** every emitted CNPJ passes both check digits and was printed on the
  site; CNPJs of the platform, the payment intermediary or the agency that built the shop are recognised
  and never billed as the seller. All **107 of 107** held-out CNPJs were found in the Receita Federal
  register, all **ATIVA**.
- **High coverage:** **83.6 %** of a Brazilian shop list becomes a billed row (**87.0 %** of the
  reachable shops).
- **You pay only for a seller row.** $4.00 per 1,000 sellers. A dead site, a walled site, a site that
  prints no CNPJ, a contact-only site, a platform-only CNPJ and an individual seller's CPF are **never
  charged**.

***

### 🏪 Where the data comes from

Brazilian online shops print their seller identification — nome empresarial, CNPJ, address and contact
details — on the site itself, usually in the footer ("rodapé") and in the Termos de Uso / Política de
Privacidade. The Actor finds that block on each shop and reads it.

***

### 🔍 What it does, per domain

1. **Fetches the homepage** — directly from Apify's network — and reads its **footer**, its visible text,
   its **inline JSON** (on modern storefronts the block often lives only there — e.g. a page-state string
   carrying `"americanas s.a. / CNPJ: 00.776.574/0006-60 / Inscrição Estadual: …"` with none of it in the
   rendered HTML) and its **JSON-LD**. Nuvemshop's copyright line (`Copyright Loja X - 43771721000108 -
   2026`) and its store-state object are read too.
2. **When the homepage lacks part of the block**, ranks the shop's **own** links with Brazilian labels —
   *Termos de Uso, Política de Privacidade* > *Quem Somos, Institucional* > *Trocas e Devoluções* >
   *Fale Conosco, Atendimento* — and merges up to two of those pages field by field (the contact page
   first when the contact channels are what is missing).
3. **Picks the seller's CNPJ** among every check-digit-valid number on the page: a number printed next
   to a platform, payment or agency name (PagSeguro, Mercado Pago, Nuvemshop, ClearSale, "Desenvolvido
   por …") belongs to that company, and so does any other branch of the same root. The rest are returned
   in `otherCnpjs` / `thirdPartyCnpjs`, never merged.
4. **Reads every statutory field next to that CNPJ** — the razão social nearest the number, the
   inscrição estadual, the address from the street word to the CEP, the city checked against the IBGE
   list of 5,571 municipalities for that UF.
5. **Cross-checks the CNPJ with the Receita Federal open data** (BrasilAPI, with minhareceita.org as the
   fallback) and says whether the register's name matches the one the site printed.

A shop that refuses a direct request (403 / challenge / connection reset) is retried on **Apify
RESIDENTIAL exit nodes in Brazil**, with a fresh session per attempt. Dead hosts and 404s are never retried.

***

### 📦 What you get — every field

#### Seller identity

| Field | What it is |
|---|---|
| `companyName` | `registeredName`, else `nameNearCnpj`, else the JSON-LD name. |
| `registeredName` | The **razão social** as the site prints it — "Crestana e Crestana Ltda", "CIRANDA CULTURAL EDITORA E DISTRIBUIDORA LTDA." — from a "Razão social:" label, the legal-form name nearest the CNPJ, the "A {nome}, pessoa jurídica…" opening of a policy text, or the JSON-LD `legalName`. |
| `registeredNameSource` | `label` · `legal-form` · `statement` · `json-ld`. |
| `nameNearCnpj` | The name printed right next to the CNPJ without a legal form — usually the trading name ("18 Store - CNPJ: …", "Copyright Haja Amor - 40217987000115"). |
| `legalForm` | LTDA · S.A. · EIRELI · SLU · MEI · EPP · ME — from the razão social's suffix. |
| `nameCpfWithheld` | An MEI's name printed with the owner's CPF after it: the CPF digits are removed. |

#### Registrations

| Field | What it is |
|---|---|
| `cnpj` · `cnpjFormatted` · `cnpjRaw` | The seller's CNPJ — 14 characters (the alphanumeric CNPJ issued from July 2026 is supported), `12.345.678/0001-90`, and exactly as printed. |
| `cnpjSource` · `cnpjLabelled` | Where it sat (`footer` / `page` / `script` = inline JSON / `jsonld`) and whether a "CNPJ" label (or the copyright line) introduced it. |
| `cnpjIsHeadOffice` · `cnpjRoot` | Order number 0001 = matriz; the 8-digit root shared by every branch. |
| `otherCnpjs` | Other valid CNPJs the shop prints as its own (branches, group companies). |
| `thirdPartyCnpjs` | CNPJs recognised as the platform's / payment intermediary's / agency's, with the owner. |
| `stateRegistration` · `stateRegistrationDigits` · `stateRegistrationExempt` | The **inscrição estadual** as printed ("251.595.757", "ISENTO"). |

#### Physical address

| Field | What it is |
|---|---|
| `addressLine` | From the street word (Rua, Av., Rodovia, Alameda…) to the CEP, as printed. |
| `postcode` | The CEP, `NNNNN-NNN`. |
| `city` · `state` | City (IBGE spelling) and UF — only when the site prints them. |
| `addressSource` | `next-to-cnpj` (the same statement as the CNPJ), `footer`, `page`, or `json-ld`. |

#### Contact

| Field | What it is |
|---|---|
| `email` · `emails` | On-site addresses first; Cloudflare-protected and entity-encoded addresses decoded. Platform, payment and Procon / Reclame Aqui mailboxes are dropped. |
| `phone` · `phones` | E.164 (`+5511…`) for landlines and mobiles (area code checked against the national plan); 0800 / 4004-style numbers as the digits a Brazilian dials. |
| `whatsapp` · `whatsapps` · `whatsappUrl` | Numbers from wa.me / api.whatsapp.com links and "WhatsApp:" labels, plus the first click-to-chat link (including WhatsApp Business short links with no number). |
| `sacPhone` · `sacEmail` · `sacWhatsapp` | The channel printed under a SAC / Central de Atendimento / Atendimento ao Cliente label. |
| `serviceHours` | The service-hours line as printed ("Segunda a Sexta, das 9h às 17h"). |
| `socialLinks` | Instagram, Facebook, TikTok, YouTube, LinkedIn profiles (share buttons and platform help pages filtered out). |
| `termsUrl` · `privacyPolicyUrl` · `exchangePolicyUrl` | The shop's own terms, privacy and trocas-e-devoluções pages. |
| `platform` | The e-commerce platform detected from the homepage bytes: vtex, nuvemshop, tray, loja-integrada, shopify, woocommerce, magento, wake, yampi, bagy, linx, irroba, dooca, wix, prestashop, opencart. |

#### Receita Federal register (with the cross-check on)

`registerStatus` (ATIVA / BAIXADA / INAPTA / SUSPENSA / NULA, or NOT_FOUND / UNAVAILABLE) ·
`registerStatusDate` · `registerSpecialStatus` (e.g. RECUPERACAO JUDICIAL) · `registerName` ·
`registerTradeName` · `registerNameMatchesSite` · `registerOpenedOn` · `registerLegalNature` ·
`registerSize` (MICRO EMPRESA / EMPRESA DE PEQUENO PORTE / DEMAIS) · `registerMainCnae` ·
`registerMainCnaeDescription` · `registerSimples` · `registerMei` · `registerHeadOffice` · `registerCity` ·
`registerState` · `registerPostcode` · `registerPhone` · `registerEmail` · `registerCapital` (BRL) ·
`registerSource`.

#### Provenance & accounting

`domain` · `inputUrl` · `resolvedUrl` · `disclosureUrl` (where the CNPJ was found) · `disclosureSource`
(`homepage` / `homepage-inline-json` / `homepage-json-ld` / `subpage` / `merged`) · `discoveryChannel` ·
`pagesParsed` · `pagesChecked` · `fieldCount` · `fieldSources` (opt-in: the URL of every field) ·
`stableId` (the CNPJ) · `status` · `missReason` · `fetchedAt` · `elapsedMs`.

***

### 👤 Individual sellers

A seller who trades as an individual prints a **CPF** instead of a CNPJ. Such shops are reported as
`status: individual_cpf` and **never billed**; the CPF itself is never returned.

***

### 📊 Measured results — real numbers, not claims

#### The test lists, two opposite-biased frames

- **Frame A — traffic-ranked shops:** `.br` domains from the Tranco top-1M list (rank ≥ 5,000) whose
  homepage carries an e-commerce platform fingerprint and a cart — larger, established stores.
- **Frame B — web-search shops:** small and mid-size stores found by ~40 Portuguese product searches
  ("loja de chás", "semijoias loja virtual", "artigos de pesca loja online" …), big chains excluded.
- A stable hash split held out **72** Frame A and **56** Frame B shops that were never looked at while the
  parser was written. Everything below is one platform run over those 128 held-out domains, shipping
  defaults.

| | A — traffic-ranked | B — web search | all 128 |
|---|---|---|---|
| **billed rows** | **59 — 81.9 %** | **48 — 85.7 %** | **107 — 83.6 %** |
| of reachable shops | 83.1 % | 92.3 % | 87.0 % |
| contact details only, no CNPJ (not billed) | 9 | 2 | 11 |
| no CNPJ, no contact (not billed) | 3 | 0 | 3 |
| individual seller, CPF (not billed) | 0 | 1 | 1 |
| duplicate seller (not billed) | 0 | 1 | 1 |
| host dead / blocked (not billed) | 0 / 1 | 3 / 1 | 3 / 2 |

#### Per-field fill on the billed rows (A / B / all)

| field | A | B | all |
|---|---|---|---|
| **email, phone or WhatsApp** | **93.2 %** | **97.9 %** | **95.3 %** |
| **email** | 81.4 % | 85.4 % | 83.2 % |
| **phone or WhatsApp** | 86.4 % | 93.8 % | 89.7 % |
| phone | 72.9 % | 93.8 % | 82.2 % |
| WhatsApp | 76.3 % | 89.6 % | 82.2 % |
| **CNPJ (both check digits)** | **100 %** | **100 %** | **100 %** |
| a name (razão social or name next to the CNPJ) | 84.7 % | 75.0 % | 80.4 % |
| razão social with legal form / label | 71.2 % | 50.0 % | 61.7 % |
| physical address | 71.2 % | 75.0 % | 72.9 % |
| CEP | 55.9 % | 66.7 % | 60.7 % |
| city + UF | 62.7 % | 68.8 % | 65.4 % |
| SAC email · SAC phone | 62.7 · 10.2 % | 54.2 · 18.8 % | 58.9 · 14.0 % |
| service hours | 30.5 % | 45.8 % | 37.4 % |
| inscrição estadual | 3.4 % | 2.1 % | 2.8 % |
| social profiles | 93.2 % | 95.8 % | 94.4 % |
| register status ATIVA | 100 % | 100 % | 100 % |

Where the CNPJ was found: homepage 50, homepage + a subpage merged 36, a subpage only 15, the homepage's
inline JSON 5, JSON-LD 1. Platforms among the billed rows: Nuvemshop 23, Shopify 17, Tray 15, VTEX 12,
WooCommerce 8, others 20, not detected 12. Register size: MICRO EMPRESA 42, EMPRESA DE PEQUENO PORTE 28,
DEMAIS 37 (46 on the Simples Nacional, 3 MEI).

#### How you can tell it is not a parser gap

An **independently written** detector (any 14-digit run, formatted or not, passing an independently
written check-digit test) was run over every page the Actor read for every **unbilled** held-out shop:
the only check-digit-valid runs it found were 4 Shopify `variant_id`s on one page — none of them in the
Receita register. **0 real CNPJs were left behind.** On the development
lists, 35 unbilled shops were re-crawled far deeper (up to 24 requests each, ten guessed paths, 363
requests in all): **0** more CNPJs. Where a label is printed, the value is emitted: a "CEP" with digits on
108 of 112 development shops, an "Inscrição Estadual" on 11 of 13, a razão-social label on 11 of 11.

#### Output is a subset of the page

Every emitted CNPJ, phone, WhatsApp number, email, CEP and inscrição estadual is asserted present in the
bytes the Actor read — **751 checks over 108 held-out rows, 0 failures**, re-run offline on the pages the
Actor saved during two held-out platform runs (`saveRawPages`). Every single-digit mutation of 18 real
CNPJs (**2,268 mutants**)
was fed back in: a mutant is emitted only when it is itself valid (then it *is* the input); **0 were
repaired** into another number. A newline between two digit groups never welds them into one number;
the textbook example CNPJs (11.222.333/0001-81, 12.345.678/0001-95) and placeholders are refused.

#### Cross-checked against the Receita Federal

All 107 held-out CNPJs were found in the register, all **ATIVA**. Where both names were present, the
register name matched the name the site printed on **74 of 85** rows; the other 11 are brand-vs-legal-name
pairs ("Luz da Lua" / STAMPA ARTEFATOS DE COURO LTDA), three MEI records (the register names an MEI by its
CNPJ root and owner) and one misspelling on the site — the site's name and the register's name are both
returned, side by side, so you decide.

#### A real row (held-out Frame A, abridged)

```json
{
  "domain": "crestana.com.br",
  "disclosureUrl": "https://www.crestana.com.br/contato",
  "platform": "tray",
  "companyName": "Crestana e Crestana Ltda",
  "registeredName": "Crestana e Crestana Ltda",
  "legalForm": "Sociedade Limitada (LTDA)",
  "cnpj": "61355186000196",
  "cnpjFormatted": "61.355.186/0001-96",
  "cnpjIsHeadOffice": true,
  "addressLine": "Rua Piratininga, 593 - Brás, São Paulo - SP, CEP: 03042-001",
  "postcode": "03042-001",
  "city": "São Paulo",
  "state": "SP",
  "email": "sac@crestana.com.br",
  "phone": "+551132073288",
  "phones": ["+551132073288", "+551132723288", "+5511976367039"],
  "whatsapp": "+5511976367039",
  "whatsappUrl": "https://api.whatsapp.com/send?phone=5511976367039",
  "sacPhone": "+551132723288",
  "sacEmail": "sac@crestana.com.br",
  "serviceHours": "De Segunda-feira à Sexta-feira, das 08:00 às 16:30",
  "socialLinks": ["https://www.facebook.com/crestanaltda/?locale=pt_BR", "https://www.instagram.com/crestanaecrestana/", "https://www.tiktok.com/@crestanaecrestana"],
  "registerStatus": "ATIVA",
  "registerName": "CRESTANA & CRESTANA LTDA",
  "registerTradeName": "CRESTANA AUTO PECAS",
  "registerNameMatchesSite": true,
  "registerMainCnae": "4530701",
  "registerMainCnaeDescription": "Comércio por atacado de peças e acessórios novos para veículos automotores",
  "registerSize": "DEMAIS",
  "registerOpenedOn": "1964-09-15",
  "status": "ok"
}
```

#### Transport

Direct from Apify's network, with a residential retry only on a refusal: over the 128 held-out domains,
**354 direct requests and 29 residential**, of which 15 recovered a page the direct request could not get.

***

### 🧰 Every input

| Input | Default | What it does |
|---|---|---|
| `domains` | demo batch | Domains, homepage URLs or direct page URLs. Any TLD, any platform. |
| `startUrls` | — | The same list as URLs (Make / Zapier / Clay / Sheets). |
| `sourceDatasetId` + `domainFieldName` | — | Enrich a previous Actor's dataset (a Google Maps, marketplace-seller or directory run). |
| `domainsFileUrl` | — | A CSV / TXT / JSON / JSONL list at a URL. |
| `skipDomains` · `previousDatasetId` | — | Suppression: never re-deliver or re-charge a seller you already have. |
| `maxItems` | 1000 | Hard cap on billed rows. |
| `maxDomains` | 0 (all) | Cap on domains attempted. |
| `verifyWithRegister` | on | Receita Federal cross-check (status, registered name, CNAE, size, Simples / MEI). |
| `requireActiveCnpj` | off | Deliver and bill only register-ATIVA sellers. |
| `requireContact` · `requireAddress` · `requireStateRegistration` · `platformFilter` · `minFieldsRequired` | off | Quality filters — a filtered row is never billed. |
| `emailPolicy` | all | all · role-only (contato@, sac@) · exclude-role. |
| `dedupeBy` | CNPJ | CNPJ · CNPJ root (matriz and filiais as one) · domain · none. Duplicates are collapsed before anything is charged. |
| `maxPagesParsed` · `maxDiscoveryRequestsPerDomain` | 2 · 6 | Subpages merged per shop; requests per shop after the homepage. |
| `discoveryChannels` | ranked links, sitemap, WordPress index | `pathGuess` (/quem-somos, /institucional, /termos, /politica-de-privacidade and the platforms' own URL shapes) is opt-in. |
| `perDomainTimeoutSecs` · `requestTimeoutSecs` · `maxRequestRetries` | 60 · 25 · 2 | Budgets; every request and every shop also has a hard deadline. |
| `requestConcurrency` | 10 | Parallel shops (lowered automatically to what the memory can hold). |
| `followWwwAndRootVariants` · `respectRobotsTxt` | on · off | Host variants; robots.txt. |
| `proxyConfiguration` | direct | Your own proxy for the FIRST attempt, if you want one. |
| `proxyCountry` · `escalateToResidentialOnBlock` · `escalateToUnblockerOnBlock` | BR · on · off | The retry ladder on a refusal. |
| `customUserAgent` · `extraHttpHeaders` | — | Request identity. |
| `tldFilterMode` · `tldFilter` | none | Include / exclude TLDs. |
| `extractSocials` · `extractPolicyUrls` · `includeMissRows` · `includeFieldSources` · `saveRawPages` | on · on · off · off · off | Output shape and audit trail (`saveRawPages` stores every page read, gzipped, in the run's key-value store). |

A run's `RUN_SUMMARY` record (key-value store) keeps the kinds of nothing apart: dead host, blocked,
no seller CNPJ, contact details only, only a third party's CNPJ, individual seller (CPF), filtered out,
duplicate, suppressed — none of them charged.

***

### 💰 Pricing

**$4.00 per 1,000 sellers** — one `disclosure-scraped` event ($0.004) per billed row, no start fee.
Delivery and billing are atomic, so a spending cap can never leave you with an unpaid row or charge you
for one you did not get. The register cross-check is included.

**Never charged:** a dead host · a host that refused every rung · a site with no seller CNPJ · a
contact-only site · a site whose only CNPJ is the platform's or the payment intermediary's · an
individual seller's CPF · a duplicate · a row your own filters removed · any coverage row.

***

### ❓ FAQ

**Does it find the shops for me?** No — it turns a list of domains into seller records. Feed it a
Google Maps, marketplace-seller or directory export via `sourceDatasetId`.

**Which platforms work?** Any server-rendered storefront. Measured on the held-out lists: Nuvemshop,
Shopify, Tray, VTEX, WooCommerce, Magento, Linx, Loja Integrada, Wake, Yampi, Bagy, Irroba, OpenCart and
PrestaShop shops all delivered rows. Default Nuvemshop subdomains (`loja.lojavirtualnuvem.com.br`) are
treated as their own store, never collapsed into one.

**The site printed one name and the register another — which is right?** Both are returned.
`registeredName` / `nameNearCnpj` is what the site printed; `registerName` / `registerTradeName` is the
Receita's record; `registerNameMatchesSite` compares them (abbreviations such as "Com. Imp. Dist." count
as a match).

**Why is the inscrição estadual empty on most rows?** Because most shops do not print it (2.8 % of
held-out rows). Where it is printed it is read — 11 of 13 labelled development shops.

**Big retailers?** Some national chains sit behind Akamai / Cloudflare challenges (magazineluiza.com.br
answers a 2.5 KB Akamai challenge); they are reported as `blocked` and never charged. Try your own proxy
or the Unblocker toggle. The Actor is built for the long tail of SME stores, where 87 % of reachable
shops delivered a row.

**Why no browser?** A shop whose page is assembled entirely by JavaScript with no server HTML (an Angular
shell, for example) is reported as `no_disclosure`. The inline JSON of Next.js / VTEX / Nuvemshop
storefronts is read without one.

***

### ⚠️ Data limits

- **Coverage is 81.9–85.7 % of a shop list** (83.1–92.3 % of reachable shops); the rest print no seller
  CNPJ in their HTML, print only contact details, or identify the seller by CPF.
- **The inscrição estadual is rarely printed** (2.8 %); the SAC phone is labelled on 14.0 % of rows.
- **A razão social with its legal form is printed on 61.7 % of rows**; with the name printed next to the
  CNPJ, 80.4 % carry a name — and the register cross-check adds the registered name on every row.
- **City and UF are returned only when printed** (65.4 %); the CEP alone is never used to guess them.
- **2 of 128 held-out shops refused even the residential retry**, and 3 hosts were dead.
- **The register lookup** answered all 107 held-out CNPJs; when both services are down a row still
  delivers, with `registerStatus: UNAVAILABLE`.

# Actor input Schema

## `domains` (type: `array`):

One entry per shop. Accepts a bare domain ("attracione.com.br"), a homepage URL ("https://www.anjuss.com.br") or a direct page URL ("https://loja.com.br/politica-de-privacidade"). Any platform (VTEX, Nuvemshop, Tray, Loja Integrada, Shopify, WooCommerce, Wake, Magento...) and any TLD. The Actor reads the seller block each shop prints (razão social, CNPJ, inscrição estadual, address, contacts) into one row per seller. Leave empty to run the built-in demo batch.

## `startUrls` (type: `array`):

The same shop list handed over as URLs, so Make, Zapier, Clay or a Google Sheet can pass it natively (a link to a text/CSV file of URLs also works). Merged with the domain list.

## `sourceDatasetId` (type: `string`):

Dataset ID of a previous Actor run (a Google Maps, marketplace-seller or directory scraper). Each item's domain / website / site / url column is read and enriched.

## `domainFieldName` (type: `string`):

Which field of the source dataset (or which CSV column of the list file) holds the domain. Leave empty to auto-detect domain / website / site / url / dominio / loja. Dotted paths like "company.website" work.

## `domainsFileUrl` (type: `string`):

URL of a CSV, TXT, JSON or JSONL file holding the domains — for lists too big to paste into the editor. The column is picked with "Domain field / CSV column".

## `skipDomains` (type: `array`):

Domains to skip outright — customers you already have, competitors, do-not-contact entries. Matched on the registrable domain, so "www.x.com.br/pagina" and "x.com.br" are the same entry. Never charged.

## `previousDatasetId` (type: `string`):

Dataset ID of an earlier run of this Actor. Every domain and CNPJ it delivered is skipped, so a monthly refresh never re-buys a seller you already paid for.

## `maxItems` (type: `integer`):

Hard cap on rows DELIVERED AND BILLED this run. Distinct from "Max domains": not every shop prints a CNPJ, so a list yields a fraction of its domains as billed rows. 0 = no cap.

## `maxDomains` (type: `integer`):

Cap on the number of domains attempted (after dedupe and suppression). 0 = all.

## `verifyWithRegister` (type: `boolean`):

For every billed row, look the CNPJ the site printed up in the Receita Federal's open CNPJ data (BrasilAPI, with minhareceita.org as fallback) and add the register's own answer: registerStatus (ATIVA / BAIXADA / INAPTA / SUSPENSA / NULA), registerName, registerTradeName, main CNAE, size, Simples / MEI, city/UF, and registerNameMatchesSite. It never changes what the site printed and never changes what is billed (unless you turn on "Only active CNPJs").

## `requireActiveCnpj` (type: `boolean`):

Deliver and bill only rows whose CNPJ the register reports as ATIVA. A BAIXADA / INAPTA / SUSPENSA seller, or a row the register could not answer for, is filtered out and never charged. Needs the register cross-check on.

## `requireContact` (type: `boolean`):

Deliver and bill only rows that carry at least one email, phone or WhatsApp number.

## `requireAddress` (type: `boolean`):

Deliver and bill only rows where the shop printed a physical address.

## `requireStateRegistration` (type: `boolean`):

Deliver and bill only rows where the shop printed its inscrição estadual (or ISENTO).

## `platformFilter` (type: `array`):

Keep only shops detected on these platforms (detected from each homepage's own bytes). Empty = every platform.

## `minFieldsRequired` (type: `integer`):

Deliver and bill only rows with at least this many of: CNPJ, razão social, name near the CNPJ, inscrição estadual, address, CEP, city, UF, email, phone, WhatsApp, SAC phone, SAC email, service hours. 0 = off.

## `emailPolicy` (type: `string`):

"Role only" keeps just generic mailboxes (contato@, sac@, atendimento@...); "Exclude role" keeps only named mailboxes.

## `dedupeBy` (type: `string`):

Which key collapses duplicates BEFORE anything is pushed or charged. Two domains of the same seller (same CNPJ) collapse into one billed row.

## `maxPagesParsed` (type: `integer`):

How many of the shop's own pages (Termos de Uso, Política de Privacidade, Quem Somos, Fale Conosco...) may be read after the homepage when the homepage alone does not carry the full block. Stops early once CNPJ, name, address and a contact are all found.

## `maxDiscoveryRequestsPerDomain` (type: `integer`):

Budget of requests per shop after the homepage, including sitemap and page-index lookups.

## `discoveryChannels` (type: `array`):

How subpages are found. anchor = the shop's own links ranked by Brazilian labels; sitemap and wpJson run only when the footer offered no candidate link; pathGuess (off by default) tries /quem-somos, /institucional, /termos, /politica-de-privacidade and the platforms' own URL shapes. The homepage is always read.

## `perDomainTimeoutSecs` (type: `integer`):

Hard deadline per shop. A shop that does not finish is reported as unreachable and never charged.

## `requestTimeoutSecs` (type: `integer`):

Timeout for one HTTP request (a hard deadline is also enforced around it).

## `maxRequestRetries` (type: `integer`):

Retries on a transient failure or a refusal (each retry on a fresh residential session when escalation is on). Dead hosts and 404s are never retried.

## `requestConcurrency` (type: `integer`):

Shops processed in parallel. Lowered automatically to what the run's memory can hold.

## `followWwwAndRootVariants` (type: `boolean`):

When a homepage fails, try the other host variant once.

## `respectRobotsTxt` (type: `boolean`):

Skip pages robots.txt disallows for this user agent.

## `proxyConfiguration` (type: `object`):

Leave as is for the measured default: DIRECT requests first, then Apify RESIDENTIAL (Brazil) only for a shop that refuses us. Supply your own proxy URLs or an Apify proxy group to route the FIRST attempt through them instead.

## `proxyCountry` (type: `string`):

ISO country code for the RESIDENTIAL retry. BR by default. Only used when a shop refuses the direct request.

## `escalateToResidentialOnBlock` (type: `boolean`):

Retry a shop that answers 403 / 429 / a challenge page through Apify RESIDENTIAL proxy (fresh session per attempt).

## `escalateToUnblockerOnBlock` (type: `boolean`):

Last-resort rung for shops that refuse even the residential retry. Slower and uses more proxy traffic.

## `customUserAgent` (type: `string`):

Override the default desktop Chrome user agent.

## `extraHttpHeaders` (type: `object`):

Extra request headers as a JSON object.

## `tldFilterMode` (type: `string`):

No TLD filter by default — Brazilian shops trade on .com as well as .com.br. Use include / exclude with the list below.

## `tldFilter` (type: `array`):

TLDs for the filter above, e.g. "com.br", "br", "com".

## `extractSocials` (type: `boolean`):

Return the shop's Instagram / Facebook / TikTok / YouTube / LinkedIn profile links.

## `extractPolicyUrls` (type: `boolean`):

Return the shop's own terms, privacy and exchange/return policy URLs.

## `includeMissRows` (type: `boolean`):

Emit a row for every domain that produced no seller row — dead, blocked, no CNPJ printed, contact details only, only a platform/payment company's CNPJ, an individual seller with a CPF, filtered out, a duplicate, or suppressed — with its status and missReason. These rows are never billed.

## `includeFieldSources` (type: `boolean`):

Add fieldSources: the exact URL every field was read from.

## `saveRawPages` (type: `boolean`):

Store every page the parser read, gzipped, in the run's key-value store (<domain>\_\_<n>), so any row can be re-checked against the exact bytes it came from.

## Actor input object example

```json
{
  "domains": [
    "18store.com.br",
    "cicampo.com.br",
    "cirandacultural.com.br",
    "anjuss.com.br",
    "casatema.com.br"
  ],
  "maxItems": 1000,
  "maxDomains": 0,
  "verifyWithRegister": true,
  "requireActiveCnpj": false,
  "requireContact": false,
  "requireAddress": false,
  "requireStateRegistration": false,
  "minFieldsRequired": 0,
  "emailPolicy": "all",
  "dedupeBy": "cnpj-then-domain",
  "maxPagesParsed": 2,
  "maxDiscoveryRequestsPerDomain": 6,
  "discoveryChannels": [
    "anchor",
    "sitemap",
    "wpJson"
  ],
  "perDomainTimeoutSecs": 60,
  "requestTimeoutSecs": 25,
  "maxRequestRetries": 2,
  "requestConcurrency": 10,
  "followWwwAndRootVariants": true,
  "respectRobotsTxt": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "proxyCountry": "BR",
  "escalateToResidentialOnBlock": true,
  "escalateToUnblockerOnBlock": false,
  "tldFilterMode": "none",
  "extractSocials": true,
  "extractPolicyUrls": true,
  "includeMissRows": false,
  "includeFieldSources": false,
  "saveRawPages": false
}
```

# Actor output Schema

## `records` (type: `string`):

One item per shop that printed its seller CNPJ: razão social, CNPJ (both check digits verified), inscrição estadual, physical address, email, phone, WhatsApp, SAC channel, and the Receita Federal register's own answer for that CNPJ.

## `runSummary` (type: `string`):

Coverage accounting: domains attempted, rows billed, and the kinds of nothing (dead, blocked, no seller CNPJ, contact details only, only a platform/payment company's CNPJ, an individual seller with a CPF) kept apart - none of them charged.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "18store.com.br",
        "cicampo.com.br",
        "cirandacultural.com.br",
        "anjuss.com.br",
        "casatema.com.br"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapersdelight/br-decreto7962-ecommerce-contact-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "domains": [
        "18store.com.br",
        "cicampo.com.br",
        "cirandacultural.com.br",
        "anjuss.com.br",
        "casatema.com.br",
    ],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("scrapersdelight/br-decreto7962-ecommerce-contact-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "18store.com.br",
    "cicampo.com.br",
    "cirandacultural.com.br",
    "anjuss.com.br",
    "casatema.com.br"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call scrapersdelight/br-decreto7962-ecommerce-contact-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapersdelight/br-decreto7962-ecommerce-contact-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/4rqfMnqa6K6OumhFM/builds/bJdRQh0rGfNPjRpuD/openapi.json
