> For the complete documentation index, see [llms.txt](https://developers.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.didomi.io/api-and-platform/introduction/quotas.md).
# Quotas
The Didomi platform enforces quotas for some platform features such as compliance reports. Quotas are designed to protect the platform and ensure the availability and performance of our services for all our customers. Each quota is organization-specific and is enforced at the organization level.
## **Platform** quotas
We currently enforce the following quotas:
| ID | Default value | Description |
| ------------------------------ | ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `scraper_enabled_properties` | 250 | Number of properties that can be enabled for a scraping session. |
| `parallel_notices_deployments` | 3 | Maximum number of notices deployments (publishing) that can be run in parallel. |
| `exports_configs` | 3 | Maximum number of enabled batch export configs. |
| `exports_destinations` | 2 | Maximum number of batch export destinations per export config. |
| `consent_proof_reports` | 10 per month | Number of consent proof reports that can be generated by an organization per month. |
| `api_requests` | 100 requests every 15 seconds | Number of API requests authenticated with API keys that can be made by an organization. This does not apply to the Consents API routes on /consents/\*.
More information is provided on this quota in /pages/e3O3DFq3HCq9hHUdgQJg.
|
| `secrets` | 300 | Maximum number of secrets allowed to be created by an organization. |
| `metadata_partners` | 500 | Maximum number of vendors allowed to be created by an organization. |
| `metadata_purposes` | 300 | Maximum number of purposes allowed to be created by an organization. |
## **View your organization quotas**
To view the quotas applied to your organization, send an authenticated HTTP GET request to `https://api.didomi.io/v1/quotas` with your organization ID as a query-string parameter. Example:
```bash
curl -H "Authorization: Bearer " https://api.didomi.io/v1/quotas?organization_id=
```
The response will looks like this:
```javascript
{
"data": [
{
"scraper_enabled_properties": 250,
"parallel_notices_deployments": 3,
"exports_configs": 3,
"exports_destinations": 2,
"consent_proof_reports": 10,
"api_requests": 100,
"id": "...",
"organization_id": "...",
"created_at": "...",
"updated_at": "...",
"version": 0
}
],
"total": 1,
"limit": 100,
"skip": 0
}
```
## **Request a quota increase**
If you want to request an increase of any of the existing quotas, reach out to . We do our best to accommodate increase requests but cannot guarantee that we will fulfill them.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://developers.didomi.io/api-and-platform/introduction/quotas.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.