<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 26, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="permissionsets-API-breaking-changes"></div>
        <div class="heading-text"><div id="permissionsets-API-breaking-changes" class="heading-anchor_backwardsCompatibility">
          </div>PermissionSets API breaking change</div>
        <a aria-label="Skip link to PermissionSets API breaking change" class="heading-anchor-icon fa fa-anchor" 
           href="#permissionsets-API-breaking-changes"></a></h3>
      
         
      <p><strong>UPDATE (July 23, 2021)</strong>: Based on your feedback and to give you more time to align with our API changes, we’ve decided to postpone the breaking changes to our <a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets">PermissionSets API</a> to <b>September 1, 2021</b>.
See <a href="https://pipedrive.readme.io/docs/changelog#permissionsets-API-breaking-changes-postponed" target="_self">the announcement</a> for more.</p>


      <p>There are the following breaking changes happening to <a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets" target="_self">PermissionSets API</a>:</p>
      <p><b>What is going to change?</b></p>
      <p>1. The Permission Set ID format will be changed from integer to UUID (universally unique identifier) string. This means that the current IDs will be replaced with <b>new</b> values both in the endpoint path and the response body for the following three endpoints:
</p>
      <ul>
 <li><code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSets" target="_self">GET /v1/permissionSets</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSet" target="_self">GET /v1/permissionSets/:id</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSetAssignments" target="_self">GET /v1/permissionSets/:id/assignments</a></code></li>
      </ul>
      
      <p>2. The response of <code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSetAssignments" target="_self">GET /v1/permissionSets/:id/assignments</a></code>
        will no longer include the <code>id</code> field per assignment. An assignment is an object which currently includes the following fields
</p>
      <ul>
        <li><code>id</code> (which will be removed)</li>
       <li><code>user_id</code></li>
        <li><code>permission_set_id</code></li>
        <li><code>name</code> (the name of the PermissionSet)</li>
      </ul>
      
      <p>3. Permission Set objects returned from  <code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSets" target="_self">GET /v1/permissionSets</a></code>
 and <code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSet" target="_self">GET /v1/permissionSets/:id</a></code>
        will temporarily (for the next 2 months) have an additional field <code>old_id</code> of type integer, which will contain the old ID value </p>
      
      <p>4. Permission Set Assignment objects returned from <code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSetAssignments" target="_self">GET /v1/permissionSets/:id/assignments</a></code>
 will temporarily (for the next 2 months) have an additional field <code>permission_set_id_old</code> of type integer, which will contain the old Permission Set ID value
</p>
      
      <p><b>Why is it going to change?</b></p>
     <p> We are updating our data storage in preparation for providing the new Permission Set functionality in the near future.</p>
            <p><b>Who is affected?</b></p>
      <p>All consumers of the listed API endpoints are affected in case they
</p>
      <ul>
        <li>specifically expect Permission Set ID to be an integer
</li>
<li>rely on the removed Permission Set Assignment id field
</li>
        </ul>
        <br>
      <p class="published-on"><i>Published on July 8, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 26, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="permissionsets-API-breaking-changes"></div>
        <div class="heading-text"><div id="permissionsets-API-breaking-changes" class="heading-anchor_backwardsCompatibility">
          </div>PermissionSets API breaking change</div>
        <a aria-label="Skip link to PermissionSets API breaking change" class="heading-anchor-icon fa fa-anchor" 
           href="#permissionsets-API-breaking-changes"></a></h3>
      
         
      <p><strong>UPDATE (July 23, 2021)</strong>: Based on your feedback and to give you more time to align with our API changes, we’ve decided to postpone the breaking changes to our <a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets">PermissionSets API</a> to <b>September 1, 2021</b>.
See <a href="/changelog/post/permissionsets-API-breaking-changes-postponed" target="_self">the announcement</a> for more.</p>


      <p>There are the following breaking changes happening to <a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets" target="_self">PermissionSets API</a>:</p>
      <p><b>What is going to change?</b></p>
      <p>1. The Permission Set ID format will be changed from integer to UUID (universally unique identifier) string. This means that the current IDs will be replaced with <b>new</b> values both in the endpoint path and the response body for the following three endpoints:
</p>
      <ul>
 <li><code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSets" target="_self">GET /v1/permissionSets</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSet" target="_self">GET /v1/permissionSets/:id</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSetAssignments" target="_self">GET /v1/permissionSets/:id/assignments</a></code></li>
      </ul>
      
      <p>2. The response of <code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSetAssignments" target="_self">GET /v1/permissionSets/:id/assignments</a></code>
        will no longer include the <code>id</code> field per assignment. An assignment is an object which currently includes the following fields
</p>
      <ul>
        <li><code>id</code> (which will be removed)</li>
       <li><code>user_id</code></li>
        <li><code>permission_set_id</code></li>
        <li><code>name</code> (the name of the PermissionSet)</li>
      </ul>
      
      <p>3. Permission Set objects returned from  <code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSets" target="_self">GET /v1/permissionSets</a></code>
 and <code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSet" target="_self">GET /v1/permissionSets/:id</a></code>
        will temporarily (for the next 2 months) have an additional field <code>old_id</code> of type integer, which will contain the old ID value </p>
      
      <p>4. Permission Set Assignment objects returned from <code><a href="https://developers.pipedrive.com/docs/api/v1/PermissionSets#getPermissionSetAssignments" target="_self">GET /v1/permissionSets/:id/assignments</a></code>
 will temporarily (for the next 2 months) have an additional field <code>permission_set_id_old</code> of type integer, which will contain the old Permission Set ID value
</p>
      
      <p><b>Why is it going to change?</b></p>
     <p> We are updating our data storage in preparation for providing the new Permission Set functionality in the near future.</p>
            <p><b>Who is affected?</b></p>
      <p>All consumers of the listed API endpoints are affected in case they
</p>
      <ul>
        <li>specifically expect Permission Set ID to be an integer
</li>
<li>rely on the removed Permission Set Assignment id field
</li>
        </ul>
        <br>
      <p class="published-on"><i>Published on July 8, 2021</i></p>
  </div>
</div>


PermissionSets API breaking change

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 6, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="removal-of-app-extensions-for-products"></div>
        <div class="heading-text"><div id="removal-of-app-extensions-for-products" class="heading-anchor_backwardsCompatibility">
          </div>Removal of App Extensions for Products</div>
        <a aria-label="Skip link to Removal of app extensions for Products" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-app-extensions-for-products"></a></h3>
        
      <p><b>What has changed?</b></p>
     <p>Support for app extensions inside Products List view, including basic app actions and embedded app actions, is now discontinued.
      </p>

      <p><b>Why was it discontinued?</b></p>

<p>It was discontinued due to a technical change. As we have noticed that no submitted app has been making use of app extensions for Products in List view, we decided to discontinue support for it.
      </p>
<p>Should you be keen on using basic app actions or embedded app actions inside Product details or list views, please contact us directly at <a href:"mailto"marketplace.devs@pipedrive.com">marketplace.devs@pipedrive.com</a> and tell us your use case. We’d be very happy to hear from you!
</p>
          <br>
      <p class="published-on"><i>Published on July 6, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

{"product": ["App extensions"], "features": ["App actions"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 6, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="removal-of-app-extensions-for-products"></div>
        <div class="heading-text"><div id="removal-of-app-extensions-for-products" class="heading-anchor_backwardsCompatibility">
          </div>Removal of App Extensions for Products</div>
        <a aria-label="Skip link to Removal of app extensions for Products" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-app-extensions-for-products"></a></h3>
        
      <p><b>What has changed?</b></p>
     <p>Support for app extensions inside Products List view, including basic app actions and embedded app actions, is now discontinued.
      </p>

      <p><b>Why was it discontinued?</b></p>

<p>It was discontinued due to a technical change. As we have noticed that no submitted app has been making use of app extensions for Products in List view, we decided to discontinue support for it.
      </p>
<p>Should you be keen on using basic app actions or embedded app actions inside Product details or list views, please contact us directly at <a href:"mailto"marketplace.devs@pipedrive.com">marketplace.devs@pipedrive.com</a> and tell us your use case. We’d be very happy to hear from you!
</p>
          <br>
      <p class="published-on"><i>Published on July 6, 2021</i></p>
  </div>
</div>


Removal of App Extensions for Products

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 15, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="error-response-correction-for-search-api"></div>
        <div class="heading-text"><div id="error-response-correction-for-search-api" class="heading-anchor_backwardsCompatibility">
          </div>Error response correction for Search API</div>
        <a aria-label="Skip link to Error response correction for Search API" class="heading-anchor-icon fa fa-anchor" 
           href="#error-response-correction-for-search-api"></a></h3>

  <p><b>What is going to change?</b></p>
     <p>We are going to update the current incorrect error response to match <a href="https://pipedrive.readme.io/docs/core-api-concepts-responses">Pipedrive API’s core concepts of responses</a> for the following Search endpoints:
      </p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#searchDeals">GET /v1/deals/search</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem">GET /v1/itemSearch</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItemByField">GET /itemSearch/field</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#searchOrganization">GET /organizations/search</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#searchPersons">GET /persons/search</a></code></li>
      </ul>
         <p>Here is an example of a correct error response which will be applied for the endpoints listed above:
      </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">false</span>,
 <span class="cm-property">"error"</span>: <span class="cm-string">"Requested service is not available"</span>, <span class="cm-comment">//main error message</span>
 <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com"</span>,
 <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
 <span class="cm-property">"additional data"</span>: <span class="cm-atom">null</span>
}
</div></code></pre></div></div>
      
      <p><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 July 1, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 15, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="error-response-correction-for-search-api"></div>
        <div class="heading-text"><div id="error-response-correction-for-search-api" class="heading-anchor_backwardsCompatibility">
          </div>Error response correction for Search API</div>
        <a aria-label="Skip link to Error response correction for Search API" class="heading-anchor-icon fa fa-anchor" 
           href="#error-response-correction-for-search-api"></a></h3>

  <p><b>What is going to change?</b></p>
     <p>We are going to update the current incorrect error response to match <a href="https://pipedrive.readme.io/docs/core-api-concepts-responses">Pipedrive API’s core concepts of responses</a> for the following Search endpoints:
      </p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#searchDeals">GET /v1/deals/search</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem">GET /v1/itemSearch</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItemByField">GET /itemSearch/field</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#searchOrganization">GET /organizations/search</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#searchPersons">GET /persons/search</a></code></li>
      </ul>
         <p>Here is an example of a correct error response which will be applied for the endpoints listed above:
      </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">false</span>,
 <span class="cm-property">"error"</span>: <span class="cm-string">"Requested service is not available"</span>, <span class="cm-comment">//main error message</span>
 <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com"</span>,
 <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
 <span class="cm-property">"additional data"</span>: <span class="cm-atom">null</span>
}
</div></code></pre></div></div>
      
      <p><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 July 1, 2021</i></p>
  </div>
</div>


Error response correction for Search API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 30, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="breaking-bug-fix-in-post-deals-endpoint"></div>
        <div class="heading-text"><div id="breaking-bug-fix-in-post-deals-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Breaking bug fix in POST /deals endpoint</div>
        <a aria-label="Skip link to Breaking bug fix in POST /deals endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-bug-fix-in-post-deals-endpoint"></a></h3>
      
        
      <p><b>What is going to change?</b></p>
     <p> When creating a Deal via the Pipedrive API, it will start requiring the new Deal to be linked to a Person or an Organization. Therefore, when adding a Deal via the the <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal">POST /deals</a></code> endpoint, one has to insert a value for either one of these body parameters:
      </p>
      <ul>
        <li><code>person_id</code> - ID of the Person this Deal will be associated with</li>
        <li><code>org_id</code> - ID of the Organization this Deal will be associated with</li>      
      </ul>
      <p>We will be adding the red ‘required’ label to both of these body parameters in our API Reference documentation when the given grace time is over.</p>

      <p><b>Why is it going to change?</b></p>

<p>In the Pipedrive web app, it has always been mandatory to have the newly created Deal linked with a Person or an Organization. This change is needed to keep the data in Pipedrive consistent. We wish to avoid unexpected results forPipedrive users when they use the Product and other features with the Deal being not linked to a Person or an Organization.
      </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 June 30, 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">September 30, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="breaking-bug-fix-in-post-deals-endpoint"></div>
        <div class="heading-text"><div id="breaking-bug-fix-in-post-deals-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Breaking bug fix in POST /deals endpoint</div>
        <a aria-label="Skip link to Breaking bug fix in POST /deals endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-bug-fix-in-post-deals-endpoint"></a></h3>
      
        
      <p><b>What is going to change?</b></p>
     <p> When creating a Deal via the Pipedrive API, it will start requiring the new Deal to be linked to a Person or an Organization. Therefore, when adding a Deal via the the <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal">POST /deals</a></code> endpoint, one has to insert a value for either one of these body parameters:
      </p>
      <ul>
        <li><code>person_id</code> - ID of the Person this Deal will be associated with</li>
        <li><code>org_id</code> - ID of the Organization this Deal will be associated with</li>      
      </ul>
      <p>We will be adding the red ‘required’ label to both of these body parameters in our API Reference documentation when the given grace time is over.</p>

      <p><b>Why is it going to change?</b></p>

<p>In the Pipedrive web app, it has always been mandatory to have the newly created Deal linked with a Person or an Organization. This change is needed to keep the data in Pipedrive consistent. We wish to avoid unexpected results forPipedrive users when they use the Product and other features with the Deal being not linked to a Person or an Organization.
      </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 June 30, 2021</i></p>
  </div>
</div>


Breaking bug fix in <code>POST /deals</code> endpoint

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


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


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog