Migrating from CNPJa
Migration from CNPJa is straightforward. The/cnpj/{cnpj} endpoint supports the formato=cnpja parameter, which returns the response in the same format as the CNPJa API.
Step 1: Change the base URL
Step 2: Add authentication
Add thetoken parameter to the URL or the Authorization: Bearer {token} header.
Step 3: Test
The response will have the same format as CNPJa. No changes to parsing are required.Differences
| Aspect | CNPJa | This API |
|---|---|---|
| Authentication | API Key via header | Token via URL or header |
| Rate limit | Per plan | 5 req/min (free) |
| Extra data | Registration + partners | Registration + logos + Simples |
| Native format | Proprietary | Proprietary (with compatibility) |
When to remove the formato parameter
We recommend that, after validating the migration, you remove the formato=cnpja parameter and adapt your code to this API’s native format. The native format offers more fields and better structured data.