Libraries and APIs
The set of tools you will use to develop custom applications with CARTO
Libraries
deck.gl
deck.gl is an open source JavaScript (and TypeScript) based visualization library designed for large-scale geospatial datasets. It's powered by WebGL2 and WebGPU, achieving incredible visual results with high performance. It's part of the vis.gl framework, integrated into the OpenJS Foundation. CARTO is a lead contributor as well as a member of the technical steering committee of deck.gl.
To visualize geospatial data from CARTO in a custom web application, you need to use deck.gl.
npm install deck.gl@deck.gl/carto
Inside deck.gl, we maintain our CARTO module, which provides all the necessary layers and styling functions to create and style deck.gl layers from your CARTO connections.
npm install @deck.gl/carto@carto/api-client
@carto/api-client is a JavaScript (and TypeScript) client library for CARTO APIs and framework-agnostic CARTO + deck.gl web applications.
@carto/agentic-deckgl
@carto/agentic-deckgl is a framework-agnostic TypeScript library for building AI-powered map experiences on top of CARTO and deck.gl. It provides tool definitions, system prompt generation, and SDK converters that allow an LLM to control a deck.gl map through natural language — adding layers, navigating, placing markers, and applying spatial filters.
APIS
SQL API
CARTO SQL API v3 lets you run arbitrary queries in external data warehouses using an existing connection in your CARTO organization.
Tokens API
The CARTO Tokens API allows the creation API Access Tokens that grant access to specific tables, tilesets and arbitrary queries using a specific connection in your CARTO organization.
An API Access Token allows to create map layers and fetch data from tables, tilesets or arbitrary SQL queries in public applications.
Connections API
CARTO Connections API allows for programmatically managing (create, list, delete, or update) your connections to an external Data Warehouse
Imports API
CARTO Imports API allows the creation of geospatial tables in an organization's CARTO Data Warehouse by importing files via URL. Once a file is imported, the resulting table can be previewed in Data Explorer and used in Builder and external applications to create maps.
When using the carto_dw connection in your CARTO organization it will create tables in your organization's data shared folder. Learn more about CARTO Data Warehouse here.
CARTO supports importing CSV, GeoJSON, GeoPackage, KML, KMZ, TAB, Shapefiles (in a .zip package), GeoParquet, FlatGeobuf (.fgb), and File Geodatabase (a .gdb folder zipped as .gdb.zip) files. These formats can be imported into any connected data warehouse.
You can also import an ArcGIS Feature Service or Map Service layer from its URL, for example https://<host>/arcgis/rest/services/<name>/FeatureServer/0. Point at a specific layer (ending in /0, /1…) so CARTO can page through large layers.
GeoTIFF raster files are also supported when importing into BigQuery, Snowflake, and Databricks connections. The resulting table follows the Raquet specification.
The size limit for file imports is 5 GB for all formats.
Besides the CARTO Data Warehouse, imports are supported for BigQuery, Snowflake, Amazon Redshift, PostgreSQL, Databricks and Oracle. Let us know if you need a higher size limit.
Location Data Services (LDS API)
CARTO Location Data Services API provides access to the following services:
Geocoding: Get coordinates from a street address
Batch geocoding: Get coordinates from a list of street addresses
Reverse geocoding: Get a street address from a pair of coordinates
Isolines: Get isoline geometries for different methods of transportation.
Routing: Get routing geometries for different methods of transportation
Maps API
API rate limits
CARTO Cloud is protected with a web application firewall (WAF) that will automatically and temporarily block any IP that exceeds our API rate limits. These limits are applied per IP:
Maps API: 3500 requests/minute
LDS API: 3000 requests/minute
SQL API: 2500 requests/minute
Import API: 500 requests/minute
Tokens & Accounts: 300 requests/minute
Connections, Workflows & Organization Maps: 300 requests/minute
AI (LLM completions): 300 requests/minute
All other endpoints: 1000 requests/minute
The All other endpoints limit covers any API not listed above, including the Activity Data API.
Cached requests (answered by our CDN) do not count towards this rate limit.
CARTO APIs will send a 429 HTTP response if the API request is over this limit.
Last updated
Was this helpful?
