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.
Brazil CNPJ Monitor — Alerts When a Company Changes returns 6 documented output fields, including from, to, from_count, to_count and status. Every field carries a declared type, a written description and an example value. 4 runs are recorded on Apify.
- 6
- Output fields
- 7
- Inputs
- 4
- Runs
- 2026-10-16
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| from | arraynull | The value before the change. | Alice Smith |
| to | arraynull | The value after the change. | Alice Jones |
| from_count | arraynull | How many entries the value had before. | 2 |
| to_count | arraynull | How many entries the value had after. | 3 |
| status | string | number | boolean | array | objectnull | Outcome recorded for this row. | ok |
| record_type | stringnull | Discriminator for this record kind. | change |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"from": [
"Alice Smith"
],
"to": [
"Alice Jones"
],
"from_count": 2,
"to_count": 3,
"status": "ok",
"record_type": "change"
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| cnpjs | arrayoptional | One CNPJ per line, with or without punctuation. Keep the same list between runs — that is what makes a change a change. Check digits are verified locally first, so a typo is never reported as a missing company. |
| watch | arrayoptional | One entry per watched field: situacao, address, capital, contact, cnae, partners, names, tax. Unknown entries are ignored. Watching 'partners' costs nothing extra — the partner list arrives with the same request. |
| includePartners | booleanoptional | ON by default, and needed for the 'partners' watch. The list comes back with the same request, so this costs nothing extra. |
| maxItems | integeroptional | Hard limit on how many watchlist entries are checked, in the order you gave them. |
| maxChangeRows | integeroptional | Caps the rows written in one run so a first mass change cannot flood your dataset. State is always saved in full, and the SUMMARY says if it truncated. |
| requestsPerMinute | integeroptional | The registers are free and community-run, so this Actor is deliberately gentle: one request a second by default. |
| retries | integeroptional | How many times a rate-limit or server error is retried, with backoff, before the next provider is tried. |
04 — run
Run Brazil CNPJ Monitor on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
6 of 6 fields described
- What does Brazil CNPJ Monitor — Alerts When a Company Changes return?
- It returns 6 documented output fields: from, to, from_count, to_count, status and record_type. Each field declares its type, a description of what it holds, and an example value.
- What input does Brazil CNPJ Monitor — Alerts When a Company Changes take?
- All 7 inputs are optional and ship with usable defaults, so it runs as-is. They are listed with their types below.
- Does Brazil CNPJ Monitor — Alerts When a Company Changes need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run Brazil CNPJ Monitor — Alerts When a Company Changes?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.