<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 1, 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-response-data-of-get-/activityFields-endpoint"></div>
        <div class="heading-text"><div id="change-in-the-response-data-of-get-/activityFields-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Change in the response data of GET /activityFields endpoint</div>
        <a aria-label="Skip link to Change in the response data of GET /activityFields endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#change-in-the-response-data-of-get-/activityFields-endpoint"></a></h3>
     
      <p><b>What has changed?</b></p>
      
     <p> The response of 
<code> <a href="https://developers.pipedrive.com/docs/api/v1/ActivityFields#getActivityFields"  target="_self">GET /activityFields</a></code> will now include fields with following data
       <code>"key": "lead_id"</code> and <code>"field_type": "lead"</code> instead of <code>"key": "lead_title"</code> and <code>"field_type": "varchar"</code>. </p>
 
       <p>Updated example of response structure for the object:</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-meta">...</span>
            <span class="cm-string">"key"</span>: <span class="cm-string">"lead_id"</span>,
            <span class="cm-property">"name"</span>: <span class="cm-string">"Lead"</span>,
            <span class="cm-property">"order_nr"</span>: <span class="cm-number">21</span>,
            <span class="cm-property">"picklist_data"</span>: <span class="cm-atom">null</span>,
            <span class="cm-property">"field_type"</span>: <span class="cm-string">"lead"</span>,
            <span class="cm-property">"json_column_flag"</span>: <span class="cm-atom">false</span>,
            <span class="cm-property">"add_time"</span>: <span class="cm-string">"2019-12-15 12:10:23"</span>,
            <span class="cm-property">"update_time"</span>: <span class="cm-string">"2019-12-15 12:10:23"</span>,
<span class="cm-property">…</span>
}
</div></code></pre></div></div>
      
      
      <p><b>Why was it changed?</b></p>
      <p>This change was done to unify the information returned by the API to 
        make the response more consistent and clearer for data usage about Leads in Activity fields.</p> 

<p>To get data about the lead linked to an Activity, you can use the <code> <a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLead"  target="_self">GET /leads/{id}</a></code> endpoint.

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

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 1, 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-response-data-of-get-/activityFields-endpoint"></div>
        <div class="heading-text"><div id="change-in-the-response-data-of-get-/activityFields-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Change in the response data of GET /activityFields endpoint</div>
        <a aria-label="Skip link to Change in the response data of GET /activityFields endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#change-in-the-response-data-of-get-/activityFields-endpoint"></a></h3>
     
      <p><b>What has changed?</b></p>
      
     <p> The response of 
<code> <a href="https://developers.pipedrive.com/docs/api/v1/ActivityFields#getActivityFields"  target="_self">GET /activityFields</a></code> will now include fields with following data
       <code>"key": "lead_id"</code> and <code>"field_type": "lead"</code> instead of <code>"key": "lead_title"</code> and <code>"field_type": "varchar"</code>. </p>
 
       <p>Updated example of response structure for the object:</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-meta">...</span>
            <span class="cm-string">"key"</span>: <span class="cm-string">"lead_id"</span>,
            <span class="cm-property">"name"</span>: <span class="cm-string">"Lead"</span>,
            <span class="cm-property">"order_nr"</span>: <span class="cm-number">21</span>,
            <span class="cm-property">"picklist_data"</span>: <span class="cm-atom">null</span>,
            <span class="cm-property">"field_type"</span>: <span class="cm-string">"lead"</span>,
            <span class="cm-property">"json_column_flag"</span>: <span class="cm-atom">false</span>,
            <span class="cm-property">"add_time"</span>: <span class="cm-string">"2019-12-15 12:10:23"</span>,
            <span class="cm-property">"update_time"</span>: <span class="cm-string">"2019-12-15 12:10:23"</span>,
<span class="cm-property">…</span>
}
</div></code></pre></div></div>
      
      
      <p><b>Why was it changed?</b></p>
      <p>This change was done to unify the information returned by the API to 
        make the response more consistent and clearer for data usage about Leads in Activity fields.</p> 

<p>To get data about the lead linked to an Activity, you can use the <code> <a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLead"  target="_self">GET /leads/{id}</a></code> endpoint.

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


Change in the response data of <code>GET /activityFields</code> endpoint

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 22, 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-products-endpoint-and-webhook"></div>
        <div class="heading-text"><div id="breaking-change-in-products-endpoint-and-webhook" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in Products endpoint and Webhook</div>
        <a aria-label="Skip link to Breaking change in Products endpoint and Webhook" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-products-endpoint-and-webhook"></a></h3>
      
         
      <p><b>What is going to change?</b></p>
      
   <p>   The response structure to <code> <a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct"  target="_self">PUT v1/products/{id}</a></code> <code>prices</code> property will change.
     The <code>prices</code> property will be sent as an array of objects instead of an object.
     This change will also impact the webhook <b><code>updated.product</code></b> response payload as 
     its response structure will change in the same way as the endpoint. </p>
      
      <p>Response structure before</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-meta">...</span>
            <span class="cm-string">"key"</span>: <span class="cm-string">"lead_id"</span>,
            <span class="cm-property">"name"</span>: <span class="cm-string">"Lead"</span>,
            <span class="cm-property">"order_nr"</span>: <span class="cm-number">21</span>,
            <span class="cm-property">"picklist_data"</span>: <span class="cm-atom">null</span>,
            <span class="cm-property">"field_type"</span>: <span class="cm-string">"lead"</span>,
            <span class="cm-property">"json_column_flag"</span>: <span class="cm-atom">false</span>,
            <span class="cm-property">"add_time"</span>: <span class="cm-string">"2019-12-15 12:10:23"</span>,
            <span class="cm-property">"update_time"</span>: <span class="cm-string">"2019-12-15 12:10:23"</span>,
<span class="cm-property">…</span>
}
</div></code></pre></div></div>
      
    <p>Response structure after</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-meta">...</span>
<span class="cm-string">"add_time"</span>: <span class="cm-string">"2019-12-19 11:36:49"</span>,
<span class="cm-string">"update_time"</span>: <span class="cm-string">"2019-12-26 13:35:17"</span>,
<span class="cm-string">"prices"</span>: [{
  <span class="cm-property">"EUR"</span>: {
   <span class="cm-property">"id"</span>: <span class="cm-number">1</span>,
   <span class="cm-property">"product_id"</span>: <span class="cm-number">1</span>,
   <span class="cm-property">"price"</span>: <span class="cm-number">5</span>,
   <span class="cm-property">"currency"</span>: <span class="cm-string">"EUR"</span>,
   <span class="cm-property">"cost"</span>: <span class="cm-number">2</span>,
   <span class="cm-property">"overhead_cost"</span>: <span class="cm-number">3</span>
  }
 ]
}
<span class="cm-meta">...</span>
</div></code></pre></div></div>
      
      <p><b> Why is it going to change? </b></p>
<p>This is done to increase the overall consistency of all Products endpoints and webhooks to align with best practices.</p>

 <p><b>Who is affected? </b></p>
<p><ul> <li>API consumers who strictly check the response structure of the <code><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct"  target="_self">PUT v1/products/{id}</a></code> endpoint.</li>
<li>Apps or users who either check themselves or use a tool to check the payload structure of <code>updated.products</code> webhook.</li></ul> </p>



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

{"product": ["API", "Webhooks"], "features": ["Products"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 22, 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-products-endpoint-and-webhook"></div>
        <div class="heading-text"><div id="breaking-change-in-products-endpoint-and-webhook" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in Products endpoint and Webhook</div>
        <a aria-label="Skip link to Breaking change in Products endpoint and Webhook" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-products-endpoint-and-webhook"></a></h3>
      
         
      <p><b>What is going to change?</b></p>
      
   <p>   The response structure to <code> <a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct"  target="_self">PUT v1/products/{id}</a></code> <code>prices</code> property will change.
     The <code>prices</code> property will be sent as an array of objects instead of an object.
     This change will also impact the webhook <b><code>updated.product</code></b> response payload as 
     its response structure will change in the same way as the endpoint. </p>
      
      <p>Response structure before</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-meta">...</span>
            <span class="cm-string">"key"</span>: <span class="cm-string">"lead_id"</span>,
            <span class="cm-property">"name"</span>: <span class="cm-string">"Lead"</span>,
            <span class="cm-property">"order_nr"</span>: <span class="cm-number">21</span>,
            <span class="cm-property">"picklist_data"</span>: <span class="cm-atom">null</span>,
            <span class="cm-property">"field_type"</span>: <span class="cm-string">"lead"</span>,
            <span class="cm-property">"json_column_flag"</span>: <span class="cm-atom">false</span>,
            <span class="cm-property">"add_time"</span>: <span class="cm-string">"2019-12-15 12:10:23"</span>,
            <span class="cm-property">"update_time"</span>: <span class="cm-string">"2019-12-15 12:10:23"</span>,
<span class="cm-property">…</span>
}
</div></code></pre></div></div>
      
    <p>Response structure after</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-meta">...</span>
<span class="cm-string">"add_time"</span>: <span class="cm-string">"2019-12-19 11:36:49"</span>,
<span class="cm-string">"update_time"</span>: <span class="cm-string">"2019-12-26 13:35:17"</span>,
<span class="cm-string">"prices"</span>: [{
  <span class="cm-property">"EUR"</span>: {
   <span class="cm-property">"id"</span>: <span class="cm-number">1</span>,
   <span class="cm-property">"product_id"</span>: <span class="cm-number">1</span>,
   <span class="cm-property">"price"</span>: <span class="cm-number">5</span>,
   <span class="cm-property">"currency"</span>: <span class="cm-string">"EUR"</span>,
   <span class="cm-property">"cost"</span>: <span class="cm-number">2</span>,
   <span class="cm-property">"overhead_cost"</span>: <span class="cm-number">3</span>
  }
 ]
}
<span class="cm-meta">...</span>
</div></code></pre></div></div>
      
      <p><b> Why is it going to change? </b></p>
<p>This is done to increase the overall consistency of all Products endpoints and webhooks to align with best practices.</p>

 <p><b>Who is affected? </b></p>
<p><ul> <li>API consumers who strictly check the response structure of the <code><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct"  target="_self">PUT v1/products/{id}</a></code> endpoint.</li>
<li>Apps or users who either check themselves or use a tool to check the payload structure of <code>updated.products</code> webhook.</li></ul> </p>



      <p class="published-on"><i>Published on September 24, 2021</i></p>
  </div>
</div>


Breaking change in Products endpoint and Webhook

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 20, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="change-in-file-download-URLs-for-5-endpoints"></div>
        <div class="heading-text"><div id="change-in-file-download-URLs-for-5-endpoints" class="heading-anchor_backwardsCompatibility">
          </div>Change in file download URLs for 5 endpoints</div>
        <a aria-label="Skip link to Change in file download URLs for 5 endpoints" class="heading-anchor-icon fa fa-anchor" 
           href="#change-in-file-download-URLs-for-5-endpoints"></a></h3>
      
      <p><b>What is going to change?</b></p>
      <p>
        The <code>URL</code> value when downloading public files for the following 5 endpoints will now contain generic API download links instead of direct temporary links:
         <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/Deals#getDealUpdates" target="_self">GET /v1/deals/{id}/flow</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationUpdates" target="_self">GET /v1/organizations/{id}/flow</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>
      </p>
  <p>
    The download links will be the same as the ones given out by the <code><a href="https://developers.pipedrive.com/docs/api/v1/Files#getFiles">GET /v1/files</a></code> endpoint. 
  </p>
            <p><b>Who is affected?</b></p>
    <p>Anyone who uses any of the 5 endpoints listed above to download public files. You will now have to use your authentication headers or an <code>api_token</code> to download files from these endpoints.
  </p>
      <p class="published-on"><i>Published on September 20, 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">October 20, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="change-in-file-download-URLs-for-5-endpoints"></div>
        <div class="heading-text"><div id="change-in-file-download-URLs-for-5-endpoints" class="heading-anchor_backwardsCompatibility">
          </div>Change in file download URLs for 5 endpoints</div>
        <a aria-label="Skip link to Change in file download URLs for 5 endpoints" class="heading-anchor-icon fa fa-anchor" 
           href="#change-in-file-download-URLs-for-5-endpoints"></a></h3>
      
      <p><b>What is going to change?</b></p>
      <p>
        The <code>URL</code> value when downloading public files for the following 5 endpoints will now contain generic API download links instead of direct temporary links:
         <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/Deals#getDealUpdates" target="_self">GET /v1/deals/{id}/flow</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationUpdates" target="_self">GET /v1/organizations/{id}/flow</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>
      </p>
  <p>
    The download links will be the same as the ones given out by the <code><a href="https://developers.pipedrive.com/docs/api/v1/Files#getFiles">GET /v1/files</a></code> endpoint. 
  </p>
            <p><b>Who is affected?</b></p>
    <p>Anyone who uses any of the 5 endpoints listed above to download public files. You will now have to use your authentication headers or an <code>api_token</code> to download files from these endpoints.
  </p>
      <p class="published-on"><i>Published on September 20, 2021</i></p>
  </div>
</div>


Change in file download URLs for 5 endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 25, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="app-panels-become-interactive"></div>
        <div class="heading-text"><div id="app-panels-become-interactive" class="heading-anchor_backwardsCompatibility">
          </div>App panels become interactive</div>
        <a aria-label="Skip link to App panels become interactive" class="heading-anchor-icon fa fa-anchor" 
           href="#app-panels-become-interactive"></a></h3>
   
     <p>One of the main app extension points in Pipedrive, app panels, now allows you to include field and objects actions in the form of <a href="https://pipedrive.readme.io/docs/app-extensions-actions" target="_self">basic</a> or <a href="https://pipedrive.readme.io/docs/app-extensions-embedded-actions" target="_self">embedded app actions</a>. 
         With one click, users can use the app’s data displayed in the panel by clicking an action.
         This will allow them to modify, update, send new information to your app. </p>



<div class="magic-block-image">
	<figure><a href="https://files.readme.io/7bfc696-App_extensions_-_structure_of_an_app_panel_-_Pipedrive.png" class="block-display-image-parent block-display-image-size-80"><img src="https://files.readme.io/7bfc696-App_extensions_-_structure_of_an_app_panel_-_Pipedrive.png" alt="Structure of the app panel"></a>
	</figure>
	<figcaption><p>Structure of the app panel</p>
</figcaption>
</div>
      
       
<p>With new capabilities, we have also introduced some new field types (say "Hi!" to <code>tags</code> and markdown support in <code>text</code>) as well as providing an easily accessible way 
  for different types of global actions through a green action button. </p>

<p>Also, you can now include a custom error state so users will immediately 
  know what to do if something out of order happens.</p>

      <p>Read more in our guides for <a href="https://pipedrive.readme.io/docs/app-extensions-panels" target="_self">what are app panels</a>, <a href="https://pipedrive.readme.io/docs/app-panels-adding-a-panel" target="_self">how to create one</a>, and <a href="https://pipedrive.readme.io/docs/app-panels-actions-in-panels" target="_self">how to add different actions to the panel</a>. 
For discussions, requests and feedback, join us in <a href="https://devcommunity.pipedrive.com/t/app-panels-become-interactive/4545" target="_self">the DevCommunity thread</a>!
      </p>
      
      
       <br>
      <p class="published-on"><i>Published on August 25, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 25, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="app-panels-become-interactive"></div>
        <div class="heading-text"><div id="app-panels-become-interactive" class="heading-anchor_backwardsCompatibility">
          </div>App panels become interactive</div>
        <a aria-label="Skip link to App panels become interactive" class="heading-anchor-icon fa fa-anchor" 
           href="#app-panels-become-interactive"></a></h3>
   
     <p>One of the main app extension points in Pipedrive, app panels, now allows you to include field and objects actions in the form of <a href="https://pipedrive.readme.io/docs/app-extensions-actions" target="_self">basic</a> or <a href="https://pipedrive.readme.io/docs/app-extensions-embedded-actions" target="_self">embedded app actions</a>. 
         With one click, users can use the app’s data displayed in the panel by clicking an action.
         This will allow them to modify, update, send new information to your app. </p>



<div class="magic-block-image">
	<figure><a href="https://files.readme.io/7bfc696-App_extensions_-_structure_of_an_app_panel_-_Pipedrive.png" class="block-display-image-parent block-display-image-size-80"><img src="https://files.readme.io/7bfc696-App_extensions_-_structure_of_an_app_panel_-_Pipedrive.png" alt="Structure of the app panel"></a>
	</figure>
	<figcaption><p>Structure of the app panel</p>
</figcaption>
</div>
      
       
<p>With new capabilities, we have also introduced some new field types (say "Hi!" to <code>tags</code> and markdown support in <code>text</code>) as well as providing an easily accessible way 
  for different types of global actions through a green action button. </p>

<p>Also, you can now include a custom error state so users will immediately 
  know what to do if something out of order happens.</p>

      <p>Read more in our guides for <a href="https://pipedrive.readme.io/docs/app-extensions-panels" target="_self">what are app panels</a>, <a href="https://pipedrive.readme.io/docs/app-panels-adding-a-panel" target="_self">how to create one</a>, and <a href="https://pipedrive.readme.io/docs/app-panels-actions-in-panels" target="_self">how to add different actions to the panel</a>. 
For discussions, requests and feedback, join us in <a href="https://devcommunity.pipedrive.com/t/app-panels-become-interactive/4545" target="_self">the DevCommunity thread</a>!
      </p>
      
      
       <br>
      <p class="published-on"><i>Published on August 25, 2021</i></p>
  </div>
</div>


App panels become interactive

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 4, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="documentation-updates-for-api-reference"></div>
        <div class="heading-text"><div id="documentation-updates-for-api-reference" class="heading-anchor_backwardsCompatibility">
          </div>Documentation updates for API Reference</div>
        <a aria-label="Skip link to Documentation updates for API Reference" class="heading-anchor-icon fa fa-anchor" 
           href="#documentation-updates-for-api-reference"></a></h3>
      
     <p>Here are the most recent updates to our <a href="https://developers.pipedrive.com/docs/api/v1/">API Reference page</a>:
      </p>
      
      <p><b>1.</b> We documented the <b>required</b> flag for the <code>name</code> parameter for 
<code><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField" target="_self">POST /dealFields</a></code>, 
<code><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField" target="_self">POST /personFields</a></code> and 
<code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField" target="_self">POST /organizationFields</a></code> endpoints to reflect the actual functionality;</p>
      <p><b>2.</b> We added <code>product</code> and <code>related_objects</code> objects to <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts" target="_self">GET /deals/{id}/products</a></code> response schema; </p>
      <p><b>3.</b> We corrected the type of the <code>user_id</code> parameter from query parameter to body parameter for <code><a href="https://developers.pipedrive.com/docs/api/v1/Roles#deleteRoleAssignment" target="_self">DELETE /roles/{id}/assignments</a></code>;</p>
      <p><b>4.</b> For <code><a href="https://developers.pipedrive.com/docs/api/v1/Goals#addGoal" target="_self">POST /goals</a></code> endpoint, we fixed the description of the <code>interval</code> body parameter and changed it to accept <code>application/json</code> instead of <code>application/x-www-form-urlencoded</code> to reflect reality;</p>
      <p><b>5.</b> We documented the <code>add_visible_flag</code> body parameter in the documentation of the following six endpoints: </p>
   <p>   <ul><ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField" target="_self">POST /dealFields </a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealField" target="_self">PUT /dealFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField" target="_self">POST  /personFields </a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonField" target="_self">PUT  /personFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField" target="_self">POST /organizationFields </a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationField" target="_self">PUT /organizationFields</a></code></li>
      </ul></p></ul>
          
       <br>
      <p class="published-on"><i>Published on August 4, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

{"product": ["Developer Platform"], "features": ["API Reference"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 4, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="documentation-updates-for-api-reference"></div>
        <div class="heading-text"><div id="documentation-updates-for-api-reference" class="heading-anchor_backwardsCompatibility">
          </div>Documentation updates for API Reference</div>
        <a aria-label="Skip link to Documentation updates for API Reference" class="heading-anchor-icon fa fa-anchor" 
           href="#documentation-updates-for-api-reference"></a></h3>
      
     <p>Here are the most recent updates to our <a href="https://developers.pipedrive.com/docs/api/v1/">API Reference page</a>:
      </p>
      
      <p><b>1.</b> We documented the <b>required</b> flag for the <code>name</code> parameter for 
<code><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField" target="_self">POST /dealFields</a></code>, 
<code><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField" target="_self">POST /personFields</a></code> and 
<code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField" target="_self">POST /organizationFields</a></code> endpoints to reflect the actual functionality;</p>
      <p><b>2.</b> We added <code>product</code> and <code>related_objects</code> objects to <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts" target="_self">GET /deals/{id}/products</a></code> response schema; </p>
      <p><b>3.</b> We corrected the type of the <code>user_id</code> parameter from query parameter to body parameter for <code><a href="https://developers.pipedrive.com/docs/api/v1/Roles#deleteRoleAssignment" target="_self">DELETE /roles/{id}/assignments</a></code>;</p>
      <p><b>4.</b> For <code><a href="https://developers.pipedrive.com/docs/api/v1/Goals#addGoal" target="_self">POST /goals</a></code> endpoint, we fixed the description of the <code>interval</code> body parameter and changed it to accept <code>application/json</code> instead of <code>application/x-www-form-urlencoded</code> to reflect reality;</p>
      <p><b>5.</b> We documented the <code>add_visible_flag</code> body parameter in the documentation of the following six endpoints: </p>
   <p>   <ul><ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField" target="_self">POST /dealFields </a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealField" target="_self">PUT /dealFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField" target="_self">POST  /personFields </a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonField" target="_self">PUT  /personFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField" target="_self">POST /organizationFields </a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationField" target="_self">PUT /organizationFields</a></code></li>
      </ul></p></ul>
          
       <br>
      <p class="published-on"><i>Published on August 4, 2021</i></p>
  </div>
</div>


Documentation updates for API Reference

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 28, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="improving-leads-API"></div>
        <div class="heading-text"><div id="improving-leads-API" class="heading-anchor_backwardsCompatibility">
          </div>Improving Leads API</div>
        <a aria-label="Skip link to Improving Leads API" class="heading-anchor-icon fa fa-anchor" 
           href="#improving-leads-API"></a></h3>
      
     <p>We have made a few updates to our <a href="https://developers.pipedrive.com/docs/api/v1/Leads">Leads API</a>:
      </p>
<ul>
        <li>You can now indicate whether the Lead has been seen by someone in the Pipedrive UI via the new <code>was_seen</code> flag added to <code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead">POST /v1/leads/</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead">PATCH /v1/leads/\`{id}\`</a></code> endpoints.</li>
        <li>We have added the <code>visible_to</code> and the <code>cc_email</code> parameters to the responses of the following four endpoints:</li>
<ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads" target="_self">GET /v1/leads</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLead" target="_self">GET /v1/leads/\`{id}\`</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead" target="_self">POST /v1/leads/</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead" target="_self">PATCH /v1/leads/\`{id}\`</a></code></li>
</ul>
     
        <li>It is now possible to set the <code>visible_to</code> body parameter when requesting the following two endpoints:</li>
<ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead" target="_self">POST /v1/leads/</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead" target="_self">PATCH /v1/leads/\`{id}\`</a></code></li>
</ul>
     
     
        <br>
        <p class="published-on"><i>Published on July 28, 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">July 28, 2021</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="improving-leads-API"></div>
        <div class="heading-text"><div id="improving-leads-API" class="heading-anchor_backwardsCompatibility">
          </div>Improving Leads API</div>
        <a aria-label="Skip link to Improving Leads API" class="heading-anchor-icon fa fa-anchor" 
           href="#improving-leads-API"></a></h3>
      
     <p>We have made a few updates to our <a href="https://developers.pipedrive.com/docs/api/v1/Leads">Leads API</a>:
      </p>
<ul>
        <li>You can now indicate whether the Lead has been seen by someone in the Pipedrive UI via the new <code>was_seen</code> flag added to <code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead">POST /v1/leads/</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead">PATCH /v1/leads/\`{id}\`</a></code> endpoints.</li>
        <li>We have added the <code>visible_to</code> and the <code>cc_email</code> parameters to the responses of the following four endpoints:</li>
<ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads" target="_self">GET /v1/leads</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLead" target="_self">GET /v1/leads/\`{id}\`</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead" target="_self">POST /v1/leads/</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead" target="_self">PATCH /v1/leads/\`{id}\`</a></code></li>
</ul>
     
        <li>It is now possible to set the <code>visible_to</code> body parameter when requesting the following two endpoints:</li>
<ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead" target="_self">POST /v1/leads/</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead" target="_self">PATCH /v1/leads/\`{id}\`</a></code></li>
</ul>
     
     
        <br>
        <p class="published-on"><i>Published on July 28, 2021</i></p>
  </div>
</div>


Improving Leads API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 27, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="introducing-comments-API"></div>
        <div class="heading-text"><div id="introducing-comments-API" class="heading-anchor_backwardsCompatibility">
          </div>Introducing Comments API</div>
        <a aria-label="Skip link to Introducing Comments API" class="heading-anchor-icon fa fa-anchor" 
           href="#introducing-comments-API"></a></h3>
      
     <p>We have added brand new Comments endpoints to the <a href="https://developers.pipedrive.com/docs/api/v1/Notes">Notes</a> resource of the Pipedrive API.
      </p>
            <p><b>What is being added?</b></p>
    <p>The Comments API allows one to get, create, update and delete Comments for Notes.
      </p>
      <p>Comments can be added via the public API to existing Notes that are linked to Deals, Persons or Organizations. The User can edit and/or delete the comment(s) via the API if that specific comment was originally posted by the same User or if the User is an admin.
      </p>
      <p>The list of Comments under each Note can also be fetched if the User has permission to view the Note that is linked to the Deal, Person or Organization. 
      </p>
         <p><b>What is the Comments API useful for?</b></p>
      <p>The User can see, add, update and delete comments to Notes programmatically from one’s own applications. More information on the Comments feature can be found on the Pipedrive help center’s <a href="https://support.pipedrive.com/en/article/mentions-and-comments-beta">Mentions and Comments article</a>. 
      </p>
        <p><b>Here’s the list of the Comments API endpoints added:</b></p>
 <ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#getNoteComments" target="_self">GET /v1/notes/{id}/comments</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#getComment" target="_self">GET /v1/notes/{id}/comments/{commentId}</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#addNoteComment" target="_self">POST /v1/notes/{id}/comments</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#updateCommentForNote" target="_self">PUT /v1/notes/{id}/comments/{commentId}</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#deleteComment" target="_self">DELETE /v1/notes/{id}/comments/{commentId}</a></code></li>
      </ul>
      <p>Please note the OAuth scopes these endpoints have been added to: <code>deals:full</code>, <code>deals:read</code>, <code>contacts:full</code>, <code>contacts:read</code> (the same scopes as <a href="https://developers.pipedrive.com/docs/api/v1/Notes">the Notes API</a>).
        <p>
        <br>
      <p class="published-on"><i>Published on July 27, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 27, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="introducing-comments-API"></div>
        <div class="heading-text"><div id="introducing-comments-API" class="heading-anchor_backwardsCompatibility">
          </div>Introducing Comments API</div>
        <a aria-label="Skip link to Introducing Comments API" class="heading-anchor-icon fa fa-anchor" 
           href="#introducing-comments-API"></a></h3>
      
     <p>We have added brand new Comments endpoints to the <a href="https://developers.pipedrive.com/docs/api/v1/Notes">Notes</a> resource of the Pipedrive API.
      </p>
            <p><b>What is being added?</b></p>
    <p>The Comments API allows one to get, create, update and delete Comments for Notes.
      </p>
      <p>Comments can be added via the public API to existing Notes that are linked to Deals, Persons or Organizations. The User can edit and/or delete the comment(s) via the API if that specific comment was originally posted by the same User or if the User is an admin.
      </p>
      <p>The list of Comments under each Note can also be fetched if the User has permission to view the Note that is linked to the Deal, Person or Organization. 
      </p>
         <p><b>What is the Comments API useful for?</b></p>
      <p>The User can see, add, update and delete comments to Notes programmatically from one’s own applications. More information on the Comments feature can be found on the Pipedrive help center’s <a href="https://support.pipedrive.com/en/article/mentions-and-comments-beta">Mentions and Comments article</a>. 
      </p>
        <p><b>Here’s the list of the Comments API endpoints added:</b></p>
 <ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#getNoteComments" target="_self">GET /v1/notes/{id}/comments</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#getComment" target="_self">GET /v1/notes/{id}/comments/{commentId}</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#addNoteComment" target="_self">POST /v1/notes/{id}/comments</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#updateCommentForNote" target="_self">PUT /v1/notes/{id}/comments/{commentId}</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#deleteComment" target="_self">DELETE /v1/notes/{id}/comments/{commentId}</a></code></li>
      </ul>
      <p>Please note the OAuth scopes these endpoints have been added to: <code>deals:full</code>, <code>deals:read</code>, <code>contacts:full</code>, <code>contacts:read</code> (the same scopes as <a href="https://developers.pipedrive.com/docs/api/v1/Notes">the Notes API</a>).
        <p>
        <br>
      <p class="published-on"><i>Published on July 27, 2021</i></p>
  </div>
</div>


Introducing Comments API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 1, 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-postponed"></div>
        <div class="heading-text"><div id="permissionsets-API-breaking-changes-postponed" class="heading-anchor_backwardsCompatibility">
          </div>PermissionSets API breaking change postponed</div>
        <a aria-label="Skip link to PermissionSets API breaking change postponed" class="heading-anchor-icon fa fa-anchor" 
           href="#permissionsets-API-breaking-changes-postponed"></a></h3>

     <p>Note: If you are simply using our Pipedrive web app and don’t have any custom integrations that you (or a developer) has built, you should have nothing to worry about.<br>
       If you have, or someone else has, built a custom integration that you are currently using to enhance your Pipedrive experience, please forward this information to the relevant stakeholders.
      </p>
      <p>Recently on July 8, 2021, we announced <a href="https://developers.pipedrive.com/changelog/post/permissionsets-api-breaking-change">breaking changes for three PermissionSets API endpoints</a>.
      </p>
      <p>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> from July 26, 2021 to <b>September 1, 2021</b>.
      </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 23, 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">September 1, 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-postponed"></div>
        <div class="heading-text"><div id="permissionsets-API-breaking-changes-postponed" class="heading-anchor_backwardsCompatibility">
          </div>PermissionSets API breaking change postponed</div>
        <a aria-label="Skip link to PermissionSets API breaking change postponed" class="heading-anchor-icon fa fa-anchor" 
           href="#permissionsets-API-breaking-changes-postponed"></a></h3>

     <p>Note: If you are simply using our Pipedrive web app and don’t have any custom integrations that you (or a developer) has built, you should have nothing to worry about.<br>
       If you have, or someone else has, built a custom integration that you are currently using to enhance your Pipedrive experience, please forward this information to the relevant stakeholders.
      </p>
      <p>Recently on July 8, 2021, we announced <a href="https://developers.pipedrive.com/changelog/post/permissionsets-api-breaking-change">breaking changes for three PermissionSets API endpoints</a>.
      </p>
      <p>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> from July 26, 2021 to <b>September 1, 2021</b>.
      </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 23, 2021</i></p>
  </div>
</div>


PermissionSets API breaking change postponed

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 2, 2021</span>
    </div>
    <div class="change-area">
         <h3 class="header-scroll">
           <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="breaking-change-for-post-stages-endpoint"></div>
        <div class="heading-text"><div id="breaking-change-for-post-stages-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change for POST /stages endpoint</div>
        <a aria-label="Skip link to Breaking change for POST /stages endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-for-post-stages-endpoint"></a></h3>
           
         
      <p><b>What is going to change?</b></p>
      <p>The body parameter <code>name</code> of the <code><a href="https://developers.pipedrive.com/docs/api/v1/Stages#addStage">POST /stages</a></code> endpoint is a required property (both under the hood and in the documentation), but its existence is not validated when making the request. The endpoint returns <code>201</code> even when there is no value given to the name body parameter. 
      </p>
      <p>We are going to add validation to the <code>name</code> body parameter when requesting the <code><a href="https://developers.pipedrive.com/docs/api/v1/Stages#addStage">POST /stages</a></code> endpoint. When the value is not present, then the response error will be <code>400</code> “Bad request”.
      </p>

      <p><b>Why is it going to change?</b></p>
<p>The <code>name</code> body parameter should be required according to the documentation and common sense.
      </p>
      <p><b>Who is affected?</b></p>
<p>Anyone with functionality built on top of using the endpoint without specifying the stage <code>name</code>. Although it is marked as required in our <a href="https://developers.pipedrive.com/docs/api/v1/Stages#addStage">API Reference page documentation</a>, we encourage you to please check how you are using the endpoint.
      </p>
          <br>
      <p class="published-on"><i>Published on July 19, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 2, 2021</span>
    </div>
    <div class="change-area">
         <h3 class="header-scroll">
           <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="breaking-change-for-post-stages-endpoint"></div>
        <div class="heading-text"><div id="breaking-change-for-post-stages-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change for POST /stages endpoint</div>
        <a aria-label="Skip link to Breaking change for POST /stages endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-for-post-stages-endpoint"></a></h3>
           
         
      <p><b>What is going to change?</b></p>
      <p>The body parameter <code>name</code> of the <code><a href="https://developers.pipedrive.com/docs/api/v1/Stages#addStage">POST /stages</a></code> endpoint is a required property (both under the hood and in the documentation), but its existence is not validated when making the request. The endpoint returns <code>201</code> even when there is no value given to the name body parameter. 
      </p>
      <p>We are going to add validation to the <code>name</code> body parameter when requesting the <code><a href="https://developers.pipedrive.com/docs/api/v1/Stages#addStage">POST /stages</a></code> endpoint. When the value is not present, then the response error will be <code>400</code> “Bad request”.
      </p>

      <p><b>Why is it going to change?</b></p>
<p>The <code>name</code> body parameter should be required according to the documentation and common sense.
      </p>
      <p><b>Who is affected?</b></p>
<p>Anyone with functionality built on top of using the endpoint without specifying the stage <code>name</code>. Although it is marked as required in our <a href="https://developers.pipedrive.com/docs/api/v1/Stages#addStage">API Reference page documentation</a>, we encourage you to please check how you are using the endpoint.
      </p>
          <br>
      <p class="published-on"><i>Published on July 19, 2021</i></p>
  </div>
</div>


Breaking change for <code>POST /stages</code> endpoint

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 9, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="fix-in-post-pipelines-endpoint-documentation"></div>
        <div class="heading-text"><div id="fix-in-post-pipelines-endpoint-documentation" class="heading-anchor_backwardsCompatibility">
          </div>Fix in POST /pipelines endpoint documentation</div>
        <a aria-label="Skip link to Fix in POST /pipelines endpoint documentation" class="heading-anchor-icon fa fa-anchor" 
           href="#fix-in-post-pipelines-endpoint-documentation"></a></h3>
     
      <p>
        We had the <code>name</code> parameter not marked as required in the documentation of <code><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#addPipeline" targert="_self">POST /v1/pipelines</a></code> endpoint in our API Reference, but under the hood it has always been a required parameter. We have now corrected the documentation and assigned the “required”  flag to the <code>name</code> parameter.</p>
        <br>
      <p class="published-on"><i>Published on July 9, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

{"product": ["Developer Platform"], "features": ["API Reference]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">July 9, 2021</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="fix-in-post-pipelines-endpoint-documentation"></div>
        <div class="heading-text"><div id="fix-in-post-pipelines-endpoint-documentation" class="heading-anchor_backwardsCompatibility">
          </div>Fix in POST /pipelines endpoint documentation</div>
        <a aria-label="Skip link to Fix in POST /pipelines endpoint documentation" class="heading-anchor-icon fa fa-anchor" 
           href="#fix-in-post-pipelines-endpoint-documentation"></a></h3>
     
      <p>
        We had the <code>name</code> parameter not marked as required in the documentation of <code><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#addPipeline" targert="_self">POST /v1/pipelines</a></code> endpoint in our API Reference, but under the hood it has always been a required parameter. We have now corrected the documentation and assigned the “required”  flag to the <code>name</code> parameter.</p>
        <br>
      <p class="published-on"><i>Published on July 9, 2021</i></p>
  </div>
</div>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog