<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label"><b>Effective from:</b></span><br>
        <span class="from-date"><b>May 9, 2019</b></span>
    </div>
     <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="adding-a-deal-bug-fix"></div>
        <div class="heading-text"><div id="adding-a-deal-bug-fix" class="heading-anchor_backwardsCompatibility">
          </div>Adding a deal bug fix</div>
        <a aria-label="Skip link to Adding a deal bug fix" class="heading-anchor-icon fa fa-anchor" 
           href="#adding-a-deal-bug-fix"></a></h3>
       
      
      <p>We identified an issue with <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Deals/post_deals">POST /deals</a></code> endpoint. It was possible to add <code>last_activity_date</code> and <code>next_activity_date</code>  fields when adding a deal.</p>

<p>This has been fixed, because these are values which will automatically be calculated based on the activities linked to the deal.</p>
      
<p>Please let us know if you have any questions by replying to the forum thread <a href="https://devcommunity.pipedrive.com/t/update-deal-details-using-api-not-working/1065/">here</a>.</p>

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

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label"><b>Effective from:</b></span><br>
        <span class="from-date"><b>May 9, 2019</b></span>
    </div>
     <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="adding-a-deal-bug-fix"></div>
        <div class="heading-text"><div id="adding-a-deal-bug-fix" class="heading-anchor_backwardsCompatibility">
          </div>Adding a deal bug fix</div>
        <a aria-label="Skip link to Adding a deal bug fix" class="heading-anchor-icon fa fa-anchor" 
           href="#adding-a-deal-bug-fix"></a></h3>
       
      
      <p>We identified an issue with <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Deals/post_deals">POST /deals</a></code> endpoint. It was possible to add <code>last_activity_date</code> and <code>next_activity_date</code>  fields when adding a deal.</p>

<p>This has been fixed, because these are values which will automatically be calculated based on the activities linked to the deal.</p>
      
<p>Please let us know if you have any questions by replying to the forum thread <a href="https://devcommunity.pipedrive.com/t/update-deal-details-using-api-not-working/1065/">here</a>.</p>

        <p class="published-on"><i>Published on May 17, 2019</i></p>
    </div>
</div>


Adding a Deal bug fix

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 7, 2019</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-limit-for-importing-emails-and-phone-numbers"></div>
        <div class="heading-text"><div id="new-limit-for-importing-emails-and-phone-numbers" class="heading-anchor_backwardsCompatibility">
          </div>New limit for importing emails and phone numbers</div>
        <a aria-label="Skip link to New limit for importing emails and phone numbers" class="heading-anchor-icon fa fa-anchor" 
           href="#new-limit-for-importing-emails-and-phone-numbers"></a></h3>
      
    
      <p><b>What will change?</b>
        <br>
The number of emails and phone numbers a user can add to a <b>“person” type object</b> will be limited to <b>150 records each</b>. A user can add a maximum of <b>150 emails</b> and a maximum of <b>150 phone numbers</b> per person.</p>

 <p>When a person object has reached 150 emails, their UI will no longer show the <b>“+ add more” button</b>. If a 3rd party developer sends more than 150 emails, they will receive an API error. This API error should help to prevent data loss for the customer.</p>
<br>
 <p><b>Why?</b>
   <br>
3rd party developers can unknowingly abuse the API - for example, adding thousands of emails and/or phone numbers into one person happens regularly a few times per month. They usually clean up after themselves, but this still adds a lot of real-time processing demands to our servers.</p>
<br>
 <p><b>Who is affected?</b>
   <br>
The most obvious will be companies who already have too many emails or phone numbers per person, as they will no longer be able to add any more emails or phone numbers to their “person” type objects.
      </p>

        <p class="published-on"><i>Published on May 7, 2019</i></p>
    </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 7, 2019</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-limit-for-importing-emails-and-phone-numbers"></div>
        <div class="heading-text"><div id="new-limit-for-importing-emails-and-phone-numbers" class="heading-anchor_backwardsCompatibility">
          </div>New limit for importing emails and phone numbers</div>
        <a aria-label="Skip link to New limit for importing emails and phone numbers" class="heading-anchor-icon fa fa-anchor" 
           href="#new-limit-for-importing-emails-and-phone-numbers"></a></h3>
      
    
      <p><b>What will change?</b>
        <br>
The number of emails and phone numbers a user can add to a <b>“person” type object</b> will be limited to <b>150 records each</b>. A user can add a maximum of <b>150 emails</b> and a maximum of <b>150 phone numbers</b> per person.</p>

 <p>When a person object has reached 150 emails, their UI will no longer show the <b>“+ add more” button</b>. If a 3rd party developer sends more than 150 emails, they will receive an API error. This API error should help to prevent data loss for the customer.</p>
<br>
 <p><b>Why?</b>
   <br>
3rd party developers can unknowingly abuse the API - for example, adding thousands of emails and/or phone numbers into one person happens regularly a few times per month. They usually clean up after themselves, but this still adds a lot of real-time processing demands to our servers.</p>
<br>
 <p><b>Who is affected?</b>
   <br>
The most obvious will be companies who already have too many emails or phone numbers per person, as they will no longer be able to add any more emails or phone numbers to their “person” type objects.
      </p>

        <p class="published-on"><i>Published on May 7, 2019</i></p>
    </div>
</div>


New limit for importing emails and phone numbers

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">April 22, 2019</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="related_objects-in-API-response-can-now-be-turned-off"></div>
        <div class="heading-text"><div id="related_objects-in-API-response-can-now-be-turned-off" class="heading-anchor_backwardsCompatibility">
          </div><code>related_objects</code> in API response can now be turned off</div>
        <a aria-label="Skip link to related_objects in API response can now be turned off" class="heading-anchor-icon fa fa-anchor" 
           href="#related_objects-in-API-response-can-now-be-turned-off"></a></h3>
      
    
      <p> We have added a new global <code>GET</code> parameter <code>related_objects=0</code> that will turn off <code>related_objects</code> in API response. We have added it to boost performance and improve response time for the data you really need.</p>

        <p class="published-on"><i>Published on April 22, 2019</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">April 22, 2019</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="related_objects-in-API-response-can-now-be-turned-off"></div>
        <div class="heading-text"><div id="related_objects-in-API-response-can-now-be-turned-off" class="heading-anchor_backwardsCompatibility">
          </div><code>related_objects</code> in API response can now be turned off</div>
        <a aria-label="Skip link to related_objects in API response can now be turned off" class="heading-anchor-icon fa fa-anchor" 
           href="#related_objects-in-API-response-can-now-be-turned-off"></a></h3>
      
    
      <p> We have added a new global <code>GET</code> parameter <code>related_objects=0</code> that will turn off <code>related_objects</code> in API response. We have added it to boost performance and improve response time for the data you really need.</p>

        <p class="published-on"><i>Published on April 22, 2019</i></p>
    </div>
</div>


<code>related_objects</code> in API response can now be turned off

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 9, 2019</span>
    </div>
   <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="removal-of-users-activities-endpoint"></div>
        <div class="heading-text"><div id="removal-of-users-activities-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Removal of the <code>/users/{id}/activities</code> endpoint of the Users resource</div>
        <a aria-label="Skip link to Removal of the /users/{id}/activities endpoint of the Users resource" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-users-activities-endpoint"></a></h3>
     
      <p> We will be <b>removing</b> the following endpoint from the<a href="https://developers.pipedrive.com/docs/api/v1/#!/Users" target="_self"> Users</a> resource:</p>

<ul>
<li><code>GET</code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Users/get_users_id_activities" target="_self">/users/{id}/activities</a>
</ul>
<br>

  <p> This endpoint was deprecated 1.5 years ago. In case you are still using the above-mentioned API endpoint in your code or 3rd party app/integration, please <b>remove</b> any dependency on this endpoint.</p>
<br>
<p>
  You have the option to replace it by using <code>GET</code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Activities/get_activities" target="_self">/activities</a> endpoint by passing the <code>user_id</code> parameter. You will get the same exact response with the addition of <code>related_objects</code> being <b>added</b> to the <b>output</b>.</p>
        <p class="published-on"><i>Published on April 9, 2019</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">May 9, 2019</span>
    </div>
   <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="removal-of-users-activities-endpoint"></div>
        <div class="heading-text"><div id="removal-of-users-activities-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Removal of the <code>/users/{id}/activities</code> endpoint of the Users resource</div>
        <a aria-label="Skip link to Removal of the /users/{id}/activities endpoint of the Users resource" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-users-activities-endpoint"></a></h3>
     
      <p> We will be <b>removing</b> the following endpoint from the<a href="https://developers.pipedrive.com/docs/api/v1/#!/Users" target="_self"> Users</a> resource:</p>

<ul>
<li><code>GET</code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Users/get_users_id_activities" target="_self">/users/{id}/activities</a>
</ul>
<br>

  <p> This endpoint was deprecated 1.5 years ago. In case you are still using the above-mentioned API endpoint in your code or 3rd party app/integration, please <b>remove</b> any dependency on this endpoint.</p>
<br>
<p>
  You have the option to replace it by using <code>GET</code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Activities/get_activities" target="_self">/activities</a> endpoint by passing the <code>user_id</code> parameter. You will get the same exact response with the addition of <code>related_objects</code> being <b>added</b> to the <b>output</b>.</p>
        <p class="published-on"><i>Published on April 9, 2019</i></p>
    </div>
</div>


Removal of the <code>/users/{id}/activities</code> endpoint of the Users resource

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">April 14, 2019</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-size-limit-for-notes"></div>
        <div class="heading-text"><div id="new-size-limit-for-notes" class="heading-anchor_backwardsCompatibility">
          </div>New size limit for notes</div>
        <a aria-label="Skip link to New size limit for notes" class="heading-anchor-icon fa fa-anchor" 
           href="#new-size-limit-for-notes"></a></h3>

 
        <p>We will be decreasing the size limit for notes. There will be no need to edit existing notes, but after <b>April 14th</b> it will not be possible to create notes larger than <b>3MB</b>.
<br></br>
We decided to decrease the note size to approximately <b>3,000,000 characters (or 3MB per note)</b> because large-sized notes reduce application memory and affect the performance negatively.
<br></br>
If your code or 3rd party app/integration has been designed to create or update notes, please doublecheck these as they may fail if the note being created or updated is too large.</p>
 
        <p class="published-on"><i>Published on March 19, 2019</i></p>
    </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">April 14, 2019</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-size-limit-for-notes"></div>
        <div class="heading-text"><div id="new-size-limit-for-notes" class="heading-anchor_backwardsCompatibility">
          </div>New size limit for notes</div>
        <a aria-label="Skip link to New size limit for notes" class="heading-anchor-icon fa fa-anchor" 
           href="#new-size-limit-for-notes"></a></h3>

 
        <p>We will be decreasing the size limit for notes. There will be no need to edit existing notes, but after <b>April 14th</b> it will not be possible to create notes larger than <b>3MB</b>.
<br></br>
We decided to decrease the note size to approximately <b>3,000,000 characters (or 3MB per note)</b> because large-sized notes reduce application memory and affect the performance negatively.
<br></br>
If your code or 3rd party app/integration has been designed to create or update notes, please doublecheck these as they may fail if the note being created or updated is too large.</p>
 
        <p class="published-on"><i>Published on March 19, 2019</i></p>
    </div>
</div>


New size limit for notes

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 2, 2019</span>
    </div>
<div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="removal-of-authorizations-endpoint"></div>
        <div class="heading-text"><div id="removal-of-authorizations-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Removal of the <code>/authorizations</code> endpoint</div>
        <a aria-label="Skip link to Removal of the /authorizations endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-authorizations-endpoint"></a></h3>
  
      <p> We will be <b>removing</b> <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Authorizations" target="_self"> the Authorizations</a></code> endpoint:</p>
       <ul><li>  <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Authorizations/post_authorizations"> POST /authorizations </a></code></li></ul>

  <p> We deprecated this endpoint on February 28, 2019, and we strongly advise you to avoid the use of this endpoint. The <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Authorizations/post_authorizations" target="_self">/authorizations</a></code> endpoint is a legacy way of authorization using generic API keys. Such an approach does not provide transparency into which applications have access to data nor the opportunity to control the permissions these integrations have. Therefore we suggest using <code><a href="https://pipedrive.readme.io/docs/marketplace-oauth-authorization" target="_self">OAuth Authorization</a></code> instead.
</br>
</br>
In case you are using the <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Authorizations/post_authorizations" target="_self">/authorizations</a></code> API endpoint in your code or 3rd party app/integration, <b>please remove any dependency on this endpoint as soon as possible.<b></p>
        <p class="published-on"><i>Published on February 28, 2019</i></p>
    </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 2, 2019</span>
    </div>
<div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="removal-of-authorizations-endpoint"></div>
        <div class="heading-text"><div id="removal-of-authorizations-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Removal of the <code>/authorizations</code> endpoint</div>
        <a aria-label="Skip link to Removal of the /authorizations endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-authorizations-endpoint"></a></h3>
  
      <p> We will be <b>removing</b> <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Authorizations" target="_self"> the Authorizations</a></code> endpoint:</p>
       <ul><li>  <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Authorizations/post_authorizations"> POST /authorizations </a></code></li></ul>

  <p> We deprecated this endpoint on February 28, 2019, and we strongly advise you to avoid the use of this endpoint. The <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Authorizations/post_authorizations" target="_self">/authorizations</a></code> endpoint is a legacy way of authorization using generic API keys. Such an approach does not provide transparency into which applications have access to data nor the opportunity to control the permissions these integrations have. Therefore we suggest using <code><a href="https://pipedrive.readme.io/docs/marketplace-oauth-authorization" target="_self">OAuth Authorization</a></code> instead.
</br>
</br>
In case you are using the <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Authorizations/post_authorizations" target="_self">/authorizations</a></code> API endpoint in your code or 3rd party app/integration, <b>please remove any dependency on this endpoint as soon as possible.<b></p>
        <p class="published-on"><i>Published on February 28, 2019</i></p>
    </div>
</div>


Removal of the <code>/authorizations</code> endpoint

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">February 11, 2019</span>
    </div>
  <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="removal-of-permissionsetassignments-endpoints-of-the-users-resource"></div>
        <div class="heading-text"><div id="removal-of-permissionsetassignments-endpoints-of-the-users-resource" class="heading-anchor_backwardsCompatibility">
          </div>Removal of <code>permissionSetAssignments</code> endpoints of the Users resource</div>
        <a aria-label="Skip link to Removal of permissionSetAssignments endpoints of the Users resource" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-permissionsetassignments-endpoints-of-the-users-resource"></a></h3>
   
 
   <p>We have <strong>removed</strong> the following endpoints of the <a href="https://developers.pipedrive.com/docs/api/v1/#!/Users" target="_self">Users</a> resource:</p>

<ul>
<li><code>GET</code>/users/{id}/permissionSetAssignments</li>
<li><code>POST</code>/users/{id}/permissionSetAssignments</li>
<li><code>DELETE</code>/users/{id}/permissionSetAssignments</li>
</ul>
            <br>
<p>In case you are using the above-mentioned API endpoints in your code or 3rd party app/integration, please remove any dependency on this endpoint.</p>
        <p class="published-on"><i>Published on February 11, 2019</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">February 11, 2019</span>
    </div>
  <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="removal-of-permissionsetassignments-endpoints-of-the-users-resource"></div>
        <div class="heading-text"><div id="removal-of-permissionsetassignments-endpoints-of-the-users-resource" class="heading-anchor_backwardsCompatibility">
          </div>Removal of <code>permissionSetAssignments</code> endpoints of the Users resource</div>
        <a aria-label="Skip link to Removal of permissionSetAssignments endpoints of the Users resource" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-permissionsetassignments-endpoints-of-the-users-resource"></a></h3>
   
 
   <p>We have <strong>removed</strong> the following endpoints of the <a href="https://developers.pipedrive.com/docs/api/v1/#!/Users" target="_self">Users</a> resource:</p>

<ul>
<li><code>GET</code>/users/{id}/permissionSetAssignments</li>
<li><code>POST</code>/users/{id}/permissionSetAssignments</li>
<li><code>DELETE</code>/users/{id}/permissionSetAssignments</li>
</ul>
            <br>
<p>In case you are using the above-mentioned API endpoints in your code or 3rd party app/integration, please remove any dependency on this endpoint.</p>
        <p class="published-on"><i>Published on February 11, 2019</i></p>
    </div>
</div>


Removal of <code>permissionSetAssignments</code> endpoints of the Users resource

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 30, 2019</span>
    </div>
   <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="Field-selector-in-requests-with-OAuth"></div>
        <div class="heading-text"><div id="Field-selector-in-requests-with-OAuth" class="heading-anchor_backwardsCompatibility">
          </div>Field selector in requests with OAuth</div>
        <a aria-label="Skip link to Field selector in requests with OAuth" class="heading-anchor-icon fa fa-anchor" 
           href="#Field-selector-in-requests-with-OAuth"></a></h3>
      
        <p>Field selector is now also supported in requests done with OAuth. Note that most endpoints in our API Reference support this, but not all. See examples of field selector usage <a href="https://pipedrive.readme.io/docs/core-api-concepts-requests#section-field-selector">here</a>.</p>
 
        <p class="published-on"><i>Published on January 30, 2019</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["Authorization"], "features": ["OAuth"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 30, 2019</span>
    </div>
   <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="Field-selector-in-requests-with-OAuth"></div>
        <div class="heading-text"><div id="Field-selector-in-requests-with-OAuth" class="heading-anchor_backwardsCompatibility">
          </div>Field selector in requests with OAuth</div>
        <a aria-label="Skip link to Field selector in requests with OAuth" class="heading-anchor-icon fa fa-anchor" 
           href="#Field-selector-in-requests-with-OAuth"></a></h3>
      
        <p>Field selector is now also supported in requests done with OAuth. Note that most endpoints in our API Reference support this, but not all. See examples of field selector usage <a href="https://pipedrive.readme.io/docs/core-api-concepts-requests#section-field-selector">here</a>.</p>
 
        <p class="published-on"><i>Published on January 30, 2019</i></p>
    </div>
</div>


Field selector in requests with OAuth

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 28, 2019</span>
    </div>
    <div class="change-area">
        <h3 class="heading heading-3 header-scroll" align="">
            <div class="heading-anchor anchor waypoint" id="New webhooks policy"></div>
            <div class="heading-text">
                <div id="New webhooks policy" class="heading-anchor_backwardsCompatibility"></div>
                New webhooks policy
            </div>
            <a aria-label="Skip link to New webhooks policy" class="heading-anchor-icon fa fa-anchor" href="#New webhooks policy"></a>
        </h3>
        
        <p>We are implementing a new webhooks usage policy in order to provide more stable and continuous deliveries, at a more reasonable rate. It will affect both general and App-Specific webhooks. Read more about it in <a href="https://pipedrive.readme.io/docs/guide-for-webhooks#webhooks-policy">Webhooks policy</a>.</p>

        <p class="published-on"><i>Published on January 22, 2019</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">January 28, 2019</span>
    </div>
    <div class="change-area">
        <h3 class="heading heading-3 header-scroll" align="">
            <div class="heading-anchor anchor waypoint" id="New webhooks policy"></div>
            <div class="heading-text">
                <div id="New webhooks policy" class="heading-anchor_backwardsCompatibility"></div>
                New webhooks policy
            </div>
            <a aria-label="Skip link to New webhooks policy" class="heading-anchor-icon fa fa-anchor" href="#New webhooks policy"></a>
        </h3>
        
        <p>We are implementing a new webhooks usage policy in order to provide more stable and continuous deliveries, at a more reasonable rate. It will affect both general and App-Specific webhooks. Read more about it in <a href="https://pipedrive.readme.io/docs/guide-for-webhooks#webhooks-policy">Webhooks policy</a>.</p>

        <p class="published-on"><i>Published on January 22, 2019</i></p>
    </div>
</div>


New webhooks policy

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 14, 2018</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="section-14-12-2018-more_items_in_collection-key-added-to-searchresults-response"></div>
        <div class="heading-text"><div id="section-14-12-2018-more_items_in_collection-key-added-to-searchresults-response" class="heading-anchor_backwardsCompatibility">
          </div><code>more_items_in_collection</code> key added to <code>/searchResults</code> response</div>
        <a aria-label="Skip link to more_items_in_collection key added to 
                       /searchResults response" class="heading-anchor-icon fa fa-anchor" 
           href="#section-14-12-2018-more_items_in_collection-key-added-to-searchresults-response"></a></h3>
      
 
        <p>The <code>more_items_in_collection</code> key was missing from the output of <a href="https://developers.pipedrive.com/docs/api/v1/#!/SearchResults/get_searchResults">/searchResults</a> endpoint, so we added it. 
Here is an example:</p>
      
    <div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar"><button type="button">JSON</button></div><div class="CodeTabs-inner"><pre><code class="rdmd-code lang-json theme-light" data-lang="json" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><div class="cm-s-neo"><span class="cm-string">"additional_data"</span>: {
    <span class="cm-property">"pagination"</span>: {
        <span class="cm-property">"start"</span>: <span class="cm-number">0</span>,
        <span class="cm-property">"next_start"</span>: <span class="cm-number">100</span>,
        <span class="cm-property">"more_in_provider"</span>: <span class="cm-atom">false</span>,
        <span class="cm-property">"more_items_in_collection"</span>: <span class="cm-atom">false</span>
    }
}
</div></code></pre></div></div>
 
      <p class="published-on"><i>Published on December 14, 2018</i></p>
    </div>
</div>
`}</HTMLBlock>

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

<code>more_items_in_collection</code> key added to /searchResults response


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 14, 2018</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="section-14-12-2018-more_items_in_collection-key-added-to-searchresults-response"></div>
        <div class="heading-text"><div id="section-14-12-2018-more_items_in_collection-key-added-to-searchresults-response" class="heading-anchor_backwardsCompatibility">
          </div><code>more_items_in_collection</code> key added to <code>/searchResults</code> response</div>
        <a aria-label="Skip link to more_items_in_collection key added to 
                       /searchResults response" class="heading-anchor-icon fa fa-anchor" 
           href="#section-14-12-2018-more_items_in_collection-key-added-to-searchresults-response"></a></h3>
      
 
        <p>The <code>more_items_in_collection</code> key was missing from the output of <a href="https://developers.pipedrive.com/docs/api/v1/#!/SearchResults/get_searchResults">/searchResults</a> endpoint, so we added it. 
Here is an example:</p>
      
    <div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar"><button type="button">JSON</button></div><div class="CodeTabs-inner"><pre><code class="rdmd-code lang-json theme-light" data-lang="json" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><div class="cm-s-neo"><span class="cm-string">"additional_data"</span>: {
    <span class="cm-property">"pagination"</span>: {
        <span class="cm-property">"start"</span>: <span class="cm-number">0</span>,
        <span class="cm-property">"next_start"</span>: <span class="cm-number">100</span>,
        <span class="cm-property">"more_in_provider"</span>: <span class="cm-atom">false</span>,
        <span class="cm-property">"more_items_in_collection"</span>: <span class="cm-atom">false</span>
    }
}
</div></code></pre></div></div>
 
      <p class="published-on"><i>Published on December 14, 2018</i></p>
    </div>
</div>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog