📘

Attention: breaking changes!:

We are introducing new upper limits to the count of entities that the customers are able to store within the Pipedrive application, for the entities mentioned below.

Why is it changing?

We are introducing these new limits in an effort to ensure the optimal performance and stability of our system. We project that these limits will not impact the overwhelming majority of our customers, as they serve to prevent extreme cases, thus keeping our systems stable.

Summary of the new limits

The summarised list of affected entities and corresponding new limits is as follows:

1. Activity types - new limit of 1,000 per company
2. Custom field options - new limit of 1,000 options per custom field
3. Deal products - new limit of 200 attached products per deal
4. Filters - new limit of 5,000 per company
5. Tasks - new limit of 5,000 per project
6. Related organizations - new limit of 10,000 per contact organization

What is changing?

1. Limit on activity types count

From November 18th, activity types will have a a maximum total count limit of 1,000 activity types per company. In case the limit is reached, adding new activity types will fail with a 403 error code for the following endpoints:

• POST /v1/activityTypes

Editing existing activity types is not affected by this limit.

Here's an example of the 403 error response:

{
  "success": false,
  "error": "Maximum number of activity types per company reached. Maximum limit: 1000",
  "error_info": "Please check developers.pipedrive.com for more information about Pipedrive API",
  "data": null,
  "additional_data: null
}

2. Limit on custom field options count

From November 18th, option- and multi-option custom fields will have a maximum count limit of 1,000 options per one custom field. In case the limit is reached for a custom field, adding new options to this field will fail with a 403 error code. This change affects the following endpoints:

• POST /v1/dealFields
• PUT /v1/dealFields/{id}
• POST /v1/organizationFields
• PUT /v1/organizationFields/{id}
• POST /v1/personFields
• PUT /v1/personFields/{id}
• POST /v1/productFields
• PUT /v1/productFields/{id}

Here's an example of the 403 error response:

{
  "success": false,
  "error": "Maximum number of options per field reached. Maximum limit: 1000",
  "error_info": "Please check developers.pipedrive.com for more information about Pipedrive API",
  "data": null,
  "additional_data: null
}

3. Limit on deal products

From November 18th, products attached to a deal will have a a maximum count limit of 200 products per deal. In case the limit is reached for a deal, adding or linking more products to this deal will fail with a 403 error code. This change affects the following endpoints:

• POST /v1/deals/{id}/products

Here's an example of the 403 error response:

{
  "success": false,
  "error": "Maximum number of products per deal reached. Maximum limit: 200",
  "error_info": "Please check developers.pipedrive.com for more information about Pipedrive API",,
  "data": null,
  "additional_data": null
}

4. Limit on filters count

From November 18th, filters will have a a maximum total count limit of 5,000 filters per company. In case the limit is reached, adding new filters will fail with a 403 error code for the following endpoints:

• POST /v1/filters

Here's an example of the 403 error response:

{
  "success": false,
  "error": "Maximum number of filters per company reached. Maximum limit: 5000",
  "error_info": "Please check developers.pipedrive.com for more information about Pipedrive API",
  "data": null,
  "additional_data": null
}

5. Limit on project tasks count

From November 18th, tasks will have a a maximum count limit of 5,000 tasks per one project. In case the limit is reached for a project, adding or linking more tasks to this project will fail with a 403 error code. This change affects the following endpoints:

• POST /v1/tasks
• PUT /v1/tasks/{id}

Here's an example of the 403 error response:

{
  "success": false,
  "error": "Maximum number of tasks per project reached. Maximum limit: 5000",
  "error_info": "Please check developers.pipedrive.com for more information about Pipedrive API",
  "data": null,
  "additional_data": null
}

6. Limit on related organizations count

From November 18th, contact organizations will have a maximum count limit of 10,000 related organizations per one contact organization. In case the limit is reached for an organization, linking more related contact organizations to this contact organization will fail with a 403 error code. This change affects the following endpoints:

• POST /v1/organizationRelationships
• PUT /v1/organizationRelationships/{id}

Here's an example of the 403 error response:

{
  "success": false,
  "error": "Maximum number of related organizations per contact organization reached. Maximum limit: 10000",
  "error_info": "Please check developers.pipedrive.com for more information about Pipedrive API",
  "data": null,
  "additional_data": null
}

If you have any questions or comments, feel free to let us know in the Developer’s Community.