Next API
CNPJ, CNAE, ZIP code, and geolocation API — with real-time lookups straight from Brazil's Federal Revenue Service
Connect your system, CRM, or ERP to a business database straight from Brazil's Federal Revenue Service. CNPJ, CNAE, ZIP code, geolocation — all via REST API. You choose per call: the synced database, which responds in milliseconds, or the real-time lookup, which hits the Federal Revenue Service at request time and returns the data exactly as it stands right now.
- Real-time lookups, straight from the Federal Revenue Service
- Synced database with millisecond response times
- REST API with full documentation
- CNPJ, CNAE, ZIP code, and geolocation lookups
- Integrate in minutes, not weeks
The problem it solves
Every team that works with Brazilian companies has built the same workaround: someone opens the Federal Revenue's website, types in a CNPJ, solves a captcha, copies the fields, and pastes them into a spreadsheet. As volume grows, that turns into a full-time intern or a scraper that breaks every week.
The Next API removes that step entirely. A GET request with the CNPJ returns the full record as JSON, with a stable contract and no captcha in the way. What used to be manual work becomes a single call inside your sign-up flow, credit analysis, or data enrichment pipeline.
Where it typically fits in
In the sign-up form, auto-filling legal name and address from the CNPJ entered — fewer fields, fewer typos, less abandonment. In the credit pipeline, confirming registration status and company size before approving a limit. In the CRM, enriching leads with CNAE and share capital to prioritize the pipeline.
It also fits into compliance and KYC workflows, where you need an auditable record of a company's status at the moment it was onboarded.
Two modes, chosen per call
Not every lookup has the same requirements. Enriching ten thousand CRM records calls for speed and can tolerate data that's a few weeks old. Approving a six-figure credit line cannot: there you need to know if the company is active right now.
The synced database responds in milliseconds from our own infrastructure and follows the Federal Revenue's publication cycle. It's the right mode for volume: form auto-fill, batch enrichment, prospecting, market analysis.
The real-time lookup hits the Federal Revenue Service at request time and returns the current state of the registry — no delay, no cache, no wondering how many days old the data is. It's the right mode when a mistake is costly: credit approval, supplier onboarding, compliance checks, contract signing.
The choice is per call, not per plan. The same system can use the synced database for sign-up and real-time lookups for the approval pipeline, with the same key and the same response format.
What integration looks like
It's a standard REST API: key-based authentication, JSON responses, standard HTTP status codes, and documentation with ready-to-use examples. There's no mandatory SDK — it works with whatever HTTP client your stack already uses.
Most integrations are up and running the same afternoon. Full documentation, with every endpoint and response format, is on the Next API website.
Features
Form-ready latency
An indexed database served from our own infrastructure, fast enough to run inside a sign-up field.
Full documentation
Every endpoint documented, with request and response examples for each one.
Real-time lookups
The request hits the Federal Revenue Service at that same instant and returns the registry as it stands now. No cache, no delay.
Synced database
For volume, our own database responds in milliseconds and follows the Federal Revenue's publication cycle.
More than just CNPJ
Beyond the company record, the API also resolves CNAE, ZIP code, and geolocation with the same standards.
Frequently asked questions
Does the Next API query the Federal Revenue Service in real time?
Yes. Besides the synced database, which responds in milliseconds, the Next API offers real-time lookups: the request hits the Federal Revenue Service at the moment of the call and returns the registry exactly as it stands then, with no cache and no delay. You choose the mode per call, with the same key and response format.
When should I use each mode?
Use the synced database for volume and speed — form auto-fill, batch enrichment, prospecting, market analysis. Use real-time lookups when a mistake is costly and the data needs to be current: credit approval, supplier onboarding, compliance checks, and contract signing.
What data does the Next API return?
A full CNPJ record (legal name, trade name, registration status, size, legal nature, share capital, and ownership structure), primary and secondary CNAE codes, address with ZIP code and geolocation.
How long does integration take?
It's a REST API with key-based authentication and JSON responses. Most integrations are ready within a few hours, using whatever HTTP client your stack already has.
Is the Next API the same as Consulta CNPJ Fácil?
The data is the same. The difference is the use case: Consulta CNPJ Fácil is the web interface for free, one-off lookups; the Next API is programmatic access for anyone who needs high-volume lookups inside their own system.
Is there a request limit?
Limits vary by plan. Details and technical documentation are on the Next API website.
Ready to get started?
Try Next API now or talk to our team to figure out which setup makes sense for your operation.