<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 22, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="new-field-for-webhooks"></div>
        <div class="heading-text"><div id="new-field-for-webhooks" class="heading-anchor_backwardsCompatibility">
          </div>New field for webhooks</div>
        <a aria-label="Skip link to New field for webhooks" class="heading-anchor-icon fa fa-anchor" 
           href="#new-field-for-webhooks"></a></h3>
      
        
      <p>We've publicly documented the <code>change_source</code> field for <a href="https://pipedrive.readme.io/docs/guide-for-webhooks">Webhooks</a>. This field allows you to see where the webhook has been triggered from.</p>
<p>Only the following 2 values are possible for this field:<br>
      <ul>
        <li><code>app</code> - the webhook is triggered from the Pipedrive web app </li>
        <li><code>api</code> - the webhook is triggered through the API</li>
      
      </ul>

      
          <br>
      <p class="published-on"><i>Published on June 22, 2021</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">June 22, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="new-field-for-webhooks"></div>
        <div class="heading-text"><div id="new-field-for-webhooks" class="heading-anchor_backwardsCompatibility">
          </div>New field for webhooks</div>
        <a aria-label="Skip link to New field for webhooks" class="heading-anchor-icon fa fa-anchor" 
           href="#new-field-for-webhooks"></a></h3>
      
        
      <p>We've publicly documented the <code>change_source</code> field for <a href="https://pipedrive.readme.io/docs/guide-for-webhooks">Webhooks</a>. This field allows you to see where the webhook has been triggered from.</p>
<p>Only the following 2 values are possible for this field:<br>
      <ul>
        <li><code>app</code> - the webhook is triggered from the Pipedrive web app </li>
        <li><code>api</code> - the webhook is triggered through the API</li>
      
      </ul>

      
          <br>
      <p class="published-on"><i>Published on June 22, 2021</i></p>
  </div>
</div>


New field for Webhooks

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 3, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="new-field-in-the-api-response-of-the-related-objects-object"></div>
        <div class="heading-text"><div id="new-field-in-the-api-response-of-the-related-objects-object" class="heading-anchor_backwardsCompatibility">
          </div>New field in the API response of the <code>related_objects</code> object</div>
        <a aria-label="Skip link to New field in the API response of the related_objects object" class="heading-anchor-icon fa fa-anchor" 
           href="#new-field-in-the-api-response-of-the-related-objects-object"></a></h3>
      
        
      <p><b>What is going to change?</b></p>
      
      <p> We have added a new field <code>owner_id</code> to the <code>person</code> object of the <code>related_objects</code> in the API response. This field shows the owner ID of the user who owns the Person record. The value of the field is always an integer.
      <p>Here’s the code example of the new response in JSON:</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-property">"data"</span>: [<span class="cm-meta">...</span>],
  <span class="cm-string">"additional_data"</span>: {<span class="cm-meta">...</span>},
  <span class="cm-string">"related_objects"</span>: {
    <span class="cm-property">"person"</span>: {
      <span class="cm-property">"1"</span>: {
        <span class="cm-property">"id"</span>: <span class="cm-number">1</span>,
        <span class="cm-property">"name"</span>: <span class="cm-string">"person name"</span>,
        <span class="cm-property">"active_flag"</span>: <span class="cm-atom">true</span>,
        <span class="cm-property">"email"</span>: [
          {
            <span class="cm-property">"label"</span>: <span class="cm-string">"work"</span>,
            <span class="cm-property">"value"</span>: <span class="cm-string">"person@gmail.com"</span>,
            <span class="cm-property">"primary"</span>: <span class="cm-atom">true</span>
          }
        ],
        <span class="cm-property">"phone"</span>: [
          {
            <span class="cm-property">"label"</span>: <span class="cm-string">"work"</span>,
            <span class="cm-property">"value"</span>: <span class="cm-string">"5555555"</span>,
            <span class="cm-property">"primary"</span>: <span class="cm-atom">true</span>
          }
        ],
        <span class="cm-property">"owner_id"</span>: <span class="cm-number">1111111</span>
      }
    }
  }
}
}
</div></code></pre></div></div>
      <p><b>Why is it added?</b></p>
      <p>In addition to fixing a bug in our web app, this update will also bring more consistency to our API as the field <code>owner_id</code> is currently present only in the <code>organization</code> object of the <code>related_objects</code>.
</p>
       <p><b>Who is affected?</b></p>
      <p>Users who are referring to the <code>person</code> object of the <code>related_objects</code> in webhooks and when using the following 15 API endpoints:</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#getActivities" target="_self">GET /v1/activities</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#getActivity" target="_self">GET /v1/activities/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#addActivity" target="_self">POST /v1/activities</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#updateActivity" target="_self">PUT /v1/activities/{id} </a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals" target="_self">GET /v1/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeal" target="_self">GET /v1/deals/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealActivities" target="_self">GET /v1/deals/{id}/activities</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealUpdates" target="_self">GET /v1/deals/{id}/flow</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealParticipants" target="_self">GET /v1/deals/{id}/participants</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_self">POST /v1/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealParticipant" target="_self">POST /v1/deals/{id}/participants</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_self">PUT /v1/deals/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationDeals" target="_self">GET /v1/organizations/{id}/deals </a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonDeals" target="_self">GET /v1/persons/{id}/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonUpdates" target="_self">GET /v1/persons/{id}/flow
 </a></code></li>
      </ul>
        

      

          <br>
      <p class="published-on"><i>Published on June 3, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 3, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="new-field-in-the-api-response-of-the-related-objects-object"></div>
        <div class="heading-text"><div id="new-field-in-the-api-response-of-the-related-objects-object" class="heading-anchor_backwardsCompatibility">
          </div>New field in the API response of the <code>related_objects</code> object</div>
        <a aria-label="Skip link to New field in the API response of the related_objects object" class="heading-anchor-icon fa fa-anchor" 
           href="#new-field-in-the-api-response-of-the-related-objects-object"></a></h3>
      
        
      <p><b>What is going to change?</b></p>
      
      <p> We have added a new field <code>owner_id</code> to the <code>person</code> object of the <code>related_objects</code> in the API response. This field shows the owner ID of the user who owns the Person record. The value of the field is always an integer.
      <p>Here’s the code example of the new response in JSON:</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-property">"data"</span>: [<span class="cm-meta">...</span>],
  <span class="cm-string">"additional_data"</span>: {<span class="cm-meta">...</span>},
  <span class="cm-string">"related_objects"</span>: {
    <span class="cm-property">"person"</span>: {
      <span class="cm-property">"1"</span>: {
        <span class="cm-property">"id"</span>: <span class="cm-number">1</span>,
        <span class="cm-property">"name"</span>: <span class="cm-string">"person name"</span>,
        <span class="cm-property">"active_flag"</span>: <span class="cm-atom">true</span>,
        <span class="cm-property">"email"</span>: [
          {
            <span class="cm-property">"label"</span>: <span class="cm-string">"work"</span>,
            <span class="cm-property">"value"</span>: <span class="cm-string">"person@gmail.com"</span>,
            <span class="cm-property">"primary"</span>: <span class="cm-atom">true</span>
          }
        ],
        <span class="cm-property">"phone"</span>: [
          {
            <span class="cm-property">"label"</span>: <span class="cm-string">"work"</span>,
            <span class="cm-property">"value"</span>: <span class="cm-string">"5555555"</span>,
            <span class="cm-property">"primary"</span>: <span class="cm-atom">true</span>
          }
        ],
        <span class="cm-property">"owner_id"</span>: <span class="cm-number">1111111</span>
      }
    }
  }
}
}
</div></code></pre></div></div>
      <p><b>Why is it added?</b></p>
      <p>In addition to fixing a bug in our web app, this update will also bring more consistency to our API as the field <code>owner_id</code> is currently present only in the <code>organization</code> object of the <code>related_objects</code>.
</p>
       <p><b>Who is affected?</b></p>
      <p>Users who are referring to the <code>person</code> object of the <code>related_objects</code> in webhooks and when using the following 15 API endpoints:</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#getActivities" target="_self">GET /v1/activities</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#getActivity" target="_self">GET /v1/activities/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#addActivity" target="_self">POST /v1/activities</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#updateActivity" target="_self">PUT /v1/activities/{id} </a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals" target="_self">GET /v1/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeal" target="_self">GET /v1/deals/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealActivities" target="_self">GET /v1/deals/{id}/activities</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealUpdates" target="_self">GET /v1/deals/{id}/flow</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealParticipants" target="_self">GET /v1/deals/{id}/participants</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_self">POST /v1/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealParticipant" target="_self">POST /v1/deals/{id}/participants</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_self">PUT /v1/deals/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationDeals" target="_self">GET /v1/organizations/{id}/deals </a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonDeals" target="_self">GET /v1/persons/{id}/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonUpdates" target="_self">GET /v1/persons/{id}/flow
 </a></code></li>
      </ul>
        

      

          <br>
      <p class="published-on"><i>Published on June 3, 2021</i></p>
  </div>
</div>


New field in the API response of the <code>related_objects</code> object

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 3, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="new-field-lead-default-visibility-in-the-roles-api"></div>
        <div class="heading-text"><div id="new-field-lead-default-visibility-in-the-roles-api" class="heading-anchor_backwardsCompatibility">
          </div>           New field <code>lead_default_visibility</code> in the Roles API</div>
        <a aria-label="Skip link to New field lead_default_visibility in the Roles API" class="heading-anchor-icon fa fa-anchor" 
           href="#new-field-lead-default-visibility-in-the-roles-api"></a></h3>
      
         
      <p>Users already had control over the default visibility for other entities (Organizations, People, Deals and Products). Now, the Users can also define the default visibility for their <b>leads</b>. </p>
      <p><b>What has been added to the Roles API?</b></p>
      <p>In order for our Users to be able to define the default visibility for their leads also via the API, we have extended the responses of three Roles’ endpoints.</p>
      <p>The possible values for the <code>lead_default_visibility</code> field depend on the plan the company using the Roles API is on:</p>
       <p>Essential / Advanced plan:</p>
      <ul>
        <li><code>1</code> (Owner & followers)</li>
        <li><code>3</code> (Entire company)</li>
      </ul>
      
      <p>Professional / Enterprise plan:</p>
      <ul>
        <li><code>1</code> (Owner & followers)</li>
        <li><code>3</code> (Owners visibility group)</li>
        <li><code>5</code> (Owners visibility group and below)
</li>
        <li><code>7</code> (Entire company)</li>
      </ul>
       <br>
      <p><b>Which Roles API endpoints are affected?</b></p>
     
       <p>1. <code><a href="https://developers.pipedrive.com/docs/api/v1/Roles#getRoleSettings" target="_self">GET /v1/roles/{id}/settings</a></code> - we updated the response to include <code>lead_default_visibility</code>, so now this endpoint will <b>always</b> return:</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-property">"success"</span>: <span class="cm-atom">true</span>,
 <span class="cm-property">"data"</span>: {
  (<span class="cm-meta">...</span>)
  <span class="cm-string">"lead_default_visibility"</span>: <span class="cm-number">1</span>
 }
}
</div></code></pre></div></div>
      
         <p>2. <code><a href="https://developers.pipedrive.com/docs/api/v1/Roles#addOrUpdateRoleSetting" target="_self">POST /v1/roles/{id}/settings</a></code> - the request <b>can</b> include and return the field <code>lead_default_visibility</code> in the body (if updating the lead visibility)</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-property">"success"</span>: <span class="cm-atom">true</span>,
 <span class="cm-property">"data"</span>: {
  <span class="cm-property">"id"</span>: <span class="cm-number">2</span>,
  <span class="cm-property">"lead_default_visibility"</span>: <span class="cm-number">1</span>
 }
}
</div></code></pre></div></div>
      
         <p>3. <code><a href="https://developers.pipedrive.com/docs/api/v1/Roles#getRole" target="_self">GET /v1/roles/{id}</a></code> - we updated the response to include <code>lead_default_visibility</code>, so now this endpoint will <b>always</b> return</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-property">"success"</span>: <span class="cm-atom">true</span>,
 <span class="cm-property">"data"</span>: { <span class="cm-meta">...</span> },
 <span class="cm-property">"additional_data"</span>: {
  <span class="cm-property">"settings"</span>: {
   (<span class="cm-meta">...</span>)
   <span class="cm-string">"lead_default_visibility"</span>: <span class="cm-number">1</span>
  }
 }
}
</div></code></pre></div></div>
      
      
          <br>
      <p class="published-on"><i>Published on June 3, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 3, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="new-field-lead-default-visibility-in-the-roles-api"></div>
        <div class="heading-text"><div id="new-field-lead-default-visibility-in-the-roles-api" class="heading-anchor_backwardsCompatibility">
          </div>           New field <code>lead_default_visibility</code> in the Roles API</div>
        <a aria-label="Skip link to New field lead_default_visibility in the Roles API" class="heading-anchor-icon fa fa-anchor" 
           href="#new-field-lead-default-visibility-in-the-roles-api"></a></h3>
      
         
      <p>Users already had control over the default visibility for other entities (Organizations, People, Deals and Products). Now, the Users can also define the default visibility for their <b>leads</b>. </p>
      <p><b>What has been added to the Roles API?</b></p>
      <p>In order for our Users to be able to define the default visibility for their leads also via the API, we have extended the responses of three Roles’ endpoints.</p>
      <p>The possible values for the <code>lead_default_visibility</code> field depend on the plan the company using the Roles API is on:</p>
       <p>Essential / Advanced plan:</p>
      <ul>
        <li><code>1</code> (Owner & followers)</li>
        <li><code>3</code> (Entire company)</li>
      </ul>
      
      <p>Professional / Enterprise plan:</p>
      <ul>
        <li><code>1</code> (Owner & followers)</li>
        <li><code>3</code> (Owners visibility group)</li>
        <li><code>5</code> (Owners visibility group and below)
</li>
        <li><code>7</code> (Entire company)</li>
      </ul>
       <br>
      <p><b>Which Roles API endpoints are affected?</b></p>
     
       <p>1. <code><a href="https://developers.pipedrive.com/docs/api/v1/Roles#getRoleSettings" target="_self">GET /v1/roles/{id}/settings</a></code> - we updated the response to include <code>lead_default_visibility</code>, so now this endpoint will <b>always</b> return:</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-property">"success"</span>: <span class="cm-atom">true</span>,
 <span class="cm-property">"data"</span>: {
  (<span class="cm-meta">...</span>)
  <span class="cm-string">"lead_default_visibility"</span>: <span class="cm-number">1</span>
 }
}
</div></code></pre></div></div>
      
         <p>2. <code><a href="https://developers.pipedrive.com/docs/api/v1/Roles#addOrUpdateRoleSetting" target="_self">POST /v1/roles/{id}/settings</a></code> - the request <b>can</b> include and return the field <code>lead_default_visibility</code> in the body (if updating the lead visibility)</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-property">"success"</span>: <span class="cm-atom">true</span>,
 <span class="cm-property">"data"</span>: {
  <span class="cm-property">"id"</span>: <span class="cm-number">2</span>,
  <span class="cm-property">"lead_default_visibility"</span>: <span class="cm-number">1</span>
 }
}
</div></code></pre></div></div>
      
         <p>3. <code><a href="https://developers.pipedrive.com/docs/api/v1/Roles#getRole" target="_self">GET /v1/roles/{id}</a></code> - we updated the response to include <code>lead_default_visibility</code>, so now this endpoint will <b>always</b> return</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-property">"success"</span>: <span class="cm-atom">true</span>,
 <span class="cm-property">"data"</span>: { <span class="cm-meta">...</span> },
 <span class="cm-property">"additional_data"</span>: {
  <span class="cm-property">"settings"</span>: {
   (<span class="cm-meta">...</span>)
   <span class="cm-string">"lead_default_visibility"</span>: <span class="cm-number">1</span>
  }
 }
}
</div></code></pre></div></div>
      
      
          <br>
      <p class="published-on"><i>Published on June 3, 2021</i></p>
  </div>
</div>


New field <code>lead_default_visibility</code> in the Roles API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 26, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="reassessment-of-the-limitation-of-custom-fields-options"></div>
        <div class="heading-text"><div id="reassessment-of-the-limitation-of-custom-fields-options" class="heading-anchor_backwardsCompatibility">
          </div>           Reassessment of the limitation of custom fields options</div>
        <a aria-label="Skip link to Reassessment of the limitation of custom fields options" class="heading-anchor-icon fa fa-anchor" 
           href="#reassessment-of-the-limitation-of-custom-fields-options"></a></h3>

      <p>Regarding <a href="https://pipedrive.readme.io/docs/changelog#limitation-of-custom-fields-options" target="_self">the recent limitation for 2 custom field type's options</a>, after further user testing, our product team has risen the limit of <b>options single option and multiple options custom fields</b> can have to <b>10,000 options per custom field</b>. When the limit of 10,000 options has been reached the following error message will be displayed: 
<code>"You reached the limit of 10000 options per field. Remove some options to be able to save."</code>
</p>


          <br>
      <p class="published-on"><i>Published on May 26, 2021</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">May 26, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="reassessment-of-the-limitation-of-custom-fields-options"></div>
        <div class="heading-text"><div id="reassessment-of-the-limitation-of-custom-fields-options" class="heading-anchor_backwardsCompatibility">
          </div>           Reassessment of the limitation of custom fields options</div>
        <a aria-label="Skip link to Reassessment of the limitation of custom fields options" class="heading-anchor-icon fa fa-anchor" 
           href="#reassessment-of-the-limitation-of-custom-fields-options"></a></h3>

      <p>Regarding <a href="/changelog/post/limitation-of-custom-fields-options" target="_self">the recent limitation for 2 custom field type's options</a>, after further user testing, our product team has risen the limit of <b>options single option and multiple options custom fields</b> can have to <b>10,000 options per custom field</b>. When the limit of 10,000 options has been reached the following error message will be displayed: 
<code>"You reached the limit of 10000 options per field. Remove some options to be able to save."</code>
</p>


          <br>
      <p class="published-on"><i>Published on May 26, 2021</i></p>
  </div>
</div>


Reassessment of the limitation of custom fields options

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 19, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="new-field-in-get/deals/summary-endpoint-response"></div>
        <div class="heading-text"><div id="new-field-in-get/deals/summary-endpoint-response" class="heading-anchor_backwardsCompatibility">
          </div>           New fields in <code>GET /deals/summary</code> endpoint response</div>
        <a aria-label="Skip link to New fields in GET /deals/summary endpoint response" class="heading-anchor-icon fa fa-anchor" 
           href="#new-field-in-get/deals/summary-endpoint-response"></a></h3>

        
      <p>We have added two new fields to the <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsSummary" target="_self">GET /deals/summary</a></code> endpoint response:</p>
  
      <ul>
        <li><code>is_custom_currency</code> - a boolean showing whether the currency is considered custom </li>
        <li><code>total_custom_currency_count</code> - an integer showing the total count of currencies for which <code>is_custom_currency</code> is <code>true</code></li>
      
      </ul>

      
          <br>
      <p class="published-on"><i>Published on May 19, 2021</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">May 19, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="new-field-in-get/deals/summary-endpoint-response"></div>
        <div class="heading-text"><div id="new-field-in-get/deals/summary-endpoint-response" class="heading-anchor_backwardsCompatibility">
          </div>           New fields in <code>GET /deals/summary</code> endpoint response</div>
        <a aria-label="Skip link to New fields in GET /deals/summary endpoint response" class="heading-anchor-icon fa fa-anchor" 
           href="#new-field-in-get/deals/summary-endpoint-response"></a></h3>

        
      <p>We have added two new fields to the <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsSummary" target="_self">GET /deals/summary</a></code> endpoint response:</p>
  
      <ul>
        <li><code>is_custom_currency</code> - a boolean showing whether the currency is considered custom </li>
        <li><code>total_custom_currency_count</code> - an integer showing the total count of currencies for which <code>is_custom_currency</code> is <code>true</code></li>
      
      </ul>

      
          <br>
      <p class="published-on"><i>Published on May 19, 2021</i></p>
  </div>
</div>


New fields in <code>GET /deals/summary</code> endpoint response

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 12, 2021</span>
    </div>
    <div class="change-area">
        <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="limitation-of-custom-fields-options"></div>
        <div class="heading-text"><div id="limitation-of-custom-fields-options" class="heading-anchor_backwardsCompatibility">
          </div> Limitation of custom field's options          </div>
        <a aria-label="Skip link to Limitation of custom field's options" class="heading-anchor-icon fa fa-anchor" 
           href="#limitation-of-custom-fields-options"></a></h3>

	<p><strong>UPDATE (May 26, 2021)</strong>: After further testing, our team has decided to increase the limit of possible options per field to 10,000. See <a href="https://pipedrive.readme.io/docs/changelog#reassessment-of-the-limitation-of-custom-fields-options" target="_self">the announcement</a> for more.</p>

      <p> Starting from May 12, 2021, we will be limiting the amount of <b>options</b> <a href="https://pipedrive.readme.io/docs/core-api-concepts-custom-fields" target="_self">custom fields</a> with type 
        <b>“Multiple option”</b> and <b>“Single option”</b> can have. The limit will be <b>500 options</b> per custom field.</p>

<p>When the amount of options per custom field is reached, an error message will be displayed in the API response. 
  The error message will be as follows: </p>


<p><code>"You reached the limit of 500 options per field. Remove some options to be able to save."</code></p>

<p>In case there is a need for more options to be added to a custom field, the user will have to delete some existing options from that field to fit into the limit.</p>

<p>Nothing will break for the users who already have created more than 500 options for their custom fields, but if they decide to add more options they would need to remove all the extra options which exceed the 500 limit.</p>

      
      <br>
      <p class="published-on"><i>Published on May 12, 2021</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">May 12, 2021</span>
    </div>
    <div class="change-area">
        <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="limitation-of-custom-fields-options"></div>
        <div class="heading-text"><div id="limitation-of-custom-fields-options" class="heading-anchor_backwardsCompatibility">
          </div> Limitation of custom field's options          </div>
        <a aria-label="Skip link to Limitation of custom field's options" class="heading-anchor-icon fa fa-anchor" 
           href="#limitation-of-custom-fields-options"></a></h3>

	<p><strong>UPDATE (May 26, 2021)</strong>: After further testing, our team has decided to increase the limit of possible options per field to 10,000. See <a href="/changelog/post/reassessment-of-the-limitation-of-custom-fields-options" target="_self">the announcement</a> for more.</p>

      <p> Starting from May 12, 2021, we will be limiting the amount of <b>options</b> <a href="https://pipedrive.readme.io/docs/core-api-concepts-custom-fields" target="_self">custom fields</a> with type 
        <b>“Multiple option”</b> and <b>“Single option”</b> can have. The limit will be <b>500 options</b> per custom field.</p>

<p>When the amount of options per custom field is reached, an error message will be displayed in the API response. 
  The error message will be as follows: </p>


<p><code>"You reached the limit of 500 options per field. Remove some options to be able to save."</code></p>

<p>In case there is a need for more options to be added to a custom field, the user will have to delete some existing options from that field to fit into the limit.</p>

<p>Nothing will break for the users who already have created more than 500 options for their custom fields, but if they decide to add more options they would need to remove all the extra options which exceed the 500 limit.</p>

      
      <br>
      <p class="published-on"><i>Published on May 12, 2021</i></p>
  </div>
</div>


Limitation of custom field's options

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 7, 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-leads-api-response"></div>
        <div class="heading-text"><div id="breaking-change-in-leads-api-response" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in Leads API response</div>
        <a aria-label="Skip link to Breaking change in Leads API response" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-leads-api-response"></a></h3>
      
        
      <p>In the <code>source_name</code> format of the Leads response object, the empty string of <code>""</code> will become <code>"Manually created"</code> for these four endpoints:</p>
    
      <ul>
        <li><code>
            <a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads" target"_self">GET /leads</a>
          </code></li>
         <li><code>
            <a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLead" target"_self">GET /lead/{id}</a>
          </code></li>
         <li><code>
            <a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead" target"_self">POST /leads</a>
          </code></li>
         <li><code>
            <a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead" target"_self">PATCH /leads/{id}</a>
          </code></li>
      
      </ul>
<p>Due to this change, one more item will be added to the <code>
            <a href="https://developers.pipedrive.com/docs/api/v1/LeadSources#getLeadSources" target"_self">GET /leadSources</a></code> response: 
  <code>{name: "Manually created"}</code> .
The additional response item essentially is <b>not</b> a breaking change, but you might want to look into this in case your code checks the responses in a more strict way.</p>

      <p><b>What is going to change?</b></p>

<p> Until now, it was not possible to filter manually created leads specifically, 
  because the <code>source_name</code> was an empty string. After adding an actual value to the 
  <code>source_name</code>, it will be possible to filter manually created leads using this value.</p>

      <p><b>Who is affected?</b></p>

<p>Anyone with functionality built on top of the previous behavior will need to alter their code.
</p>
          <br>
      <p class="published-on"><i>Published on May 6, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 7, 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-leads-api-response"></div>
        <div class="heading-text"><div id="breaking-change-in-leads-api-response" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in Leads API response</div>
        <a aria-label="Skip link to Breaking change in Leads API response" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-leads-api-response"></a></h3>
      
        
      <p>In the <code>source_name</code> format of the Leads response object, the empty string of <code>""</code> will become <code>"Manually created"</code> for these four endpoints:</p>
    
      <ul>
        <li><code>
            <a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads" target"_self">GET /leads</a>
          </code></li>
         <li><code>
            <a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLead" target"_self">GET /lead/{id}</a>
          </code></li>
         <li><code>
            <a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead" target"_self">POST /leads</a>
          </code></li>
         <li><code>
            <a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead" target"_self">PATCH /leads/{id}</a>
          </code></li>
      
      </ul>
<p>Due to this change, one more item will be added to the <code>
            <a href="https://developers.pipedrive.com/docs/api/v1/LeadSources#getLeadSources" target"_self">GET /leadSources</a></code> response: 
  <code>{name: "Manually created"}</code> .
The additional response item essentially is <b>not</b> a breaking change, but you might want to look into this in case your code checks the responses in a more strict way.</p>

      <p><b>What is going to change?</b></p>

<p> Until now, it was not possible to filter manually created leads specifically, 
  because the <code>source_name</code> was an empty string. After adding an actual value to the 
  <code>source_name</code>, it will be possible to filter manually created leads using this value.</p>

      <p><b>Who is affected?</b></p>

<p>Anyone with functionality built on top of the previous behavior will need to alter their code.
</p>
          <br>
      <p class="published-on"><i>Published on May 6, 2021</i></p>
  </div>
</div>


Breaking change in Leads API response

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 27, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="permissions-update-for-calllogs-creation"></div>
        <div class="heading-text"><div id="permissions-update-for-calllogs-creation" class="heading-anchor_backwardsCompatibility">
          </div>Permissions update for CallLogs creation</div>
        <a aria-label="Skip link to Permissions update for CallLogs creation" class="heading-anchor-icon fa fa-anchor" 
           href="#permissions-update-for-calllogs-creation"></a></h3>
      
        
      <p><b>Endpoint directly affected:</b></p>
      <ul><li><code><a href="https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLog" target"_self">POST /callLogs</a></code></li></ul>

      <p><b>What is going to change?</b></p>

<p>Going forward, the creation of a call log will be limited by the creating User's permissions. If the User creating the call log does not have the permission to view the Person, Organization or Deal that is attached to this activity, then the call log will not be created. A User can only attach entities they have permissions to see to the call log.</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. Therefore, if you are creating call logs then you need to review whether this functionality of the permissions update requires changes on your side.
</p>
          <br>
      <p class="published-on"><i>Published on April 29, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 27, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="permissions-update-for-calllogs-creation"></div>
        <div class="heading-text"><div id="permissions-update-for-calllogs-creation" class="heading-anchor_backwardsCompatibility">
          </div>Permissions update for CallLogs creation</div>
        <a aria-label="Skip link to Permissions update for CallLogs creation" class="heading-anchor-icon fa fa-anchor" 
           href="#permissions-update-for-calllogs-creation"></a></h3>
      
        
      <p><b>Endpoint directly affected:</b></p>
      <ul><li><code><a href="https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLog" target"_self">POST /callLogs</a></code></li></ul>

      <p><b>What is going to change?</b></p>

<p>Going forward, the creation of a call log will be limited by the creating User's permissions. If the User creating the call log does not have the permission to view the Person, Organization or Deal that is attached to this activity, then the call log will not be created. A User can only attach entities they have permissions to see to the call log.</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. Therefore, if you are creating call logs then you need to review whether this functionality of the permissions update requires changes on your side.
</p>
          <br>
      <p class="published-on"><i>Published on April 29, 2021</i></p>
  </div>
</div>


Permissions update for CallLogs creation

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 12, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="bug-fix-in-webhooks-payload"></div>
        <div class="heading-text"><div id="bug-fix-in-webhooks-payload" class="heading-anchor_backwardsCompatibility">
          </div>Bug fix in Webhooks payload</div>
        <a aria-label="Skip link to Bug fix in Webhooks payload" class="heading-anchor-icon fa fa-anchor" 
           href="#bug-fix-in-webhooks-payload"></a></h3>
      
         
      <p>We will fix the requests’ payload mismatch for webhooks triggered manually and via the API: the address-related data in the <code>current</code> and <code>previous</code> objects will match the API response format.


</p>
     
      <p>Please remove any dependencies relying on the current behavior.</p>
          <br>
      <p class="published-on"><i>Published on April 28, 2021</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">May 12, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="bug-fix-in-webhooks-payload"></div>
        <div class="heading-text"><div id="bug-fix-in-webhooks-payload" class="heading-anchor_backwardsCompatibility">
          </div>Bug fix in Webhooks payload</div>
        <a aria-label="Skip link to Bug fix in Webhooks payload" class="heading-anchor-icon fa fa-anchor" 
           href="#bug-fix-in-webhooks-payload"></a></h3>
      
         
      <p>We will fix the requests’ payload mismatch for webhooks triggered manually and via the API: the address-related data in the <code>current</code> and <code>previous</code> objects will match the API response format.


</p>
     
      <p>Please remove any dependencies relying on the current behavior.</p>
          <br>
      <p class="published-on"><i>Published on April 28, 2021</i></p>
  </div>
</div>


Bug fix in Webhooks payload

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 5, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="change-in-the-availability-of-webhooks-for-apps"></div>
        <div class="heading-text"><div id="change-in-the-availability-of-webhooks-for-apps" class="heading-anchor_backwardsCompatibility">
          </div>Change in the availability of webhooks for apps</div>
        <a aria-label="Skip link to Change in the availability of webhooks for apps" class="heading-anchor-icon fa fa-anchor" 
           href="#change-in-the-availability-of-webhooks-for-apps"></a></h3>
      
    
      <p><b>What is changing?</b></p>
      <p>Apps that are creating, fetching, and deleting webhooks as a part of their functionality will start to only be able to see and delete webhooks that the app itself has created.  This means that starting from the change date, an app can see and delete only  webhooks that have the type set as <code>type='application'</code>. </p>
        
       <p> This is done to protect and maintain a separation of admin privileges to manage users' webhooks and applications' webhooks.</p>
      
      <p><b>Who is affected?</b></p>
      <p> Every app that has functionality that relies on receiving any other type of webhooks besides  <code>'application'</code>, e.g. <code>'general'</code>.</p>
          <br>
      <p class="published-on"><i>Published on April 5, 2021</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">May 5, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="change-in-the-availability-of-webhooks-for-apps"></div>
        <div class="heading-text"><div id="change-in-the-availability-of-webhooks-for-apps" class="heading-anchor_backwardsCompatibility">
          </div>Change in the availability of webhooks for apps</div>
        <a aria-label="Skip link to Change in the availability of webhooks for apps" class="heading-anchor-icon fa fa-anchor" 
           href="#change-in-the-availability-of-webhooks-for-apps"></a></h3>
      
    
      <p><b>What is changing?</b></p>
      <p>Apps that are creating, fetching, and deleting webhooks as a part of their functionality will start to only be able to see and delete webhooks that the app itself has created.  This means that starting from the change date, an app can see and delete only  webhooks that have the type set as <code>type='application'</code>. </p>
        
       <p> This is done to protect and maintain a separation of admin privileges to manage users' webhooks and applications' webhooks.</p>
      
      <p><b>Who is affected?</b></p>
      <p> Every app that has functionality that relies on receiving any other type of webhooks besides  <code>'application'</code>, e.g. <code>'general'</code>.</p>
          <br>
      <p class="published-on"><i>Published on April 5, 2021</i></p>
  </div>
</div>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog