<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 6, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="get-/itemsearch-now-supports-returning-leads"></div>
        <div class="heading-text"><div id="get-/itemsearch-now-supports-returning-leads" class="heading-anchor_backwardsCompatibility">
          </div><code>GET/itemSearch</code> now supports returning Leads</div>
        <a aria-label="Skip link to GET/itemSearch now supports returning Leads" class="heading-anchor-icon fa fa-anchor" 
           href="#get-/itemsearch-now-supports-returning-leads"></a></h3>
      
      
        
      <p><b>What will change?</b></p>
       
<p><code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem">GET /itemSearch</a></code> now supports returning <b>Leads</b> in <code>related_items</code> for Organizations and Persons that are linked to it. When the <code>search_for_related_items</code>for <code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem">GET /itemSearch</a></code> is set to <code>true</code>, the response will include up to 100 newest related <b>Leads</b> in addition to up to a 100 <b>Deals</b> for each found Person and Organization.
   
</p>

  <p class="published-on"><i>Published on January 6, 2021</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["ItemSearch"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 6, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="get-/itemsearch-now-supports-returning-leads"></div>
        <div class="heading-text"><div id="get-/itemsearch-now-supports-returning-leads" class="heading-anchor_backwardsCompatibility">
          </div><code>GET/itemSearch</code> now supports returning Leads</div>
        <a aria-label="Skip link to GET/itemSearch now supports returning Leads" class="heading-anchor-icon fa fa-anchor" 
           href="#get-/itemsearch-now-supports-returning-leads"></a></h3>
      
      
        
      <p><b>What will change?</b></p>
       
<p><code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem">GET /itemSearch</a></code> now supports returning <b>Leads</b> in <code>related_items</code> for Organizations and Persons that are linked to it. When the <code>search_for_related_items</code>for <code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem">GET /itemSearch</a></code> is set to <code>true</code>, the response will include up to 100 newest related <b>Leads</b> in addition to up to a 100 <b>Deals</b> for each found Person and Organization.
   
</p>

  <p class="published-on"><i>Published on January 6, 2021</i></p>
    </div>
</div>


<code>GET/itemSearch</code> now supports returning Leads

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 4, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="breaking change in get /files endpoint"></div>
        <div class="heading-text"><div id="breaking change in get /files endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in <code>GET /files</code> endpoint</div>
        <a aria-label="Skip link to Breaking change in GET /fiels endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking change in get /files endpoint"></a></h3>
      
        
      <p><b>What will change?</b></p>
       
<p>We are going to change the definition of the sort parameter of <code><a href="https://developers.pipedrive.com/docs/api/v1/Files#getFiles">GET /files</a></code> endpoint. We’re going to allow sorting by 2 columns only (<code>id</code>, <code>update_time</code>) and restrict sorting by more than 1 column at the same time (e.g. <code>field_name_1</code> ASC, <code>field_name_2</code> DESC won’t work anymore).</p>
      <p><b>Why?</b></p>
<p>We are optimising our sorting operations together with moving to a new service for files management.</p>
      <p><b>Who is affected?</b></p>
      <p>Anyone doing queries to <code><a href="https://developers.pipedrive.com/docs/api/v1/Files#getFiles">GET /files</a></code> using sorting by <code>file_type</code>.</p>

  <p class="published-on"><i>Published on December 17, 2020</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Files"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 4, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="breaking change in get /files endpoint"></div>
        <div class="heading-text"><div id="breaking change in get /files endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in <code>GET /files</code> endpoint</div>
        <a aria-label="Skip link to Breaking change in GET /fiels endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking change in get /files endpoint"></a></h3>
      
        
      <p><b>What will change?</b></p>
       
<p>We are going to change the definition of the sort parameter of <code><a href="https://developers.pipedrive.com/docs/api/v1/Files#getFiles">GET /files</a></code> endpoint. We’re going to allow sorting by 2 columns only (<code>id</code>, <code>update_time</code>) and restrict sorting by more than 1 column at the same time (e.g. <code>field_name_1</code> ASC, <code>field_name_2</code> DESC won’t work anymore).</p>
      <p><b>Why?</b></p>
<p>We are optimising our sorting operations together with moving to a new service for files management.</p>
      <p><b>Who is affected?</b></p>
      <p>Anyone doing queries to <code><a href="https://developers.pipedrive.com/docs/api/v1/Files#getFiles">GET /files</a></code> using sorting by <code>file_type</code>.</p>

  <p class="published-on"><i>Published on December 17, 2020</i></p>
    </div>
</div>


Breaking change in <code>GET /files</code> endpoint

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 11, 2020</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="bug fix in date and datetime fields"></div>
        <div class="heading-text"><div id="bug fix in date and datetime fields" class="heading-anchor_backwardsCompatibility">
          </div>Bug fix in <code>date</code> and <code>datetime</code> fields</div>
        <a aria-label="Skip link to Bug fix in date and datetime fields" class="heading-anchor-icon fa fa-anchor" 
           href="#bug fix in date and datetime fields"></a></h3>

      <p>There was an issue with <code>date</code> and <code>datetime</code> fields, which affected Deals, Persons, Organizations, Products and Activities resources. When filtering by <code>date</code> and/or <code>datetime</code> with the operators <code><</code>, <code>></code>, <code><=</code>, <code>>=</code> it might have returned rows with an empty date (<code>0000-00-00</code>) and/or empty datetime (<code>0000-00-00 00:00:00</code>). We made the server response more strict, which means that now when filtering the same way the rows with empty date will always be excluded.</p>
        <p>The issue has now been fixed.</p>
<p>Please let us know if you have any questions by replying to the forum thread <a href="https://devcommunity.pipedrive.com/t/bug-fix-in-date-and-datetime-fields/3517">here</a>.</p>

  <p class="published-on"><i>Published on December 11, 2020</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Deals", "Persons", "Organizations", "Products", "Activities"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 11, 2020</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="bug fix in date and datetime fields"></div>
        <div class="heading-text"><div id="bug fix in date and datetime fields" class="heading-anchor_backwardsCompatibility">
          </div>Bug fix in <code>date</code> and <code>datetime</code> fields</div>
        <a aria-label="Skip link to Bug fix in date and datetime fields" class="heading-anchor-icon fa fa-anchor" 
           href="#bug fix in date and datetime fields"></a></h3>

      <p>There was an issue with <code>date</code> and <code>datetime</code> fields, which affected Deals, Persons, Organizations, Products and Activities resources. When filtering by <code>date</code> and/or <code>datetime</code> with the operators <code><</code>, <code>></code>, <code><=</code>, <code>>=</code> it might have returned rows with an empty date (<code>0000-00-00</code>) and/or empty datetime (<code>0000-00-00 00:00:00</code>). We made the server response more strict, which means that now when filtering the same way the rows with empty date will always be excluded.</p>
        <p>The issue has now been fixed.</p>
<p>Please let us know if you have any questions by replying to the forum thread <a href="https://devcommunity.pipedrive.com/t/bug-fix-in-date-and-datetime-fields/3517">here</a>.</p>

  <p class="published-on"><i>Published on December 11, 2020</i></p>
    </div>
</div>


Bug fix in <code>date</code> and <code>datetime</code> fields

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 28, 2020</span>
    </div>
    <div class="change-area">
        <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="removal of two endpoints from the /users resource"></div>
        <div class="heading-text"><div id="removal of two endpoints from the /users resource" class="heading-anchor_backwardsCompatibility">
          </div>Removal of two endpoints from the <code>/Users</code> resource</div>
        <a aria-label="Skip link to Removal of two endpoints from the /Users resource" class="heading-anchor-icon fa fa-anchor" 
           href="#removal of two endpoints from the /users resource"></a></h3>

      <p>We have now deprecated and will be removing the following two endpoints from the <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Users">Users</a></code> resource:</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserBlacklistedEmails">GET /users/{id}/blacklistedEmails</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#addUserBlacklistedEmail">POST /users/{id}/blacklistedEmails</a></code></li>
      </ul>
<p>In case you are still using the above-mentioned API endpoints in your code or 3rd party app/integration, please remove any dependency on these endpoints <b>by December 28, 2020</b>.</p>

  <p class="published-on"><i>Published on November 23, 2020</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Users"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 28, 2020</span>
    </div>
    <div class="change-area">
        <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="removal of two endpoints from the /users resource"></div>
        <div class="heading-text"><div id="removal of two endpoints from the /users resource" class="heading-anchor_backwardsCompatibility">
          </div>Removal of two endpoints from the <code>/Users</code> resource</div>
        <a aria-label="Skip link to Removal of two endpoints from the /Users resource" class="heading-anchor-icon fa fa-anchor" 
           href="#removal of two endpoints from the /users resource"></a></h3>

      <p>We have now deprecated and will be removing the following two endpoints from the <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Users">Users</a></code> resource:</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserBlacklistedEmails">GET /users/{id}/blacklistedEmails</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#addUserBlacklistedEmail">POST /users/{id}/blacklistedEmails</a></code></li>
      </ul>
<p>In case you are still using the above-mentioned API endpoints in your code or 3rd party app/integration, please remove any dependency on these endpoints <b>by December 28, 2020</b>.</p>

  <p class="published-on"><i>Published on November 23, 2020</i></p>
    </div>
</div>


Removal of two endpoints from the <code>/Users</code> resource

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 30, 2020</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="leads-oauth-scope"></div>
        <div class="heading-text"><div id="leads-oauth-scope" class="heading-anchor_backwardsCompatibility">
          </div>Leads OAuth scopes</div>
        <a aria-label="Skip link to Leads OAuth scopes" class="heading-anchor-icon fa fa-anchor" 
           href="#leads-oauth-scope"></a></h3>
      
         
      <p><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads" target="_self">Leads</a></code> endpoints have now been added to two new scopes which are available for OAuth apps.</p>

<p>You can find the endpoints of the <code><a href="https://developers.pipedrive.com/docs/api/v1/Leads" target="_self">Leads</a></code> resource under <code>leads:read</code> and <code>leads:full</code> scopes.</p>
      <p> Endpoints in <code>leads:full</code> scope: </p>
      <ul>
          <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead">POST /leads</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads">GET /leads</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLead">GET /leads/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead">PATCH /leads/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#deleteLead">DELETE /leads/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/LeadSources#getLeadSources">GET /leadSources</a></code></li>
           <li><code><a href="https://developers.pipedrive.com/docs/api/v1/LeadLabels#addLeadLabel">POST /leadLabels</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/LeadLabels#getLeadLabels">GET /leadLabels</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/LeadLabels#updateLeadLabel">PATCH /leadLabels/{id}</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/LeadLabels#deleteLeadLabel">DELETE /leadLabels/{id}</a></code></li>
      </ul>
       <p> Endpoints in <code>leads:read</code> scope: </p>
      <ul>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads">GET /leads</a></code></li>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLead">GET /leads/{id}</a></code></li>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/LeadSources#getLeadSources">GET /leadSources</a></code></li>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/LeadLabels#getLeadLabels">GET /leadLabels</a></code></li>
      </ul>
      
<p>You can read more about the scopes and permission explanations <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations">here</a>.</p> 
      <p>If you wish to update the scopes of an already approved or published app, be sure to <a href="https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app#changing-the-scopes">learn how changing the scopes will affect your app's existing users</a>.</p>
    	
      
       <p class="published-on"><i>Published on October 30, 2020</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["Authentication"], "features": ["Scopes"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 30, 2020</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="leads-oauth-scope"></div>
        <div class="heading-text"><div id="leads-oauth-scope" class="heading-anchor_backwardsCompatibility">
          </div>Leads OAuth scopes</div>
        <a aria-label="Skip link to Leads OAuth scopes" class="heading-anchor-icon fa fa-anchor" 
           href="#leads-oauth-scope"></a></h3>
      
         
      <p><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads" target="_self">Leads</a></code> endpoints have now been added to two new scopes which are available for OAuth apps.</p>

<p>You can find the endpoints of the <code><a href="https://developers.pipedrive.com/docs/api/v1/Leads" target="_self">Leads</a></code> resource under <code>leads:read</code> and <code>leads:full</code> scopes.</p>
      <p> Endpoints in <code>leads:full</code> scope: </p>
      <ul>
          <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead">POST /leads</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads">GET /leads</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLead">GET /leads/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead">PATCH /leads/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#deleteLead">DELETE /leads/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/LeadSources#getLeadSources">GET /leadSources</a></code></li>
           <li><code><a href="https://developers.pipedrive.com/docs/api/v1/LeadLabels#addLeadLabel">POST /leadLabels</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/LeadLabels#getLeadLabels">GET /leadLabels</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/LeadLabels#updateLeadLabel">PATCH /leadLabels/{id}</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/LeadLabels#deleteLeadLabel">DELETE /leadLabels/{id}</a></code></li>
      </ul>
       <p> Endpoints in <code>leads:read</code> scope: </p>
      <ul>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads">GET /leads</a></code></li>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLead">GET /leads/{id}</a></code></li>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/LeadSources#getLeadSources">GET /leadSources</a></code></li>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/LeadLabels#getLeadLabels">GET /leadLabels</a></code></li>
      </ul>
      
<p>You can read more about the scopes and permission explanations <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations">here</a>.</p> 
      <p>If you wish to update the scopes of an already approved or published app, be sure to <a href="https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app#changing-the-scopes">learn how changing the scopes will affect your app's existing users</a>.</p>
    	
      
       <p class="published-on"><i>Published on October 30, 2020</i></p>
    </div>
</div>


Leads OAuth scopes

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 30, 2020</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-logic-for-updating-scopes-on-existing-apps"></div>
        <div class="heading-text"><div id="new-logic-for-updating-scopes-on-existing-apps" class="heading-anchor_backwardsCompatibility">
          </div>New logic for updating scopes on existing apps</div>
        <a aria-label="Skip link to New logic for updating scopes on existing apps" class="heading-anchor-icon fa fa-anchor" 
           href="#new-logic-for-updating-scopes-on-existing-apps"></a></h3>
      
        
<p>Apps can now update their <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations">OAuth scopes</a> without automatically having the app uninstalled for all existing users.</p>
      <p><b>The process will now work as follows:</b></p>
      <p>Apps (<a href="https://pipedrive.readme.io/docs/marketplace-creating-a-proper-app#types-of-apps">draft/private, unlisted and public</a>) can update their scopes at any time.</p>
      
<p>When the scopes have been updated, existing users will receive a notification email letting them know of the change in scopes and asking them to reauthorize the app. </p>
      
      <p>Apps that decide to update their scopes must be able to clearly direct users to reauthorize the app in the Marketplace. This must be done to allow users to use the app in its full capacity. The scopes change will not halt the app's functionality - the features built with previous scopes will continue working. </p>
      
<p>From the Marketplace side, the app listing will remain available and won’t be sent back into <a href="https://pipedrive.readme.io/docs/marketplace-app-approval-process">the app approval process</a>. The scopes displayed in the installation screen of the app listing will be automatically updated to reflect the new scopes.</p>
      
 <p>The user has the option to either accept or deny all scopes. Because of this, it's a good idea to build apps that only request scopes that are absolutely necessary for your particular use-case. You can see the list of available OAuth scopes <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations">here</a>.</p>

	

 <p class="published-on"><i>Published on October 30, 2020</i></p>
    </div>
</div>
`}</HTMLBlock>


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 30, 2020</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-logic-for-updating-scopes-on-existing-apps"></div>
        <div class="heading-text"><div id="new-logic-for-updating-scopes-on-existing-apps" class="heading-anchor_backwardsCompatibility">
          </div>New logic for updating scopes on existing apps</div>
        <a aria-label="Skip link to New logic for updating scopes on existing apps" class="heading-anchor-icon fa fa-anchor" 
           href="#new-logic-for-updating-scopes-on-existing-apps"></a></h3>
      
        
<p>Apps can now update their <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations">OAuth scopes</a> without automatically having the app uninstalled for all existing users.</p>
      <p><b>The process will now work as follows:</b></p>
      <p>Apps (<a href="https://pipedrive.readme.io/docs/marketplace-creating-a-proper-app#types-of-apps">draft/private, unlisted and public</a>) can update their scopes at any time.</p>
      
<p>When the scopes have been updated, existing users will receive a notification email letting them know of the change in scopes and asking them to reauthorize the app. </p>
      
      <p>Apps that decide to update their scopes must be able to clearly direct users to reauthorize the app in the Marketplace. This must be done to allow users to use the app in its full capacity. The scopes change will not halt the app's functionality - the features built with previous scopes will continue working. </p>
      
<p>From the Marketplace side, the app listing will remain available and won’t be sent back into <a href="https://pipedrive.readme.io/docs/marketplace-app-approval-process">the app approval process</a>. The scopes displayed in the installation screen of the app listing will be automatically updated to reflect the new scopes.</p>
      
 <p>The user has the option to either accept or deny all scopes. Because of this, it's a good idea to build apps that only request scopes that are absolutely necessary for your particular use-case. You can see the list of available OAuth scopes <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations">here</a>.</p>

	

 <p class="published-on"><i>Published on October 30, 2020</i></p>
    </div>
</div>


New logic for updating scopes on existing apps

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 27, 2020</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="bug-fix-in-get-pipelines-endpoint"></div>
        <div class="heading-text"><div id="bug-fix-in-get-pipelines-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Bug fix in <code>GET /pipelines</code> endpoint</div>
        <a aria-label="Skip link to Bug fix in GET /pipelines endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#bug-fix-in-get-pipelines-endpoint"></a></h3>
      
        

      <p>There were two issues with <code><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelines">GET /pipelines</a></code> endpoint.
It ignored <code>start</code> and <code>limit</code> parameters when getting all pipelines, and in some cases for the <code>more_items_in_collection</code> field an incorrect value was returned (<code>true</code> instead of <code>false</code>).</p>
        
      <p>Both issues have now been fixed.</p>
<p>Please let us know if you have any questions by replying to the forum thread <a href="https://devcommunity.pipedrive.com/t/bug-fix-in-get-pipelines-endpoint/3386">here</a>.</p>

  <p class="published-on"><i>Published on October 27, 2020</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Pipelines"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 27, 2020</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="bug-fix-in-get-pipelines-endpoint"></div>
        <div class="heading-text"><div id="bug-fix-in-get-pipelines-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Bug fix in <code>GET /pipelines</code> endpoint</div>
        <a aria-label="Skip link to Bug fix in GET /pipelines endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#bug-fix-in-get-pipelines-endpoint"></a></h3>
      
        

      <p>There were two issues with <code><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelines">GET /pipelines</a></code> endpoint.
It ignored <code>start</code> and <code>limit</code> parameters when getting all pipelines, and in some cases for the <code>more_items_in_collection</code> field an incorrect value was returned (<code>true</code> instead of <code>false</code>).</p>
        
      <p>Both issues have now been fixed.</p>
<p>Please let us know if you have any questions by replying to the forum thread <a href="https://devcommunity.pipedrive.com/t/bug-fix-in-get-pipelines-endpoint/3386">here</a>.</p>

  <p class="published-on"><i>Published on October 27, 2020</i></p>
    </div>
</div>


Bug fix in <code>GET /pipelines</code> endpoint

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 20, 2020</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="closing-of-get-leadlabels-id-endpoint"></div>
        <div class="heading-text"><div id="closing-of-get-leadlabels-id-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Closing of <code>GET /leadLabels/:id</code> endpoint</div>
        <a aria-label="Skip link to Closing of GET /leadLabels/:id endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#closing-of-get-leadlabels-id-endpoint"></a></h3>
      

      <p>We are closing a non-functional <code>GET /leadLabels/:id</code> endpoint for fetching one Lead label at a time,  due to it not being fully implemented.
        </p>

  <p class="published-on"><i>Published on October 20, 2020</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["LeadLabels"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 20, 2020</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="closing-of-get-leadlabels-id-endpoint"></div>
        <div class="heading-text"><div id="closing-of-get-leadlabels-id-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Closing of <code>GET /leadLabels/:id</code> endpoint</div>
        <a aria-label="Skip link to Closing of GET /leadLabels/:id endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#closing-of-get-leadlabels-id-endpoint"></a></h3>
      

      <p>We are closing a non-functional <code>GET /leadLabels/:id</code> endpoint for fetching one Lead label at a time,  due to it not being fully implemented.
        </p>

  <p class="published-on"><i>Published on October 20, 2020</i></p>
    </div>
</div>


Closing of <code>GET /leadLabels/:id</code> endpoint

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 10, 2020</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="breaking-change-in-post-deals-and-put-deals-id-endpoints"></div>
        <div class="heading-text"><div id="breaking-change-in-post-deals-and-put-deals-id-endpoints" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in <code>POST /deals</code> and <code>PUT /deals/{id}</code> endpoints</div>
        <a aria-label="Skip link to Breaking change in POST /deals and PUT /deals/{id} endpoints" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-post-deals-and-put-deals-id-endpoints"></a></h3>
      
         
      <p><b>Endpoints directly affected:</b></p>
<ul>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_self">POST /deals</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_self">PUT /deals/{id}</a></code></li>
      </ul>
      <p><b>What will change?</b></p>
      <p>In Pipedrive, admin users can set visibility groups and permission sets. Visibility groups are used to categorize users and dictate what entity they will be allowed to see.  Permission sets dictate what actions the users in the account are able to perform. To see and set the visibility group of the entity through the API we have the <code>visible_to</code> parameter.
 </p>
      <p>If one tries to set the wrong <code>visible_to</code> value when requesting <code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization" target="_self">POST /organizations</a></code>, <code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#updateOrganization" target="_self">PUT /organizations/{id}</a></code>, <code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#addPerson" target="_self">POST /persons</a></code>  or <code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#updatePerson" target="_self">PUT /persons/{id}</a></code>  endpoints, they will get the <code>403</code> response code. We’re adding that same additional validation to <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_self">POST /deals</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_self">PUT /deals/{id}</a></code> endpoints.</p>
     <p><b>Why?</b></p>
     <p><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Deals/post_deals" target="_self">POST /deals</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_self">PUT /deals/{id}</a></code> endpoints don't currently return an error if an incorrect value is given to <code>visible_to</code> parameter, instead the request is shown to be successful and it will ignore the data sent by the user.
     <p><b>Who is affected?</b></p>
            <p>This change affects only <b>non-admin</b> type of users who belong to a permission set where the permission <b>Can change visibility of items</b> is turned <b>off</b>.</p>
      
      <p class="published-on"><i>Published on October 13, 2020</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Deals"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 10, 2020</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="breaking-change-in-post-deals-and-put-deals-id-endpoints"></div>
        <div class="heading-text"><div id="breaking-change-in-post-deals-and-put-deals-id-endpoints" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in <code>POST /deals</code> and <code>PUT /deals/{id}</code> endpoints</div>
        <a aria-label="Skip link to Breaking change in POST /deals and PUT /deals/{id} endpoints" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-post-deals-and-put-deals-id-endpoints"></a></h3>
      
         
      <p><b>Endpoints directly affected:</b></p>
<ul>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_self">POST /deals</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_self">PUT /deals/{id}</a></code></li>
      </ul>
      <p><b>What will change?</b></p>
      <p>In Pipedrive, admin users can set visibility groups and permission sets. Visibility groups are used to categorize users and dictate what entity they will be allowed to see.  Permission sets dictate what actions the users in the account are able to perform. To see and set the visibility group of the entity through the API we have the <code>visible_to</code> parameter.
 </p>
      <p>If one tries to set the wrong <code>visible_to</code> value when requesting <code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization" target="_self">POST /organizations</a></code>, <code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#updateOrganization" target="_self">PUT /organizations/{id}</a></code>, <code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#addPerson" target="_self">POST /persons</a></code>  or <code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#updatePerson" target="_self">PUT /persons/{id}</a></code>  endpoints, they will get the <code>403</code> response code. We’re adding that same additional validation to <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_self">POST /deals</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_self">PUT /deals/{id}</a></code> endpoints.</p>
     <p><b>Why?</b></p>
     <p><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Deals/post_deals" target="_self">POST /deals</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_self">PUT /deals/{id}</a></code> endpoints don't currently return an error if an incorrect value is given to <code>visible_to</code> parameter, instead the request is shown to be successful and it will ignore the data sent by the user.
     <p><b>Who is affected?</b></p>
            <p>This change affects only <b>non-admin</b> type of users who belong to a permission set where the permission <b>Can change visibility of items</b> is turned <b>off</b>.</p>
      
      <p class="published-on"><i>Published on October 13, 2020</i></p>
    </div>
</div>


Breaking change in <code>POST /deals</code> and <code>PUT /deals/{id}</code> endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 20, 2020</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="breaking-change-in-subscriptions-recurring-and-subscriptions-installment-endpoints"></div>
        <div class="heading-text"><div id="breaking-change-in-subscriptions-recurring-and-subscriptions-installment-endpoints" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in <code>/subscriptions/recurring</code> and <code>/subscriptions/installment</code> endpoints</div>
        <a aria-label="Skip link to Breaking change in /subscriptions/recurring and /subscriptions/installment endpoints<" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-subscriptions-recurring-and-subscriptions-installment-endpoints"></a></h3>
      
        
      <p><b>Endpoints directly affected:</b></p>
<ul>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#addRecurringSubscription" target="_self">POST /subscriptions/recurring</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#addSubscriptionInstallment" target="_self">POST /subscriptions/installment</a></code></li>
      </ul>
      <p><b>What will change?</b></p>
<p>Instead of allowing to specify any random 3 character string as currency, the service will start checking if the specified currency is a real currency or a custom currency used in a company. Also, the service will start returning the error <code>Unknown currency provided!</code> if the inserted currency is unknown.</p>
      <p>You can use <code><a href="https://developers.pipedrive.com/docs/api/v1/Currencies#getCurrencies" target="_self">GET /currencies</a></code> endpoint to see a list of currencies accepted by Pipedrive as well as custom currencies a company might have created.</p>
    
     <p><b>Why?</b></p>
      <p> Users are able to use the “incorrect” currencies as parameters and it may cause issues.</p>
     <p><b>Who is affected?</b></p>
      <p>Anyone with functionality built on top of the previous behaviour might need to alter their code.</p>

      
      <p class="published-on"><i>Published on October 6, 2020</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Subscriptions"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 20, 2020</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="breaking-change-in-subscriptions-recurring-and-subscriptions-installment-endpoints"></div>
        <div class="heading-text"><div id="breaking-change-in-subscriptions-recurring-and-subscriptions-installment-endpoints" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in <code>/subscriptions/recurring</code> and <code>/subscriptions/installment</code> endpoints</div>
        <a aria-label="Skip link to Breaking change in /subscriptions/recurring and /subscriptions/installment endpoints<" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-subscriptions-recurring-and-subscriptions-installment-endpoints"></a></h3>
      
        
      <p><b>Endpoints directly affected:</b></p>
<ul>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#addRecurringSubscription" target="_self">POST /subscriptions/recurring</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#addSubscriptionInstallment" target="_self">POST /subscriptions/installment</a></code></li>
      </ul>
      <p><b>What will change?</b></p>
<p>Instead of allowing to specify any random 3 character string as currency, the service will start checking if the specified currency is a real currency or a custom currency used in a company. Also, the service will start returning the error <code>Unknown currency provided!</code> if the inserted currency is unknown.</p>
      <p>You can use <code><a href="https://developers.pipedrive.com/docs/api/v1/Currencies#getCurrencies" target="_self">GET /currencies</a></code> endpoint to see a list of currencies accepted by Pipedrive as well as custom currencies a company might have created.</p>
    
     <p><b>Why?</b></p>
      <p> Users are able to use the “incorrect” currencies as parameters and it may cause issues.</p>
     <p><b>Who is affected?</b></p>
      <p>Anyone with functionality built on top of the previous behaviour might need to alter their code.</p>

      
      <p class="published-on"><i>Published on October 6, 2020</i></p>
    </div>
</div>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog