dataservices-api/doc/quota_information.md

# Quota Information

**Based on your account plan, some of the Data Services API functions are subject to quota limitations and extra fees may apply.** View our [terms and conditions](https://carto.com/terms/), or [contact us](mailto:sales@carto.com) for details about which functions require service credits to your account.

## Quota Consumption

Quota consumption is calculated based on the number of request made for each function. Be mindful of the following usage recommendations when using the Data Services API functions:

* One credit per function call will be consumed. The results are not cached. If the query is applied to a _N_ rows dataset, then _N_ credits are consumed
* Avoid running dynamic queries to these functions in your maps. This can result in credit consumption per map view. 

  **Note:** Queries to the Data Services API, and any of its functions in your maps, may be forbidden in the future

* It is advised to store results of these queries into your datasets, and refresh them as needed. This ensure more control of quota credits for your account
reorg of docs format and editing, removed mentions of providers 2016-04-13 05:19:51 +08:00			`# Quota Information`
add section for quota info + recommendations 2016-02-19 17:35:04 +08:00
applied docs 781 to dataservices-api doc 2016-05-26 23:00:13 +08:00			`Based on your account plan, some of the Data Services API functions are subject to quota limitations and extra fees may apply. View our [terms and conditions](https://carto.com/terms/), or [contact us](mailto:sales@carto.com) for details about which functions require service credits to your account.`
add section for quota info + recommendations 2016-02-19 17:35:04 +08:00
reorg of docs format and editing, removed mentions of providers 2016-04-13 05:19:51 +08:00			`## Quota Consumption`
add section for quota info + recommendations 2016-02-19 17:35:04 +08:00
reorg of docs format and editing, removed mentions of providers 2016-04-13 05:19:51 +08:00			`Quota consumption is calculated based on the number of request made for each function. Be mindful of the following usage recommendations when using the Data Services API functions:`
add section for quota info + recommendations 2016-02-19 17:35:04 +08:00
reorg of docs format and editing, removed mentions of providers 2016-04-13 05:19:51 +08:00			`* One credit per function call will be consumed. The results are not cached. If the query is applied to a _N_ rows dataset, then _N_ credits are consumed`
added best practices as an H3 under the Overview, data services api integration section 2016-04-27 00:31:08 +08:00			`* Avoid running dynamic queries to these functions in your maps. This can result in credit consumption per map view.`

			`Note: Queries to the Data Services API, and any of its functions in your maps, may be forbidden in the future`

reorg of docs format and editing, removed mentions of providers 2016-04-13 05:19:51 +08:00			`* It is advised to store results of these queries into your datasets, and refresh them as needed. This ensure more control of quota credits for your account`