<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 15th, 2025</span>
    </div>
    <div class="change-area">
      <p>We are introducing changes to files related API endpoints.</p>
   
      
			
      <h2>What is changing?</h2>
      <p>Reducing max page size (\`limit\` parameter) from 500 to 100 for the following endpoints:</p>
      
     	<br/>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Files#getFiles" target="_blank">GET v1/files</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealFiles" target="_blank">GET v1/deals/{id}/files</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationFiles" target="_blank">GET v1/organizations/{id}/files</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFiles" target="_blank">GET v1/persons/{id}/files</a></li>
      </ul>
      
      <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>
      <p>Default page size remains 100. Requests without limit param specified will return up to 100 items.</p>
      
      
      
      <h2>Why is it changing?</h2>
      <p>To improve the stability and performance of the endpoints and reduce impact on other parts of the system.</p>
      

      
      <h2>Migration guide</h2>
      <p>If you are specifying a limit larger than 100, please migrate to new max limit of 100.</p>
      <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>
      
      <p>Pseudocode example properly paginating the results:
        <pre>
        
  limit = 100  # Alternatively omit the limit (it will default to 100)
  start = 0

  do {
    response = fetch_files(start, limit)
    # process files here ...  

    start = response.additional_data.pagination.next_start
  }
  while (response.additional_data.pagination.more_items_in_collection)

        </pre>
      </p>
      
      <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>
       
  </div>
</div>
`}</HTMLBlock>

Breaking change: Reducing maximum page size for files endpoints


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 15th, 2025</span>
    </div>
    <div class="change-area">
      <p>We are introducing changes to files related API endpoints.</p>
   
      
			
      <h2>What is changing?</h2>
      <p>Reducing max page size (\`limit\` parameter) from 500 to 100 for the following endpoints:</p>
      
     	<br/>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Files#getFiles" target="_blank">GET v1/files</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealFiles" target="_blank">GET v1/deals/{id}/files</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationFiles" target="_blank">GET v1/organizations/{id}/files</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFiles" target="_blank">GET v1/persons/{id}/files</a></li>
      </ul>
      
      <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>
      <p>Default page size remains 100. Requests without limit param specified will return up to 100 items.</p>
      
      
      
      <h2>Why is it changing?</h2>
      <p>To improve the stability and performance of the endpoints and reduce impact on other parts of the system.</p>
      

      
      <h2>Migration guide</h2>
      <p>If you are specifying a limit larger than 100, please migrate to new max limit of 100.</p>
      <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>
      
      <p>Pseudocode example properly paginating the results:
        <pre>
        
  limit = 100  # Alternatively omit the limit (it will default to 100)
  start = 0

  do {
    response = fetch_files(start, limit)
    # process files here ...  

    start = response.additional_data.pagination.next_start
  }
  while (response.additional_data.pagination.more_items_in_collection)

        </pre>
      </p>
      
      <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>
       
  </div>
</div>


<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 25th, 2024</span>
    </div>
    <div class="change-area">
      <p>We are introducing new limits on the number and periodicity of subscriptions connected to Products and Deal Products.</p>
   
      
      <h2>What is changing?</h2>
      <p>There are 3 changes that we will introduce:<br />
        <ol>
          <li>The maximum number of cycles per subscription in Deal Products and Products is now <b>208</b></li>            
          <li>The billing start date limit in the past for Deal Products and Products is now <b>10 years</b></li>
          <li>For Deal Products, we are restricting the <b>weekly subscriptions</b> to a <b>fix number of cycles</b></li>
	      </ol>
      </p>
      
      <p>Affected endpoints:<br />
      	<ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST/v1/deals/{id}/products</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PUT/v1/deals/{id}/products/{dealProductId}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_blank">POST/v1/products</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_blank">PUT/v1/products/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST/v2/deals/{id}/products</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PATCH/v2/deals/{id}/products/{dealProductId}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_blank">POST/v2/products</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_blank">PATCH/v2/products/{id}</a></li>
      	</ul>
      </p>
      
      <h2>Why is it changing?</h2>
      <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>
      
      <br />
      
      <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>
       
  </div>
</div>
`}</HTMLBlock>

We are changing the behavior of subscriptions limits

Breaking change: Change Product Subscriptions Limits


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 25th, 2024</span>
    </div>
    <div class="change-area">
      <p>We are introducing new limits on the number and periodicity of subscriptions connected to Products and Deal Products.</p>
   
      
      <h2>What is changing?</h2>
      <p>There are 3 changes that we will introduce:<br />
        <ol>
          <li>The maximum number of cycles per subscription in Deal Products and Products is now <b>208</b></li>            
          <li>The billing start date limit in the past for Deal Products and Products is now <b>10 years</b></li>
          <li>For Deal Products, we are restricting the <b>weekly subscriptions</b> to a <b>fix number of cycles</b></li>
	      </ol>
      </p>
      
      <p>Affected endpoints:<br />
      	<ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST/v1/deals/{id}/products</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PUT/v1/deals/{id}/products/{dealProductId}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_blank">POST/v1/products</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_blank">PUT/v1/products/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST/v2/deals/{id}/products</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PATCH/v2/deals/{id}/products/{dealProductId}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_blank">POST/v2/products</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_blank">PATCH/v2/products/{id}</a></li>
      	</ul>
      </p>
      
      <h2>Why is it changing?</h2>
      <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>
      
      <br />
      
      <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>
       
  </div>
</div>


<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 18th, 2024</span>
    </div>
    <div class="change-area">
       <blockquote class="callout callout_info" theme="📘">
         <p class="callout-heading empty"><span class="callout-icon">📘</span></p>
         <p><strong>Attention: breaking changes!</strong>: </p>
         <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>
      </blockquote>
          
      <h2>Why is it changing?</h2>
      <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>
      
      <h2>Summary of the new limits</h2>
      <p>
        The summarised list of affected entities and corresponding new limits is as follows:
        <ol>
          <li>Activity types - new limit of <strong>1,000</strong> per company</li>
          <li>Custom field options - new limit of <strong>1,000</strong> options per custom field</li>
          <li>Deal products - new limit of <strong>200</strong> attached products per deal</li>
          <li>Filters - new limit of <strong>5,000</strong> per company</li>
          <li>Tasks - new limit of <strong>5,000</strong> per project</li>
          <li>Related organizations - new limit of <strong>10,000</strong> per contact organization</li>
	      </ol>
      </p>
      
	  	<h2>What is changing?</h2>
  
  		
  
		  <p><strong>1. Limit on activity types count</strong></p>
		  <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:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ActivityTypes#addActivityType" target="_blank">POST /v1/activityTypes</a></li>
			  </ul>
      </p>
			<p>Editing existing activity types is not affected by this limit.</p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of activity types per company reached. Maximum limit: 1000"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />

			

 			<p><strong>2. Limit on custom field options count</strong></p>
      <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:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField" target="_blank">POST /v1/dealFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealField" target="_blank">PUT /v1/dealFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField" target="_blank">POST /v1/organizationFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationField" target="_blank">PUT /v1/organizationFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField" target="_blank">POST /v1/personFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonField" target="_blank">PUT /v1/personFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField" target="_blank">POST /v1/productFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#updateProductField" target="_blank">PUT /v1/productFields/{id}</a></li>
			  </ul>
      </p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of options per field reached. Maximum limit: 1000"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />

			
			<p><strong>3. Limit on deal products</strong></p>
      <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:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST /v1/deals/{id}/products</a></li>
			  </ul>
      </p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of products per deal reached. Maximum limit: 200"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API",</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data"</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />
		
			
			<p><strong>4. Limit on filters count</strong></p>
      <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:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Filters#addFilter" target="_blank">POST /v1/filters</a></li>
			  </ul>
      </p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of filters per company reached. Maximum limit: 5000"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data"</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />

			
			<p><strong>5. Limit on project tasks count</strong></p>
      <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:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#addTask" target="_blank">POST /v1/tasks</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#updateTask" target="_blank">PUT /v1/tasks/{id}</a></li>
			  </ul>
      </p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of tasks per project reached. Maximum limit: 5000"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data"</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />


			
			<p><strong>6. Limit on related organizations count</strong></p>
      <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:
        <ul>
          <li><a href="" target="_blank">POST /v1/organizationRelationships</a></li>
          <li><a href="" target="_blank">PUT /v1/organizationRelationships/{id}</a></li>
			  </ul>
      </p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of related organizations per contact organization reached. Maximum limit: 10000"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data"</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />



      <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>
       
  </div>
</div>
`}</HTMLBlock>

New entity count limits for a set of features

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

<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 18th, 2024</span>
    </div>
    <div class="change-area">
       <blockquote class="callout callout_info" theme="📘">
         <p class="callout-heading empty"><span class="callout-icon">📘</span></p>
         <p><strong>Attention: breaking changes!</strong>: </p>
         <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>
      </blockquote>
          
      <h2>Why is it changing?</h2>
      <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>
      
      <h2>Summary of the new limits</h2>
      <p>
        The summarised list of affected entities and corresponding new limits is as follows:
        <ol>
          <li>Activity types - new limit of <strong>1,000</strong> per company</li>
          <li>Custom field options - new limit of <strong>1,000</strong> options per custom field</li>
          <li>Deal products - new limit of <strong>200</strong> attached products per deal</li>
          <li>Filters - new limit of <strong>5,000</strong> per company</li>
          <li>Tasks - new limit of <strong>5,000</strong> per project</li>
          <li>Related organizations - new limit of <strong>10,000</strong> per contact organization</li>
	      </ol>
      </p>
      
	  	<h2>What is changing?</h2>
  
  		
  
		  <p><strong>1. Limit on activity types count</strong></p>
		  <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:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ActivityTypes#addActivityType" target="_blank">POST /v1/activityTypes</a></li>
			  </ul>
      </p>
			<p>Editing existing activity types is not affected by this limit.</p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of activity types per company reached. Maximum limit: 1000"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />

			

 			<p><strong>2. Limit on custom field options count</strong></p>
      <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:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField" target="_blank">POST /v1/dealFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealField" target="_blank">PUT /v1/dealFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField" target="_blank">POST /v1/organizationFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationField" target="_blank">PUT /v1/organizationFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField" target="_blank">POST /v1/personFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonField" target="_blank">PUT /v1/personFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField" target="_blank">POST /v1/productFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#updateProductField" target="_blank">PUT /v1/productFields/{id}</a></li>
			  </ul>
      </p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of options per field reached. Maximum limit: 1000"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />

			
			<p><strong>3. Limit on deal products</strong></p>
      <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:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST /v1/deals/{id}/products</a></li>
			  </ul>
      </p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of products per deal reached. Maximum limit: 200"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API",</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data"</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />
		
			
			<p><strong>4. Limit on filters count</strong></p>
      <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:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Filters#addFilter" target="_blank">POST /v1/filters</a></li>
			  </ul>
      </p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of filters per company reached. Maximum limit: 5000"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data"</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />

			
			<p><strong>5. Limit on project tasks count</strong></p>
      <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:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#addTask" target="_blank">POST /v1/tasks</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#updateTask" target="_blank">PUT /v1/tasks/{id}</a></li>
			  </ul>
      </p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of tasks per project reached. Maximum limit: 5000"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data"</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />


			
			<p><strong>6. Limit on related organizations count</strong></p>
      <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:
        <ul>
          <li><a href="" target="_blank">POST /v1/organizationRelationships</a></li>
          <li><a href="" target="_blank">PUT /v1/organizationRelationships/{id}</a></li>
			  </ul>
      </p>
			<p>
        Here's an example of the <code>403</code> error response:<br />
        <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">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Maximum number of related organizations per contact organization reached. Maximum limit: 10000"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data"</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
			<br />



      <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>
       
  </div>
</div>

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 12th, 2024</span>
    </div>
    <div class="change-area">
      <h2>What is changing?</h2>
      <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>
      
      <h2>Why are you migrating apps?</h2>
      <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>
      
      <h2>Migration guide</h2>
      <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>
      <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>
      <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>
       
  </div>
</div>
`}</HTMLBlock>


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 12th, 2024</span>
    </div>
    <div class="change-area">
      <h2>What is changing?</h2>
      <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>
      
      <h2>Why are you migrating apps?</h2>
      <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>
      
      <h2>Migration guide</h2>
      <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>
      <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>
      <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>
       
  </div>
</div>


Improved security for access tokens related to OAuth 2.0

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 1st, 2024</span>
    </div>
    <div class="change-area">
    
      <p>We are introducing limit to since_timestamp parameter</p>
   
      
      <h2>What is changing?</h2>
      
      <a href="https://developers.pipedrive.com/docs/api/v1/Recents#getRecents" target="_blank">GET v1/recents</a>
      
      <br/>
      <p>Added a limit to the <code>since_timestamp</code> parameter.
       <br/>Mobile users can now retrieve a maximum of 3 months of past data, even if they request data from a date further in the past.
        <br/>All other users will be limited to retrieving a maximum of 1 month of past data, even if they request data from a date further in the past.
      </p>
      
      <h2>Why is it changing?</h2>
      
      <p>Improve the performance of the endpoint by applying limits.</p><br />
      
           	<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>
       
  </div>
</div>
`}</HTMLBlock>

Endpoint /recents will be limited to retrieving a maximum of 1 month of past data via API

Breaking change: Added limit to the <code>since_timestamp</code> parameter


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 1st, 2024</span>
    </div>
    <div class="change-area">
    
      <p>We are introducing limit to since_timestamp parameter</p>
   
      
      <h2>What is changing?</h2>
      
      <a href="https://developers.pipedrive.com/docs/api/v1/Recents#getRecents" target="_blank">GET v1/recents</a>
      
      <br/>
      <p>Added a limit to the <code>since_timestamp</code> parameter.
       <br/>Mobile users can now retrieve a maximum of 3 months of past data, even if they request data from a date further in the past.
        <br/>All other users will be limited to retrieving a maximum of 1 month of past data, even if they request data from a date further in the past.
      </p>
      
      <h2>Why is it changing?</h2>
      
      <p>Improve the performance of the endpoint by applying limits.</p><br />
      
           	<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>
       
  </div>
</div>


<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 3, 2024</span>
    </div>
    <div class="change-area">
      <p>We are introducing six new fields. With the addition of the subscription deal products, new fields were added to better reflect a deal’s value</p>
      
			<br/>
      
			<h2>What is being added?</h2>

			
      <p>The new fields are: <br />
        <ul>
          <li>
            <code>mrr</code> - Monthly Recurring Revenue. Recurring revenue of the deal subscriptions per month
          </li>
          <li>
            <code>arr</code> - Annual Recurring Revenue. Recurring revenue of the deal subscriptions per year
          </li>
          <li>
            <code>acv</code> - Annual Contract Value. Sum of recurring revenue and one-time fees in a single year for a deal
          </li>
          <li>
            <code>mrr_currency</code> - Currency of the <code>mrr</code> field
          </li>
          <li>
            <code>arr_currency</code> - Currency of the <code>arr</code> field
          </li>
          <li>
            <code>acv_currency</code> - Currency of the <code>acv</code> field
          </li>
        </ul>

	      <p>They were also added to the responses of the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals" target="_blank">GET /v1/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeal" target="_blank">GET /v1/deals/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline" target="_blank">GET /v1/deals/timeline</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_blank">POST /v1/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#duplicateDeal" target="_blank">POST /v1/deals/duplicate</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_blank">PUT /v1/deals/{id}</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_blank">PUT /v1/deals/{id}/merge</a></li>
      </ul>
			</p>      

     	<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>

		</div>
</div>
`}</HTMLBlock>

We are adding new deal value fields in the Deals Endpoints


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 3, 2024</span>
    </div>
    <div class="change-area">
      <p>We are introducing six new fields. With the addition of the subscription deal products, new fields were added to better reflect a deal’s value</p>
      
			<br/>
      
			<h2>What is being added?</h2>

			
      <p>The new fields are: <br />
        <ul>
          <li>
            <code>mrr</code> - Monthly Recurring Revenue. Recurring revenue of the deal subscriptions per month
          </li>
          <li>
            <code>arr</code> - Annual Recurring Revenue. Recurring revenue of the deal subscriptions per year
          </li>
          <li>
            <code>acv</code> - Annual Contract Value. Sum of recurring revenue and one-time fees in a single year for a deal
          </li>
          <li>
            <code>mrr_currency</code> - Currency of the <code>mrr</code> field
          </li>
          <li>
            <code>arr_currency</code> - Currency of the <code>arr</code> field
          </li>
          <li>
            <code>acv_currency</code> - Currency of the <code>acv</code> field
          </li>
        </ul>

	      <p>They were also added to the responses of the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals" target="_blank">GET /v1/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeal" target="_blank">GET /v1/deals/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline" target="_blank">GET /v1/deals/timeline</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_blank">POST /v1/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#duplicateDeal" target="_blank">POST /v1/deals/duplicate</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_blank">PUT /v1/deals/{id}</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_blank">PUT /v1/deals/{id}/merge</a></li>
      </ul>
			</p>      

     	<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>

		</div>
</div>


New deal values fields for customers in Advanced Plan or above

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 20, 2024</span>
    </div>
    <div class="change-area">
      <p>We are introducing 4 new fields for Leads and Deals</p>
      
			<h2>What is being added?</h2>

			
      <p>The following fields are being added to Leads and Deals:<br />
        <ul>
          <li>
            <code>origin</code> - a system-generated value indicating how the entity was created (e.g. Import, API, Manually created). User cannot change this value
          </li>
          <li>
            <code>origin_id</code> - a system-generated value which specifies the <code>origin</code> further. User can supply a value in POST payload. In other cases the value is autofilled when applicable (e.g. in case <code>origin</code> is <code>Import</code>, the <code>origin_id</code> is the unique batch id). User cannot change this value
          </li>
          <li>
            <code>channel</code> - single option editable value to further specify entity source based on marketing channel. In certain cases this field is autofilled, but it doesn’t restrict users to manipulate it afterwards
          </li>
          <li>
            <code>channel_id</code> - text field for users to further specify the <code>channel</code> by themselves. In certain cases this field is autofilled, but it doesn’t restrict users to manipulate it afterwards
          </li>
        </ul>

	      <p>All four new fields are included in respective <code>GET</code>, <code>POST</code> and <code>PUT</code> responses. <code>channel</code> and <code>channel_id</code> can be included in respective <code>POST</code> and <code>PUT</code> payloads. User can get list of currently supported values for <code>origin</code> and <code>channel</code> fields from <a href="https://developers.pipedrive.com/docs/api/v1/DealFields#getDealFields" target="_blank">DealFields endpoint</a></p>
        <p>You can read more about these new fields and how to use them  in our <a href="https://support.pipedrive.com/en/article/lead-source-deals">Knowledge Base article</a></p>
        
			</p>      

     	<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>

		</div>
</div>
`}</HTMLBlock>

We are adding 4 new fields for Deals and Leads to represent entity source

Introducing 4 new fields for Leads and Deals


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 20, 2024</span>
    </div>
    <div class="change-area">
      <p>We are introducing 4 new fields for Leads and Deals</p>
      
			<h2>What is being added?</h2>

			
      <p>The following fields are being added to Leads and Deals:<br />
        <ul>
          <li>
            <code>origin</code> - a system-generated value indicating how the entity was created (e.g. Import, API, Manually created). User cannot change this value
          </li>
          <li>
            <code>origin_id</code> - a system-generated value which specifies the <code>origin</code> further. User can supply a value in POST payload. In other cases the value is autofilled when applicable (e.g. in case <code>origin</code> is <code>Import</code>, the <code>origin_id</code> is the unique batch id). User cannot change this value
          </li>
          <li>
            <code>channel</code> - single option editable value to further specify entity source based on marketing channel. In certain cases this field is autofilled, but it doesn’t restrict users to manipulate it afterwards
          </li>
          <li>
            <code>channel_id</code> - text field for users to further specify the <code>channel</code> by themselves. In certain cases this field is autofilled, but it doesn’t restrict users to manipulate it afterwards
          </li>
        </ul>

	      <p>All four new fields are included in respective <code>GET</code>, <code>POST</code> and <code>PUT</code> responses. <code>channel</code> and <code>channel_id</code> can be included in respective <code>POST</code> and <code>PUT</code> payloads. User can get list of currently supported values for <code>origin</code> and <code>channel</code> fields from <a href="https://developers.pipedrive.com/docs/api/v1/DealFields#getDealFields" target="_blank">DealFields endpoint</a></p>
        <p>You can read more about these new fields and how to use them  in our <a href="https://support.pipedrive.com/en/article/lead-source-deals">Knowledge Base article</a></p>
        
			</p>      

     	<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>

		</div>
</div>


<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 14, 2024</span>
    </div>
    <div class="change-area">
      <p>Products and Deal Products have new fields designed for managing and streamlining the sale of products that are billed recurrently.
These fields are only available starting from the Advanced plan.</p>
      
			<br/>
      
			<h2>What is being added?</h2>

			<h3>Products</h3>
			<p>The new fields are:</p>  
      <ul>
        <li><i>billing_frequency</i> - How often a customer is billed for access to a service or product</li>
        <li><i>billing_frequency_cycles</i> - The number of times the billing frequency repeats for a product in a deal
</li>
      </ul>
      
      <p>These fields were added as body parameters to the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_blank">POST /v1/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_blank">PUT /v1/products/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v2/Products#addProduct" target="_blank">POST /v2/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v2/Products#updateProduct" target="_blank">PUT /v2/products/{id}</a></li>
      </ul>
      
      <p>They were also added to the responses of the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProducts" target="_blank">GET /v1/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProduct" target="_blank">GET /v1/products/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_blank">POST /v1/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_blank">PUT /v1/products/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProducts" target="_blank">GET /v2/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProduct" target="_blank">GET /v2/products/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_blank">POST /v2/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_blank">PATCH /v2/products/{id}</a></li>
      </ul>
      
      
      <h3>Deal Products</h3>
			<p>The new fields are:</p>  
      <ul>
        <li><i>billing_frequency</i> - How often a customer is billed for access to a service or product</li>
        <li><i>billing_frequency_cycles</i> - The number of times the billing frequency repeats for a product in a deal
</li>
        <li><i>billing_start_date</i> - When the product will start to be billed
</li>
      </ul>
      
      <p>These fields were added as body parameters to the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST /v1/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PUT /v1/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts" target="_blank">GET /v2/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST /v2/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PATCH  /v2/deals/{id}/products</a></li>
      </ul>
      
      <p>They were also added to the responses of the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts" target="_blank">GET /v1/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST /v1/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PUT /v1/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts" target="_blank">GET /v2/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST /v2/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PATCH  /v2/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsProducts" target="_blank">GET /v2/deals/products</a></li>
        
      </ul>

      <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>

		</div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Products", ], "email_description": "New subscription fields in Products and Deal Products endpoints" }

New subscription fields in Products and Deal Products endpoints


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 14, 2024</span>
    </div>
    <div class="change-area">
      <p>Products and Deal Products have new fields designed for managing and streamlining the sale of products that are billed recurrently.
These fields are only available starting from the Advanced plan.</p>
      
			<br/>
      
			<h2>What is being added?</h2>

			<h3>Products</h3>
			<p>The new fields are:</p>  
      <ul>
        <li><i>billing_frequency</i> - How often a customer is billed for access to a service or product</li>
        <li><i>billing_frequency_cycles</i> - The number of times the billing frequency repeats for a product in a deal
</li>
      </ul>
      
      <p>These fields were added as body parameters to the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_blank">POST /v1/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_blank">PUT /v1/products/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v2/Products#addProduct" target="_blank">POST /v2/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v2/Products#updateProduct" target="_blank">PUT /v2/products/{id}</a></li>
      </ul>
      
      <p>They were also added to the responses of the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProducts" target="_blank">GET /v1/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProduct" target="_blank">GET /v1/products/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_blank">POST /v1/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_blank">PUT /v1/products/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProducts" target="_blank">GET /v2/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProduct" target="_blank">GET /v2/products/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_blank">POST /v2/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_blank">PATCH /v2/products/{id}</a></li>
      </ul>
      
      
      <h3>Deal Products</h3>
			<p>The new fields are:</p>  
      <ul>
        <li><i>billing_frequency</i> - How often a customer is billed for access to a service or product</li>
        <li><i>billing_frequency_cycles</i> - The number of times the billing frequency repeats for a product in a deal
</li>
        <li><i>billing_start_date</i> - When the product will start to be billed
</li>
      </ul>
      
      <p>These fields were added as body parameters to the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST /v1/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PUT /v1/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts" target="_blank">GET /v2/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST /v2/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PATCH  /v2/deals/{id}/products</a></li>
      </ul>
      
      <p>They were also added to the responses of the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts" target="_blank">GET /v1/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST /v1/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PUT /v1/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts" target="_blank">GET /v2/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_blank">POST /v2/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_blank">PATCH  /v2/deals/{id}/products</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsProducts" target="_blank">GET /v2/deals/products</a></li>
        
      </ul>

      <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>

		</div>
</div>


<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 09, 2024</span>
    </div>
    <div class="change-area">
      <p>We’re launching app onboarding/feature guide as well as app home page functionalities to further support app activation and engagement!
</p>
<br/>
<h2>What is being added?</h2>

<h3>1. App onboarding guide</h3>
      
<p>This feature enables app creators to add an onboarding guide that empowers users to familiarize themselves with a newly installed 
  app through an overview of its features or step-by-step instructions. This can help reduce the learning curve, maximize value extraction and foster adoption.
      </p>  

<p>You can now create the guide directly in the <A href="https://app.pipedrive.com/developer-hub"><b>Developer Hub</b></a> and break it it into individual segments using content blocks. 
  To make the guide more engaging, you can add a link to a tutorial video or add a link to an onboarding article.
      </p>  
      
<p><img alt="" loading="lazy" src="https://files.readme.io/9883b7e-Navigation.png" title="" align="center" class="" caption="" height="auto" width="auto"></p>

<p>Users will be prompted to view the guide upon installing the app and returning to Pipedrive. They can access the guide at any time from the
  <b>Apps dock</b> (“My apps” panel) or from the app home page under <b>Settings → Tools and apps → Marketplace apps</b>.
      </p>
      
<p><img alt="" loading="lazy" src="https://files.readme.io/bbd85d8-example_modal.png" title="" align="center" class="" caption="" height="auto" width="auto"></p>

<p>
  Read more about it in the <a href="https://pipedrive.readme.io/docs/marketplace-registering-the-app#onboarding-for-users">documentation</a>.
</p>

      <br/>

<h3>2. App home page</h3>
<p>
      This page serves as a central hub where users who have installed your app can find everything related to it, from general information to permissions, 
  an onboarding/feature guide, support information, <a href="https://pipedrive.readme.io/docs/custom-ui-extensions-app-settings">app settings</a>, 
  <a href="https://pipedrive.readme.io/docs/app-sharing-adding-apps-to-multiple-users">>app sharing management</a> and the option to uninstall it. 
  It’s accessible from the <b>Tools & Apps > Marketplace Apps</b> or the <b>Apps dock</b> (“My apps” panel) in the top menu bar.
  <a href="https://pipedrive.readme.io/docs/app-home-page">Learn more about it</a>.
</p>

<p><img alt="" loading="lazy" src="https://files.readme.io/a3c27c7-image.png" align="center" class="" width="100%" caption="" height="auto" title=""></p>

 <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>
      
		</div>
</div>
`}</HTMLBlock>

"We are launching app onboarding guide and app home page features to help with app activation and engagement."


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 09, 2024</span>
    </div>
    <div class="change-area">
      <p>We’re launching app onboarding/feature guide as well as app home page functionalities to further support app activation and engagement!
</p>
<br/>
<h2>What is being added?</h2>

<h3>1. App onboarding guide</h3>
      
<p>This feature enables app creators to add an onboarding guide that empowers users to familiarize themselves with a newly installed 
  app through an overview of its features or step-by-step instructions. This can help reduce the learning curve, maximize value extraction and foster adoption.
      </p>  

<p>You can now create the guide directly in the <A href="https://app.pipedrive.com/developer-hub"><b>Developer Hub</b></a> and break it it into individual segments using content blocks. 
  To make the guide more engaging, you can add a link to a tutorial video or add a link to an onboarding article.
      </p>  
      
<p><img alt="" loading="lazy" src="https://files.readme.io/9883b7e-Navigation.png" title="" align="center" class="" caption="" height="auto" width="auto"></p>

<p>Users will be prompted to view the guide upon installing the app and returning to Pipedrive. They can access the guide at any time from the
  <b>Apps dock</b> (“My apps” panel) or from the app home page under <b>Settings → Tools and apps → Marketplace apps</b>.
      </p>
      
<p><img alt="" loading="lazy" src="https://files.readme.io/bbd85d8-example_modal.png" title="" align="center" class="" caption="" height="auto" width="auto"></p>

<p>
  Read more about it in the <a href="https://pipedrive.readme.io/docs/marketplace-registering-the-app#onboarding-for-users">documentation</a>.
</p>

      <br/>

<h3>2. App home page</h3>
<p>
      This page serves as a central hub where users who have installed your app can find everything related to it, from general information to permissions, 
  an onboarding/feature guide, support information, <a href="https://pipedrive.readme.io/docs/custom-ui-extensions-app-settings">app settings</a>, 
  <a href="https://pipedrive.readme.io/docs/app-sharing-adding-apps-to-multiple-users">>app sharing management</a> and the option to uninstall it. 
  It’s accessible from the <b>Tools & Apps > Marketplace Apps</b> or the <b>Apps dock</b> (“My apps” panel) in the top menu bar.
  <a href="https://pipedrive.readme.io/docs/app-home-page">Learn more about it</a>.
</p>

<p><img alt="" loading="lazy" src="https://files.readme.io/a3c27c7-image.png" align="center" class="" width="100%" caption="" height="auto" title=""></p>

 <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>
      
		</div>
</div>


Introducing app onboarding guide and app home page

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">April 08, 2024</span>
    </div>
    <div class="change-area">
      <p>We’re introducing app-sharing functionality for apps. When enabled, it allows an admin user to add the app to other users within the same Pipedrive company. 
        Adding apps to users will significantly increase the number of app installations per company, possibly increasing your app's new users and reducing churn probability of your customers.</p>
<br/>
<p><b>What is being added?</b></p>
<p>The app-sharing feature can be enabled for most apps if they meet some essential criteria. 
  It allows admin users to initiate the sharing process by selecting a group of users within their company upon app installation. 
  Once shared, team members will receive notifications through multiple channels and will need to authorize the app to start using it.
  Read more about it in the <a href="https://pipedrive.readme.io/docs/app-sharing-adding-apps-to-multiple-users">documentation</a>.
</p>

    


<p><b>Why was it added?</b></p>
<p>
      In many companies, due to the lack of a centralized system for sharing information, admins often rely on communication channels like Slack or email to push an app or integration forward, which may result in lower adoption rates and data silos. Allowing admins to add apps to multiple users in one go saves time while encouraging app adoption.
      </p>
<p>
For users, seamless access to information about added apps from a trustworthy source, along with entry points that redirect them to the authorization page, reduces barriers to installation and boosts confidence in authorizing the app, resulting in a significantly streamlined process.
</p>
<p>
App creators benefit from increased app visibility, higher utilization of the app within a customer company, and ultimately, better business results.
</p>
      </p>

		</div>
</div>
`}</HTMLBlock>

<br />

We are announcing a new developer platform feature that allows you to enable app sharing for your app.


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">April 08, 2024</span>
    </div>
    <div class="change-area">
      <p>We’re introducing app-sharing functionality for apps. When enabled, it allows an admin user to add the app to other users within the same Pipedrive company. 
        Adding apps to users will significantly increase the number of app installations per company, possibly increasing your app's new users and reducing churn probability of your customers.</p>
<br/>
<p><b>What is being added?</b></p>
<p>The app-sharing feature can be enabled for most apps if they meet some essential criteria. 
  It allows admin users to initiate the sharing process by selecting a group of users within their company upon app installation. 
  Once shared, team members will receive notifications through multiple channels and will need to authorize the app to start using it.
  Read more about it in the <a href="https://pipedrive.readme.io/docs/app-sharing-adding-apps-to-multiple-users">documentation</a>.
</p>

    


<p><b>Why was it added?</b></p>
<p>
      In many companies, due to the lack of a centralized system for sharing information, admins often rely on communication channels like Slack or email to push an app or integration forward, which may result in lower adoption rates and data silos. Allowing admins to add apps to multiple users in one go saves time while encouraging app adoption.
      </p>
<p>
For users, seamless access to information about added apps from a trustworthy source, along with entry points that redirect them to the authorization page, reduces barriers to installation and boosts confidence in authorizing the app, resulting in a significantly streamlined process.
</p>
<p>
App creators benefit from increased app visibility, higher utilization of the app within a customer company, and ultimately, better business results.
</p>
      </p>

		</div>
</div>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog