CARTO.js 4.0 introduces new concepts that in some cases, change the behavior of old components. This section clarifies those changes and describe new functionality.
Yes. See the full reference API for details.
If you want to learn more about authorization and authentication, read the fundamentals about this topic, or dig into the Auth API details.
From your CARTO dashboard, click Your API keys from the avatar drop-down menu to view your uniquely generated API key.
The permissions you set up when you create the API key. CARTO platform uses an authentication system that allows you to customize API key permissions in a granular and secure way.
All billing is managed through your CARTO account.
The release of the updated CARTO.js library does not impact your plan in any way. There are no changes in terms of costs or payments of your CARTO use.
cartodb.createVis and viz.json URLs?No, you cannot. While cartodb.createVis and viz.json URLs were convenient and allowed you to prototype a map using CARTO Editor (the former version of Builder) to create a custom app, the functionality of the library has changed.
In CARTO.js 4.0, we are taking a more programmatic, low-level approach and identifying components that are separate from the front-end tool (CARTO Builder). This will make the API easier to use and more intuitive, giving developers greater flexibility in maintaining their core application.
No, you cannot.
Named Maps was a powerful and popular feature yet not easy to understand. Named maps were designed as a workaround for some of the limitations of our API keys. Named maps’ purpose might be replicated by the new authorization system.
This new library allows you to create custom Location Intelligence applications using Builder capabilities.
Highlights of this release include the ability to:
You can learn more about these main features reading the final release announcement.