This content applies to a previous version of CARTO
In October 2021 we released a new version of our platform. You can find the latest documentation at docs.carto.com
Helpful Tools
Tools for working with data.
CARTO teammates have built tools for internal use that are available to users. These are not official platform features and maintenance is not guaranteed, though they can improve workflow efficiency.
Note: These tools require an API key and a CARTO account that includes Engine.
CARTO Batch API UI
Why you need this
- Your query is failing due to a timeout error.
The Batch API UI provides an interface for making Batch queries through the SQL API. These queries handle write operations (INSERT, UPDATE, CREATE TABLE) with long execution times.
Why use Batch queries?
Every CARTO account has a maximum query time limit to maintain stable performance. Complex queries or those processing large datasets can exceed this limit and fail. Batch queries were created to circumvent timeout errors, offering significantly higher time limits by sending requests to a different endpoint.
Example endpoints:
- Standard SQL API:
https://username.carto.com/api/v2/sql - Batch query endpoint:
https://username.carto.com/api/v2/sql/job
How to use it
- Visit https://cartodb.github.io/customer_success/batch/
- Enter your CARTO account name in the Username field
- Enter your master API key
- Enter your query and click Submit
The tool automatically monitors job status changes from pending to running to done without requiring manual checks. Do not refresh the browser after submitting.
CDB Manager
Why you need this
- You need to access data information not exposed in the CARTO dashboard.
CDB Manager lets you apply PostgreSQL queries to your account, access dataset details (indexes, triggers), and view stored procedures.
How to use it
- Visit https://betis.carto.io/
- Click New
- Click Current endpoint and enter a connection name
- Enter your CARTO account username
- Click Update
Access features through sidebar sections. Use Settings to configure row display and dataset visibility.
Tip: Credentials are not stored externally, but local storage is used – avoid shared computers.
