[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">December 19, 2024</span>\n    </div>\n    <div class=\"change-area\">\n        <p>We are happy to announce new v2 endpoints for Activities API to offer a fast and performant way for interacting with the Pipedrive API. See our <a href=\"https://developers.pipedrive.com/docs/api/v1/Activities\">API Reference</a> for more information.</p>\n        <h3><b>What is the benefit of the new endpoints?</b></h3>\n        <p>We are introducing API v2 to eventually replace v1 endpoints. API v2 is more performant and offers better developer experience. See more information here:</p>\n        <ul>\n            <li><a href=\"https://pipedrive.readme.io/docs/pipedrive-api-v2\" target=\"blank\">Pipedrive API v2 overview</a></li>\n            <li><a href=\"https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide#activities-api\" target=\"blank\">Pipedrive API v2 migration guide</a></li>\n        </ul>\n        <h3><b>Timeline of the launch</b></h3>\n        <p>We’re releasing the public BETA on December 19th, and the API will be available for usage and testing on all accounts. We’ll notify you here in the changelog once the full version of the API is released, so remember to subscribe. Keep in mind that between the BETA and the full release of the API, the endpoints are subject to changes.</p>\n        <p>We are eager to hear your feedback, questions or comments in the <a href=\"https://devcommunity.pipedrive.com/\">Developers’ Community.</a></p>\n    </div>\n</div>"
}
[/block]

Introducing new Activities API v2 endpoints in public BETA

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">March 17th, 2025</span>\n    </div>\n    <div class=\"change-area\">      \n      <h2>What is changing?</h2>\n      <p>From <b>March 17, 2025</b>, all new webhooks created via API will be <b>version 2.0</b> by default. Legacy v1 webhooks can still be created by specifying the <code>version</code> parameter in the API request body until further notice.</p>\n      \n      <h2>Why it is changing?</h2>\n\t\t\t<p>We introduced webhooks v2 at the beginning of 2023 to bring <b>added reliability and stability</b> by <b>reducing duplicate and missing webhook triggers</b> and <b>delays</b>. In addition, <code>lead</code> webhooks are supported in v2. Webhooks v2 have proven their maturity and it is time to start sunsetting v1.</p>\n      \n      <h2>Things to know about webhooks v2</h2>\n      <ol>\n        <li>Webhooks v2 and v1 will continue to run in parallel for the time being but <b>v1 will be deprecated completely by the end of 2025</b>. You will be notified of any changes via our <a href=\"https://developers.pipedrive.com/changelog\">Changelog</a>, so make sure you subscribe to it.</li>\n        <li>Please review the <a href=\"https://pipedrive.readme.io/docs/webhooks-v2-migration-guide\">v1 to v2 migration guide</a> closely as there are significant differences in webhooks v2’s payload.</li>\n        <li>Should a field no longer be available in the payload of a v2 webhook, please query it from our API.</li>\n      </ol>\n\n      <br />\n      <p>Learn about webhooks v2 <a href=\"https://pipedrive.readme.io/docs/guide-for-webhooks-v2\">here</a> and how to migrate your webhooks from v1 to v2 <a href=\"https://pipedrive.readme.io/docs/webhooks-v2-migration-guide\">here</a>. If you have any feedback or run into any issues, please do let us know in our <a href=\"https://devcommunity.pipedrive.com/\">Developers’ Community</a>!</p>\n       \n  </div>\n</div>"
}
[/block]

Breaking change: Webhooks v2 will become the new default version

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">December 2nd, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We are introducing token-based rate limits for API requests.</p>\n      \n      <h2>What is changing?</h2>\n      <p><b>Token-Based Rate Limits</b>: API requests will now consume tokens from the company's daily budget, which resets every 24 hours. If the token budget is exceeded, further requests will return a 429 (Too Many Requests) response until the budget resets the next day.</p>\n      <p><b>APIv2</b>: We encourage migrating to APIv2, which is more efficient and comes with a lower token cost per request. This can help reduce your token consumption and improve performance.</p>\n\t\t\t\n      \n      <h2>Why it is changing?</h2>\n\t\t\t<p>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. </p>\n      \n      <h2>Timeline of changes</h2>\n      <ul>\n        <li><b>December 2nd, 2024</b>: Token-based rate limits will apply to all new signups.</li>\n        <li><b>March 1st, 2025</b>: The token-based rate limits will begin rolling out for existing customers.</li>\n        <li><b>May 31st, 2025</b>: The rollout will be complete, and all existing customers will be subject to the new limits.</li>\n      </ul>\n  \n      <h2>Additional resources:</h2>\n      <ul>\n        <li><a href=\"https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting\">Developer documentation</a></li>\n        <li><a href=\"https://pipedrive.readme.io/docs/guide-for-optimizing-api-usage\">API usage optimization</a></li>\n        <li><a href=\"https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide\">APIv2 Migration Guide</a></li>\n      </ul>\n\n      <br />\n      <p>If you have any questions or comments, feel free to let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n       \n  </div>\n</div>"
}
[/block]

Breaking changes: Token-Based Rate Limits for API Usage

Breaking changes: Token-Based Rate Limits for API requests

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">December 2, 2024</span>\n    </div>\n    <div class=\"change-area\">\n        <p>We are happy to announce new production-ready v2 endpoints for Products, Pipelines and Stages API to offer a fast and performant way for interacting with the Pipedrive API:\n        <ul>\n            <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products\" target=\"blank\">Products API</a></li>\n            <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Pipelines\" target=\"blank\">Pipelines API</a></li>\n            <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Stages\" target=\"blank\">Stages API</a></li>\n        </ul>\n        </p>\n        <h3><b>What is the benefit of the new endpoints?</b></h3>\n        <p>We are introducing API v2 to eventually replace v1 endpoints. API v2 is more performant and offers better developer experience. See more information here:</p>\n        <ul>\n            <li><a href=\"https://pipedrive.readme.io/docs/pipedrive-api-v2\" target=\"blank\">Pipedrive API v2 overview</a></li>\n            <li><a href=\"https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide\" target=\"blank\">Pipedrive API v2 migration guide</a></li>\n        </ul>\n\n    </div>\n</div>"
}
[/block]

Introducing new v2 endpoints for Products, Pipelines and Stages API

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">November 18th, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>Update on new entity count limits for a set of features</p>\n  \n      <h2>What is changing?</h2>\n      <p>The format of the text in the <code>error</code> response field is being updated for entity count limits that were announced previously <a href=\"https://developers.pipedrive.com/changelog/post/breaking-change-new-entity-count-limits-for-a-set-of-features\">in this changelog update</a>.</p>      \n      \n      <p>Affected endpoints:\n        <ul>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/ActivityTypes#addActivityType\">POST /v1/activityTypes</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField\">POST /v1/dealFields</a></li>\n\t\t\t\t\t<li><a href=\"https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealField\">PUT /v1/dealFields/{id}</a></li>\n         \t<li><a href=\"https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField\">POST /v1/organizationFields</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationField\">PUT /v1/organizationFields/{id}</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField\">POST /v1/personFields</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonField\">PUT /v1/personFields/{id}</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField\">POST /v1/productFields</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/ProductFields#updateProductField\">PUT /v1/productFields/{id}</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\">POST /v1/deals/{id}/products</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Filters#addFilter\">POST /v1/filters</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Tasks#addTask\">POST /v1/tasks</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Tasks#updateTask\">PUT /v1/tasks/{id}</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/OrganizationRelationships#addOrganizationRelationship\">POST /v1/organizationRelationships</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/OrganizationRelationships#updateOrganizationRelationship\">PUT /v1/organizationRelationships/{id}</a></li>\n      </ul>\n            \n\t\t\t<p>\n        Here's an example of the <code>403</code> error response for <code>POST</code>request:<br />\n        <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\" role=\"tablist\"><button aria-selected=\"true\" class=\"CodeTabs_active\" role=\"tab\" type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\" role=\"tabpanel\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\" tabindex=\"0\"><div class=\"cm-s-neo\">{\n  <span class=\"cm-property\">\"success\"</span>: <span class=\"cm-atom\">false</span>,\n  <span class=\"cm-property\">\"error\"</span>: <span class=\"cm-string\">\"Couldn't add activity type. You've reached the activity type per company limit.\"</span>,\n  <span class=\"cm-property\">\"error_info\"</span>: <span class=\"cm-string\">\"Please check developers.pipedrive.com for more information about Pipedrive API\"</span>,\n  <span class=\"cm-property\">\"data\"</span>: <span class=\"cm-atom\">null</span>,\n  <span class=\"cm-property\">\"additional_data</span>: <span class=\"cm-atom\">null</span>\n}\n\n</div></code></pre></div></div>\n\t\t\t</p>\n\t\t\t<br />\n            \n     <p>\n        Here's an example of the <code>403</code> error response for <code>PUT</code>request:<br />\n        <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\" role=\"tablist\"><button aria-selected=\"true\" class=\"CodeTabs_active\" role=\"tab\" type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\" role=\"tabpanel\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\" tabindex=\"0\"><div class=\"cm-s-neo\">{\n  <span class=\"cm-property\">\"success\"</span>: <span class=\"cm-atom\">false</span>,\n  <span class=\"cm-property\">\"error\"</span>: <span class=\"cm-string\">\"Couldn't add activity type. You've reached the activity type per company limit.\"</span>,\n  <span class=\"cm-property\">\"error_info\"</span>: <span class=\"cm-string\">\"Please check developers.pipedrive.com for more information about Pipedrive API\"</span>,\n  <span class=\"cm-property\">\"data\"</span>: <span class=\"cm-atom\">null</span>,\n  <span class=\"cm-property\">\"additional_data</span>: <span class=\"cm-atom\">null</span>\n}\n\n</div></code></pre></div></div>\n\t\t\t</p>\n\t\t\t<br />\n           \n      <h2>Why it is changing?</h2>\n<p>This update aims to improve clarity and provide a better user experience by enhancing the wording in error messages.</p>\n     \n      <p>If you have any questions or comments, feel free to let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n       \n  </div>\n</div>"
}
[/block]

Update on new entity count limits for a set of features

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">October 2nd, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>New custom fields selector in Products endpoint</p>\n   \n      \n\t\t\t\n      <h2>What is changing?</h2>\n      <p>We’ve added a new query parameter - <code>custom_fields</code> - to the <a href=\"https://developers.pipedrive.com/docs/api/v1/Products#getProducts\" target=\"_blank\">GET /api/v2/products</a> endpoint that can be used if you are only interested in a particular set of custom fields.\nThe query parameter is a comma separated string of custom field keys. When included the endpoint response will only include the custom fields defined in the query parameter.\n</p>\n      \n      \n      <p>If you have any questions or comments, feel free to let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n       \n  </div>\n</div>"
}
[/block]

{"product": ["API"], "features": ["Products”], "email_description": "Added new selector to Products endpoint" }

New custom fields selector in Products endpoint

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">January 15th, 2025</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We are introducing changes to files related API endpoints.</p>\n   \n      \n\t\t\t\n      <h2>What is changing?</h2>\n      <p>Reducing max page size (`limit` parameter) from 500 to 100 for the following endpoints:</p>\n      \n     \t<br/>\n      \n      <ul>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Files#getFiles\" target=\"_blank\">GET v1/files</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealFiles\" target=\"_blank\">GET v1/deals/{id}/files</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationFiles\" target=\"_blank\">GET v1/organizations/{id}/files</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFiles\" target=\"_blank\">GET v1/persons/{id}/files</a></li>\n      </ul>\n      \n      <p>If a client passes a limit higher than 100, no error will be returned and the API will treat it as if 100 was passed.</p>\n      <p>Default page size remains 100. Requests without limit param specified will return up to 100 items.</p>\n      \n      \n      \n      <h2>Why is it changing?</h2>\n      <p>To improve the stability and performance of the endpoints and reduce impact on other parts of the system.</p>\n      \n\n      \n      <h2>Migration guide</h2>\n      <p>If you are specifying a limit larger than 100, please migrate to new max limit of 100.</p>\n      <p>Alternatively, do not send a limit altogether to rely on the default limit of 100. If you are not paginating the results and just grabbing the first page, it is recommended to properly paginate the results in case there is more than 100 files in the response.</p>\n      \n      <p>Pseudocode example properly paginating the results:\n        <pre>\n        \n  limit = 100  # Alternatively omit the limit (it will default to 100)\n  start = 0\n\n  do {\n    response = fetch_files(start, limit)\n    # process files here ...  \n\n    start = response.additional_data.pagination.next_start\n  }\n  while (response.additional_data.pagination.more_items_in_collection)\n\n        </pre>\n      </p>\n      \n      <p>If you have any questions or comments, feel free to let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n       \n  </div>\n</div>"
}
[/block]

Breaking change: Reducing maximum page size for files endpoints

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">November 25th, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We are introducing new limits on the number and periodicity of subscriptions connected to Products and Deal Products.</p>\n   \n      \n      <h2>What is changing?</h2>\n      <p>There are 3 changes that we will introduce:<br />\n        <ol>\n          <li>The maximum number of cycles per subscription in Deal Products and Products is now <b>208</b></li>            \n          <li>The billing start date limit in the past for Deal Products and Products is now <b>10 years</b></li>\n          <li>For Deal Products, we are restricting the <b>weekly subscriptions</b> to a <b>fix number of cycles</b></li>\n\t      </ol>\n      </p>\n      \n      <p>Affected endpoints:<br />\n      \t<ul>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"_blank\">POST/v1/deals/{id}/products</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"_blank\">PUT/v1/deals/{id}/products/{dealProductId}</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#addProduct\" target=\"_blank\">POST/v1/products</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#updateProduct\" target=\"_blank\">PUT/v1/products/{id}</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"_blank\">POST/v2/deals/{id}/products</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"_blank\">PATCH/v2/deals/{id}/products/{dealProductId}</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#addProduct\" target=\"_blank\">POST/v2/products</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#updateProduct\" target=\"_blank\">PATCH/v2/products/{id}</a></li>\n      \t</ul>\n      </p>\n      \n      <h2>Why is it changing?</h2>\n      <p>To ensure we can replicate all the Subscriptions data in the new Insights revenue report, we are limiting the number of total payments per Deal, ensuring that all the data will always be visible in your reports!</p>\n      \n      <br />\n      \n      <p>If you have any questions or comments, feel free to let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n       \n  </div>\n</div>"
}
[/block]

We are changing the behavior of subscriptions limits

Breaking change: Change Product Subscriptions Limits

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">November 18th, 2024</span>\n    </div>\n    <div class=\"change-area\">\n       <blockquote class=\"callout callout_info\" theme=\"📘\">\n         <p class=\"callout-heading empty\"><span class=\"callout-icon\">📘</span></p>\n         <p><strong>Attention: breaking changes!</strong>: </p>\n         <p>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.</p>\n      </blockquote>\n          \n      <h2>Why is it changing?</h2>\n      <p>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.</p>\n      \n      <h2>Summary of the new limits</h2>\n      <p>\n        The summarised list of affected entities and corresponding new limits is as follows:\n        <ol>\n          <li>Activity types - new limit of <strong>1,000</strong> per company</li>\n          <li>Custom field options - new limit of <strong>1,000</strong> options per custom field</li>\n          <li>Deal products - new limit of <strong>200</strong> attached products per deal</li>\n          <li>Filters - new limit of <strong>5,000</strong> per company</li>\n          <li>Tasks - new limit of <strong>5,000</strong> per project</li>\n          <li>Related organizations - new limit of <strong>10,000</strong> per contact organization</li>\n\t      </ol>\n      </p>\n      \n\t  \t<h2>What is changing?</h2>\n  \n  \t\t\n  \n\t\t  <p><strong>1. Limit on activity types count</strong></p>\n\t\t  <p>From <strong>November 18th</strong>, activity types will have a <strong>a maximum total count limit of 1,000 activity types per company</strong>. In case the limit is reached, adding new activity types will fail with a <code>403</code> error code for the following endpoints:\n        <ul>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/ActivityTypes#addActivityType\" target=\"_blank\">POST /v1/activityTypes</a></li>\n\t\t\t  </ul>\n      </p>\n\t\t\t<p>Editing existing activity types is not affected by this limit.</p>\n\t\t\t<p>\n        Here's an example of the <code>403</code> error response:<br />\n        <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\" role=\"tablist\"><button aria-selected=\"true\" class=\"CodeTabs_active\" role=\"tab\" type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\" role=\"tabpanel\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\" tabindex=\"0\"><div class=\"cm-s-neo\">{\n  <span class=\"cm-property\">\"success\"</span>: <span class=\"cm-atom\">false</span>,\n  <span class=\"cm-property\">\"error\"</span>: <span class=\"cm-string\">\"Maximum number of activity types per company reached. Maximum limit: 1000\"</span>,\n  <span class=\"cm-property\">\"error_info\"</span>: <span class=\"cm-string\">\"Please check developers.pipedrive.com for more information about Pipedrive API\"</span>,\n  <span class=\"cm-property\">\"data\"</span>: <span class=\"cm-atom\">null</span>,\n  <span class=\"cm-property\">\"additional_data</span>: <span class=\"cm-atom\">null</span>\n}\n\n</div></code></pre></div></div>\n\t\t\t</p>\n\t\t\t<br />\n\n\t\t\t\n\n \t\t\t<p><strong>2. Limit on custom field options count</strong></p>\n      <p>From <strong>November 18th</strong>, option- and multi-option custom fields will have a <strong>maximum count limit of 1,000 options per one custom field</strong>. In case the limit is reached for a custom field, adding new options to this field will fail with a <code>403</code> error code. This change affects the following endpoints:\n        <ul>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField\" target=\"_blank\">POST /v1/dealFields</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealField\" target=\"_blank\">PUT /v1/dealFields/{id}</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField\" target=\"_blank\">POST /v1/organizationFields</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationField\" target=\"_blank\">PUT /v1/organizationFields/{id}</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField\" target=\"_blank\">POST /v1/personFields</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonField\" target=\"_blank\">PUT /v1/personFields/{id}</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField\" target=\"_blank\">POST /v1/productFields</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/ProductFields#updateProductField\" target=\"_blank\">PUT /v1/productFields/{id}</a></li>\n\t\t\t  </ul>\n      </p>\n\t\t\t<p>\n        Here's an example of the <code>403</code> error response:<br />\n        <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\" role=\"tablist\"><button aria-selected=\"true\" class=\"CodeTabs_active\" role=\"tab\" type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\" role=\"tabpanel\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\" tabindex=\"0\"><div class=\"cm-s-neo\">{\n  <span class=\"cm-property\">\"success\"</span>: <span class=\"cm-atom\">false</span>,\n  <span class=\"cm-property\">\"error\"</span>: <span class=\"cm-string\">\"Maximum number of options per field reached. Maximum limit: 1000\"</span>,\n  <span class=\"cm-property\">\"error_info\"</span>: <span class=\"cm-string\">\"Please check developers.pipedrive.com for more information about Pipedrive API\"</span>,\n  <span class=\"cm-property\">\"data\"</span>: <span class=\"cm-atom\">null</span>,\n  <span class=\"cm-property\">\"additional_data</span>: <span class=\"cm-atom\">null</span>\n}\n\n</div></code></pre></div></div>\n\t\t\t</p>\n\t\t\t<br />\n\n\t\t\t\n\t\t\t<p><strong>3. Limit on deal products</strong></p>\n      <p>From <strong>November 18th</strong>, products attached to a deal will have a <strong>a maximum count limit of 200 products per deal</strong>. In case the limit is reached for a deal, adding or linking more products to this deal will fail with a <code>403</code> error code. This change affects the following endpoints:\n        <ul>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"_blank\">POST /v1/deals/{id}/products</a></li>\n\t\t\t  </ul>\n      </p>\n\t\t\t<p>\n        Here's an example of the <code>403</code> error response:<br />\n        <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\" role=\"tablist\"><button aria-selected=\"true\" class=\"CodeTabs_active\" role=\"tab\" type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\" role=\"tabpanel\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\" tabindex=\"0\"><div class=\"cm-s-neo\">{\n  <span class=\"cm-property\">\"success\"</span>: <span class=\"cm-atom\">false</span>,\n  <span class=\"cm-property\">\"error\"</span>: <span class=\"cm-string\">\"Maximum number of products per deal reached. Maximum limit: 200\"</span>,\n  <span class=\"cm-property\">\"error_info\"</span>: <span class=\"cm-string\">\"Please check developers.pipedrive.com for more information about Pipedrive API\",</span>,\n  <span class=\"cm-property\">\"data\"</span>: <span class=\"cm-atom\">null</span>,\n  <span class=\"cm-property\">\"additional_data\"</span>: <span class=\"cm-atom\">null</span>\n}\n\n</div></code></pre></div></div>\n\t\t\t</p>\n\t\t\t<br />\n\t\t\n\t\t\t\n\t\t\t<p><strong>4. Limit on filters count</strong></p>\n      <p>From <strong>November 18th</strong>, filters will have a <strong>a maximum total count limit of 5,000 filters per company</strong>. In case the limit is reached, adding new filters will fail with a <code>403</code> error code for the following endpoints:\n        <ul>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Filters#addFilter\" target=\"_blank\">POST /v1/filters</a></li>\n\t\t\t  </ul>\n      </p>\n\t\t\t<p>\n        Here's an example of the <code>403</code> error response:<br />\n        <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\" role=\"tablist\"><button aria-selected=\"true\" class=\"CodeTabs_active\" role=\"tab\" type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\" role=\"tabpanel\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\" tabindex=\"0\"><div class=\"cm-s-neo\">{\n  <span class=\"cm-property\">\"success\"</span>: <span class=\"cm-atom\">false</span>,\n  <span class=\"cm-property\">\"error\"</span>: <span class=\"cm-string\">\"Maximum number of filters per company reached. Maximum limit: 5000\"</span>,\n  <span class=\"cm-property\">\"error_info\"</span>: <span class=\"cm-string\">\"Please check developers.pipedrive.com for more information about Pipedrive API\"</span>,\n  <span class=\"cm-property\">\"data\"</span>: <span class=\"cm-atom\">null</span>,\n  <span class=\"cm-property\">\"additional_data\"</span>: <span class=\"cm-atom\">null</span>\n}\n\n</div></code></pre></div></div>\n\t\t\t</p>\n\t\t\t<br />\n\n\t\t\t\n\t\t\t<p><strong>5. Limit on project tasks count</strong></p>\n      <p>From <strong>November 18th</strong>, tasks will have a <strong>a maximum count limit of 5,000 tasks per one project</strong>. In case the limit is reached for a project, adding or linking more tasks to this project will fail with a <code>403</code> error code. This change affects the following endpoints:\n        <ul>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Tasks#addTask\" target=\"_blank\">POST /v1/tasks</a></li>\n          <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Tasks#updateTask\" target=\"_blank\">PUT /v1/tasks/{id}</a></li>\n\t\t\t  </ul>\n      </p>\n\t\t\t<p>\n        Here's an example of the <code>403</code> error response:<br />\n        <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\" role=\"tablist\"><button aria-selected=\"true\" class=\"CodeTabs_active\" role=\"tab\" type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\" role=\"tabpanel\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\" tabindex=\"0\"><div class=\"cm-s-neo\">{\n  <span class=\"cm-property\">\"success\"</span>: <span class=\"cm-atom\">false</span>,\n  <span class=\"cm-property\">\"error\"</span>: <span class=\"cm-string\">\"Maximum number of tasks per project reached. Maximum limit: 5000\"</span>,\n  <span class=\"cm-property\">\"error_info\"</span>: <span class=\"cm-string\">\"Please check developers.pipedrive.com for more information about Pipedrive API\"</span>,\n  <span class=\"cm-property\">\"data\"</span>: <span class=\"cm-atom\">null</span>,\n  <span class=\"cm-property\">\"additional_data\"</span>: <span class=\"cm-atom\">null</span>\n}\n\n</div></code></pre></div></div>\n\t\t\t</p>\n\t\t\t<br />\n\n\n\t\t\t\n\t\t\t<p><strong>6. Limit on related organizations count</strong></p>\n      <p>From <strong>November 18th</strong>, contact organizations will have a <strong>maximum count limit of 10,000 related organizations  per one contact organization</strong>. In case the limit is reached for an organization, linking more related contact organizations to this contact organization will fail with a <code>403</code> error code. This change affects the following endpoints:\n        <ul>\n          <li><a href=\"\" target=\"_blank\">POST /v1/organizationRelationships</a></li>\n          <li><a href=\"\" target=\"_blank\">PUT /v1/organizationRelationships/{id}</a></li>\n\t\t\t  </ul>\n      </p>\n\t\t\t<p>\n        Here's an example of the <code>403</code> error response:<br />\n        <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\" role=\"tablist\"><button aria-selected=\"true\" class=\"CodeTabs_active\" role=\"tab\" type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\" role=\"tabpanel\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\" tabindex=\"0\"><div class=\"cm-s-neo\">{\n  <span class=\"cm-property\">\"success\"</span>: <span class=\"cm-atom\">false</span>,\n  <span class=\"cm-property\">\"error\"</span>: <span class=\"cm-string\">\"Maximum number of related organizations per contact organization reached. Maximum limit: 10000\"</span>,\n  <span class=\"cm-property\">\"error_info\"</span>: <span class=\"cm-string\">\"Please check developers.pipedrive.com for more information about Pipedrive API\"</span>,\n  <span class=\"cm-property\">\"data\"</span>: <span class=\"cm-atom\">null</span>,\n  <span class=\"cm-property\">\"additional_data\"</span>: <span class=\"cm-atom\">null</span>\n}\n\n</div></code></pre></div></div>\n\t\t\t</p>\n\t\t\t<br />\n\n\n\n      <p>If you have any questions or comments, feel free to let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n       \n  </div>\n</div>"
}
[/block]

New entity count limits for a set of features

Breaking change: new entity count limits for a set of features

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">November 12th, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <h2>What is changing?</h2>\n      <p>Starting from November 12, 2024, all public and private apps will be gradually migrated to encrypted access tokens associated with <a href=\"https://pipedrive.readme.io/docs/marketplace-oauth-api\" target=\"_blank\">OAuth 2.0</a>. This only applies to apps that weren't affected by <a href=\"https://developers.pipedrive.com/changelog/post/improved-security-for-access-tokens-related-to-oauth-20\" target=\"_blank\">last year’s changes</a>.</p>\n      \n      <h2>Why are you migrating apps?</h2>\n      <p>We’re making this change to improve security, comply with <a href=\"https://oauth.net/2/\" target=\"_blank\">industry standards</a> and prepare for the full deprecation of the old encryption.</p>\n      \n      <h2>Migration guide</h2>\n      <p>New access tokens will be longer for improved security. Please check your app’s authentication logic and allocate enough storage space. We recommend using a minimum of varchar (768) for storing the tokens in your app’s database.</p>\n      <p>For more information about OAuth authorization, check out <a href=\"https://pipedrive.readme.io/docs/marketplace-oauth-authorization\" target=\"_blank\">this article</a>.</p>\n      <p>If you have any questions or comments, feel free to let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n       \n  </div>\n</div>"
}
[/block]

Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog