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


Fix in <code>POST /pipelines</code> endpoint documentation

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


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


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog