Brazil E-commerce CNPJ Scraper - Online Seller Contacts
Pricing
$4.00 / 1,000 per brazilian online seller returneds
Brazil E-commerce CNPJ Scraper - Online Seller Contacts
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.
Pricing
$4.00 / 1,000 per brazilian online seller returneds
Rating
0.0
(0)
Developer
Scrapers Delight
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 months ago
Last modified
Categories
Features
Share
🇧🇷 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
- 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 () and its store-state object are read too.Copyright Loja X - 43771721000108 - 2026 - 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).
- 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. - 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.
- 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:
.brdomains 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 % |
| 81.4 % | 85.4 % | 83.2 % | |
| phone or WhatsApp | 86.4 % | 93.8 % | 89.7 % |
| phone | 72.9 % | 93.8 % | 82.2 % |
| 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_ids 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)
{"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.