Brazil CNPJ Monitor — Alerts When a Company Changes
Pricing
from $2.00 / 1,000 results
Brazil CNPJ Monitor — Alerts When a Company Changes
Watch a list of Brazilian CNPJs and get back only what changed since the last run: status, address, capital social, contacts, CNAE, names, tax elections and the partner list. No API key needed. The first run sets a baseline; a field it could not check is named, never passed off as unchanged.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
alaudin burki
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 hours ago
Last modified
Categories
Share
Give it a list of CNPJs and a schedule. Get back only what changed since the last run — registration status, address, capital social, contacts, CNAE, names, tax elections, and the partner list.
No API key. The lookup is served by free, keyless mirrors of Receita Federal's open data, so a scheduled run simply works.
The two things that make a monitor usable
1. A change is a change. Partner lists are compared as sorted sets, so a register that returns the same sócios in a different order is not reported as movement. A monitor that reports order-shuffles gets ignored.
2. "No change" is never "we could not look." If a watched field could not be checked, the run SUMMARY names it:
Some watched fields were not checked this run (company:2 fetch failure(s)), so no change there means "not looked at", not "unchanged".
That distinction is the whole product. A field silently not monitored is worse than honest downtime.
What you get
status | Meaning |
|---|---|
baseline | First run for this CNPJ. Its current state is recorded; nothing is claimed to have changed. |
changed | One row per changed field: field, from_value, to_value, and from_count/to_count for lists. |
removed_from_watchlist | The CNPJ left your list — reported once, so the drop is deliberate. |
invalid | Rejected locally. The CNPJ failed its check digits; nothing was sent to any provider. |
not_found / error | The register does not have it, or a provider failed. Never silently absent. |
What it watches
situacao · address · capital · contact · cnae · partners · names · tax
Watching partners costs nothing extra — the partner list arrives with the same request.
Two providers, and it never burns the fallback
The lookup is served by community mirrors, not the government endpoint. That is a real dependency, so it is handled:
- Falls back across
brasilapiandminhareceita— one rate-limited or down, the other answers. - A 404 is an answer, not an outage, so the fallback is not spent on a definitive result.
- Validate locally first. CNPJ check digits are verified in code, so a typo never costs a request and is never reported as a missing company.
State
The watchlist baseline lives in the run's key-value store and is written before the output is decided, so a capped output never loses it. maxChangeRows caps one run's rows and the SUMMARY says when it truncated.
Scheduling it
Run it on a schedule — daily for most watchlists. The same list plus a schedule is the whole product.
What it deliberately does not do
- It does not unmask CPFs. The register publishes them masked; so does this.
- It does not notify you directly. It writes rows; wire the dataset to Slack or e-mail with your own notifier.
- It does not watch CNPJs you did not list.
What makes this different
Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.
- Brazil CNPJ Monitor — Alerts When a Company Changes declares all 6 of its output fields in its dataset schema, each with a type, a written description and an example value.
- The output fields of Brazil CNPJ Monitor include from, to, from_count, to_count, status and record_type.
- Brazil CNPJ Monitor needs no API key, login or account of any kind before its first run.
- Every one of Brazil CNPJ Monitor's 7 inputs is optional, so it runs with no configuration at all.
- Every number published about Brazil CNPJ Monitor is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
- Brazil CNPJ Monitor is filed under business and developer tools so that it is found by the people looking for that job, not by its internal name.
Limitations
- Brazil CNPJ Monitor reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
- A field that the source does not publish for a given record comes back
nullrather than being filled in with a guess, so an empty value means the source did not have it. - Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
- This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.
FAQ
What does Brazil CNPJ Monitor return?
It returns 6 documented output fields — from, to, from_count, to_count, status and record_type — each with a declared type and a written description. The full schema is below.
What does Brazil CNPJ Monitor require to run?
Nothing. All 7 inputs are optional and ship with working defaults.
Does Brazil CNPJ Monitor need an API key?
No. It reads only public data and asks for no account.
How is Brazil CNPJ Monitor billed?
Per result returned, on Apify. A run that returns nothing costs nothing. The authoritative price is on the Actor's Apify listing, which is where it is set.
