Understanding your organization quotas

Every CARTO subscription plan includes a set of available quotas such as the total number of editor users that the organization can create.

Let’s review these quotas more in depth, with examples to help you predict usage.

Usage quota

Every time any user in your organization interacts with the CARTO Platform through the UI or through our APIs, Usage quota units will be consumed from your annual quota. Technically speaking, this quota is based on requests to the following CARTO APIs: Maps API, SQL API, Import API, and LDS API.

Not all API requests are worth the same. Here's a rundown of what each API does and how it is weighted against the Usage quota.

API	When is it used?	Weight	Example
Maps API	To load layers and tiles in a map. Every time you interact with a map these requests are needed, including opening, styling, editing, exploring, or zooming in a map.	0.1	10 requests to the Maps API will consume 1 Usage quota unit.
SQL API	To push queries to the data warehouse for analytical purposes (that is, not to render a map) Widgets in Builder and all components in Workflows use this API. Creating tilesets or enrichments from the CARTO Workspace will also make use of it.	10	1 request to the SQL API will consume 10 Usage quota units.
Import API	To import geospatial files from your computer (or from a url) to your data warehouse	10	1 imported file will consume 10 Usage quota unit.
LDS API	LDS stands for "Location Data Services" and it is used to geocode addresses and compute isolines based on your data.	0.1	1 LDS API

Only successful requests (2xx) are counted towards the usage quota.

Metadata-related endpoints are excluded from the usage quota calculations, such as retrieving the details of a sql job, map or import job.

Cached requests are included in the usage quota calculations, so viewers will get the best performance regardless of the usage quota.

The Usage quota is annual, and it will reset AFTER your reset date. During the reset date, you'll still see consumption for the ongoing period, and it will only display "0" the following day.

The Usage quota is a soft quota, which means that even if your organization exceeds this quota the platform will continue to work as usual for all users, from editors to live public maps. This avoids unnecessary disruptions, and also allows great flexibility for accidental or unforecasted usage peaks

Lastly, the usage quota is updated every day, so if you do actions now, you should see the changes reflected the following day.

Average monthly usage

Because the Usage quota is annual and it is consumed progressively, we provide a simple estimation on how good you're doing versus your quota at any time. If we estimate that your organization will run out of quota, we will provide an estimated date where your quota will exhaust.

This estimation is based on your current consumption and assumes your organization will keep using the platform at that same rate.

Editor users

An editor is a user that has permissions to create and edit maps, connections, applications… This is a hard quota, and will be enforced whenever you try to add new editors or when new editors try join the organization. For more information on how to manage users, check Managing User Roles.

Users set as “Admin” also count towards the editor quotas.

Example:

If I already have 3 out of 3 editors/admins available, I won’t be able to invite new editors or promote viewers to editors or admins.

Viewer users

A viewer is a user that can only view the objects (maps, applications…) produced in the organization. They can’t create or edit anything in the organization… This is a hard quota, and will be enforced whenever users try to signup or whenever you try to add new viewers through invitations or roles. For more information on how to manage users, check Managing User Roles.

Example

If I already have 50 out of 50 viewers available, I won’t be able to invite viewers or demote editors to viewers. Also, users that try to join or request to join the organization will be blocked.

Tokens

Using the Tokens API you can create permanent tokens that your apps and projects will use to access the CARTO APIs. This quota is the maximum amount of tokens you can have at the organization level. This is a hard quota and will be enforced whenever you try to generate a new token.

Temporary access tokens (for example those generated using an M2M application) don't count towards this quota.

Example

If I already used 100 out of 100 tokens, I won't be able to create new tokens using the Tokens API or any other method. Existing tokens will still work as usual.

Location Data Services (LDS)

Whenever you geocode a table or calculate isolines based on your data, you're using our Location Data Services, abbreviated as LDS. The use of LDS is limited by an annual quota (LDS credits) that you can track here.

LDS credits are consumed for every geocoded row and for every isoline calculated.

The tracker for LDS credits in Workspace updates automatically in near real-time.

Example

If I have already geocoded 50,000 rows and calculated 50,000 isolines, and my LDS credits quota is 100,000, I won't be able to process more geocoding or isolines..

Increasing quotas

• If you need to increase any of these quotas, please contact your Account Manager, Customer Success Manager or send an email to [e-mail]

Legacy quotas

Enterprise organizations created before March 2023 might have a different set of quotas

Since the rollout of the new Usage quota model has been progressive for existing customers, it's possible that your "Usage & Quotas" page looks slightly different than documented above. Here's a collection of older quotas that are now deprecated.

• Total maps

• Public maps

• Total connections

• Total applications

In general, if you see these quotas under your "Usage & Quotas" page, they still apply to your organization. If you have questions, please contact your Account Manager.