<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 1, 2020</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-parameter-in-oauth-/oauth/token/-responses"></div>
        <div class="heading-text"><div id="new-parameter-in-oauth-/oauth/token/-responses" class="heading-anchor_backwardsCompatibility">
          </div>New parameter in OAuth <code>/oauth/token</code> responses</div>
        <a aria-label="Skip link to New parameter in OAuth /oauth/token responses" class="heading-anchor-icon fa fa-anchor" 
           href="#new-parameter-in-oauth-/oauth/token/-responses"></a></h3>
      
      
      <p><b>What will change?</b></p>
<p>We have added a new parameter <code>api_domain</code> to OAuth <code>/oauth/token</code> responses. </p>

<p>For now, only the apps created <b>on</b> or <b>after February 20, 2020</b> will see a new parameter in the OAuth <code>/oauth/token</code> response.
</p>
      
<p>
<b>On June 1, 2020</b>, the code will <b>automatically</b> start sending the new parameter to <b>all requests</b>, i.e. apps created before February 20, 2020 will also start seeing the new parameter in the OAuth <code>/oauth/token</code> response. If you are strictly checking the shape of the response, please update your code to take the new parameter into account.
</p>
      
      <p><b>Why?</b></p>
      
<p>Until now (and because we ask you to use <code>https://companydomain.pipedrive.com</code> domains for making API requests), in order to find out the <code>company_domain</code>, you had to get the OAuth tokens first, make a request to <code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getCurrentUser">/users/me</a></code> endpoint and store it on your side. Also, the <code>company_domain</code> can change so you had to make additional request to <code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getCurrentUser">/users/me</a></code> every once in a while.</p>
      
  <p>But with this change you do not have to do that anymore, because you will now receive up-to-date <code>company_domain</code> every time you make the initial request to get the tokens or when you refresh a token.</p>
      
      <p>The current response:</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">"access_token"</span>: <span class="cm-string">"53:179:6317ef33a9fb0c4d604ce0695dad44a12bad44c9"</span>,
    <span class="cm-property">"token_type"</span>: <span class="cm-string">"Bearer"</span>,
    <span class="cm-property">"expires_in"</span>: <span class="cm-number">3599</span>,
    <span class="cm-property">"refresh_token"</span>: <span class="cm-string">"53:179:5de81994d77491d22bc10eab3bc0810f84864297"</span>,
    <span class="cm-property">"scope"</span>: <span class="cm-string">"base,deals:full,contacts:read"</span>
}
</div></code></pre></div></div>
      
      <p>The new response with the added <code>api_domain</code> parameter:</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">"access_token"</span>: <span class="cm-string">"53:179:6317ef33a9fb0c4d604ce0695dad44a12bad44c9"</span>,
    <span class="cm-property">"token_type"</span>: <span class="cm-string">"Bearer"</span>,
    <span class="cm-property">"expires_in"</span>: <span class="cm-number">3599</span>,
    <span class="cm-property">"refresh_token"</span>: <span class="cm-string">"53:179:5de81994d77491d22bc10eab3bc0810f84864297"</span>,
    <span class="cm-property">"scope"</span>: <span class="cm-string">"base,deals:full,contacts:read"</span>,
    <span class="cm-property">"api_domain"</span>: <span class="cm-string">"https://mycompanydomain.pipedrive.com"</span>
}
</div></code></pre></div></div>

      <p><b>Who is affected?</b></p>
 <p>Any app created before February 20, 2020 with functionality built on top of the previous behavior need to <b>alter their code by June 1, 2020</b>.</p>
      <p>Any apps created on or after February 20, 2020 will already see the new parameter in the OAuth <code>/oauth/token/</code> response and do not need to alter anything concerning this change.</p>
      
       <p class="published-on"><i>Published on February 21, 2020</i></p>
    </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 1, 2020</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-parameter-in-oauth-/oauth/token/-responses"></div>
        <div class="heading-text"><div id="new-parameter-in-oauth-/oauth/token/-responses" class="heading-anchor_backwardsCompatibility">
          </div>New parameter in OAuth <code>/oauth/token</code> responses</div>
        <a aria-label="Skip link to New parameter in OAuth /oauth/token responses" class="heading-anchor-icon fa fa-anchor" 
           href="#new-parameter-in-oauth-/oauth/token/-responses"></a></h3>
      
      
      <p><b>What will change?</b></p>
<p>We have added a new parameter <code>api_domain</code> to OAuth <code>/oauth/token</code> responses. </p>

<p>For now, only the apps created <b>on</b> or <b>after February 20, 2020</b> will see a new parameter in the OAuth <code>/oauth/token</code> response.
</p>
      
<p>
<b>On June 1, 2020</b>, the code will <b>automatically</b> start sending the new parameter to <b>all requests</b>, i.e. apps created before February 20, 2020 will also start seeing the new parameter in the OAuth <code>/oauth/token</code> response. If you are strictly checking the shape of the response, please update your code to take the new parameter into account.
</p>
      
      <p><b>Why?</b></p>
      
<p>Until now (and because we ask you to use <code>https://companydomain.pipedrive.com</code> domains for making API requests), in order to find out the <code>company_domain</code>, you had to get the OAuth tokens first, make a request to <code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getCurrentUser">/users/me</a></code> endpoint and store it on your side. Also, the <code>company_domain</code> can change so you had to make additional request to <code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getCurrentUser">/users/me</a></code> every once in a while.</p>
      
  <p>But with this change you do not have to do that anymore, because you will now receive up-to-date <code>company_domain</code> every time you make the initial request to get the tokens or when you refresh a token.</p>
      
      <p>The current response:</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">"access_token"</span>: <span class="cm-string">"53:179:6317ef33a9fb0c4d604ce0695dad44a12bad44c9"</span>,
    <span class="cm-property">"token_type"</span>: <span class="cm-string">"Bearer"</span>,
    <span class="cm-property">"expires_in"</span>: <span class="cm-number">3599</span>,
    <span class="cm-property">"refresh_token"</span>: <span class="cm-string">"53:179:5de81994d77491d22bc10eab3bc0810f84864297"</span>,
    <span class="cm-property">"scope"</span>: <span class="cm-string">"base,deals:full,contacts:read"</span>
}
</div></code></pre></div></div>
      
      <p>The new response with the added <code>api_domain</code> parameter:</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">"access_token"</span>: <span class="cm-string">"53:179:6317ef33a9fb0c4d604ce0695dad44a12bad44c9"</span>,
    <span class="cm-property">"token_type"</span>: <span class="cm-string">"Bearer"</span>,
    <span class="cm-property">"expires_in"</span>: <span class="cm-number">3599</span>,
    <span class="cm-property">"refresh_token"</span>: <span class="cm-string">"53:179:5de81994d77491d22bc10eab3bc0810f84864297"</span>,
    <span class="cm-property">"scope"</span>: <span class="cm-string">"base,deals:full,contacts:read"</span>,
    <span class="cm-property">"api_domain"</span>: <span class="cm-string">"https://mycompanydomain.pipedrive.com"</span>
}
</div></code></pre></div></div>

      <p><b>Who is affected?</b></p>
 <p>Any app created before February 20, 2020 with functionality built on top of the previous behavior need to <b>alter their code by June 1, 2020</b>.</p>
      <p>Any apps created on or after February 20, 2020 will already see the new parameter in the OAuth <code>/oauth/token/</code> response and do not need to alter anything concerning this change.</p>
      
       <p class="published-on"><i>Published on February 21, 2020</i></p>
    </div>
</div>


New parameter in OAuth <code>/oauth/token</code> responses

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

       
      <p> We have added a brand new <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams" target="_self">Teams</a></code> resource. Teams allow sales people to form groups of users within the organization for more efficient management.</p>
<p>The new <code>Teams</code> resource includes the following endpoints:</p>
<ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/get_teams" target="_self">GET /teams</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/get_teams_id" target="_self">GET /teams/{id}</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/get_teams_id_users" target="_self">GET /teams/{id}/users</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/get_teams_user_id" target="_self">GET /teams/user/{id}</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/post_teams" target="_self">POST /teams</a></code></li>
   <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/post_teams_id_users" target="_self">POST /teams/{id}/users</a></code></li>
   <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/put_teams_id" target="_self">PUT /teams/{id}</a></code></li>
    <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/delete_teams_id_users" target="_self">DELETE /teams/{id}/users</a></code></li>
  </ul>

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

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 10, 2019</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-teams-resource"></div>
        <div class="heading-text"><div id="new-teams-resource" class="heading-anchor_backwardsCompatibility">
          </div>New Teams resource</div>
        <a aria-label="Skip link to New Teams resource" class="heading-anchor-icon fa fa-anchor" 
           href="#new-teams-resource"></a></h3>

       
      <p> We have added a brand new <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams" target="_self">Teams</a></code> resource. Teams allow sales people to form groups of users within the organization for more efficient management.</p>
<p>The new <code>Teams</code> resource includes the following endpoints:</p>
<ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/get_teams" target="_self">GET /teams</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/get_teams_id" target="_self">GET /teams/{id}</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/get_teams_id_users" target="_self">GET /teams/{id}/users</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/get_teams_user_id" target="_self">GET /teams/user/{id}</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/post_teams" target="_self">POST /teams</a></code></li>
   <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/post_teams_id_users" target="_self">POST /teams/{id}/users</a></code></li>
   <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/put_teams_id" target="_self">PUT /teams/{id}</a></code></li>
    <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Teams/delete_teams_id_users" target="_self">DELETE /teams/{id}/users</a></code></li>
  </ul>

       <p class="published-on"><i>Published on December 10, 2019</i></p>
    </div>
</div>


New Teams resource

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label"><b>Effective from:</b></span><br>
        <span class="from-date"><b>November 29, 2019</b></span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-goals-resource"></div>
        <div class="heading-text"><div id="new-goals-resource" class="heading-anchor_backwardsCompatibility">
          </div>New Goals resource</div>
        <a aria-label="Skip link to Improved protection of user data " class="heading-anchor-icon fa fa-anchor" 
           href="#new-goals-resource"></a></h3>

        
      <p> We have added a brand new <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals" target="_self">Goals</a></code> resource. Goals help sales teams meet their sales targets.</p>
<p>The new <code>Goals</code> resource includes the following endpoints:</p>
<ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals/get_goals_find" target="_self">GET /goals/find</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals/get_goals_id_results" target="_self">GET /goals/{id}/results</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals/post_goals" target="_self">POST /goals</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals/put_goals_id" target="_self">PUT /goals/{id}</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals/delete_goals_id" target="_self">DELETE /goals/{id}</a></code></li></ul>

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

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label"><b>Effective from:</b></span><br>
        <span class="from-date"><b>November 29, 2019</b></span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-goals-resource"></div>
        <div class="heading-text"><div id="new-goals-resource" class="heading-anchor_backwardsCompatibility">
          </div>New Goals resource</div>
        <a aria-label="Skip link to Improved protection of user data " class="heading-anchor-icon fa fa-anchor" 
           href="#new-goals-resource"></a></h3>

        
      <p> We have added a brand new <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals" target="_self">Goals</a></code> resource. Goals help sales teams meet their sales targets.</p>
<p>The new <code>Goals</code> resource includes the following endpoints:</p>
<ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals/get_goals_find" target="_self">GET /goals/find</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals/get_goals_id_results" target="_self">GET /goals/{id}/results</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals/post_goals" target="_self">POST /goals</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals/put_goals_id" target="_self">PUT /goals/{id}</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Goals/delete_goals_id" target="_self">DELETE /goals/{id}</a></code></li></ul>

      
       <p class="published-on"><i>Published on November 29, 2019</i></p>
    </div>
</div>


New Goals resource

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 17, 2019</span>
    </div>
    
   <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-parameter-in-notes-post-and-put-endpoints"></div>
        <div class="heading-text"><div id="new-parameter-in-notes-post-and-put-endpoints" class="heading-anchor_backwardsCompatibility">
          </div>New parameter in Notes <code>POST</code> and <code>PUT</code> endpoints</div>
        <a aria-label="Skip link to New parameter in Notes POST and PUT endpoints " class="heading-anchor-icon fa fa-anchor" 
           href="#new-parameter-in-notes-post-and-put-endpoints"></a></h3>

         
      <p> We have added a new parameter <code>user_id</code> to the <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Notes/post_notes">POST /notes</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Notes/put_notes_id">PUT /notes/{id}</a></code> endpoints.
</p>
      <p>By inserting the ID of a user into the <code>user_id</code> parameter when making requests against the following endpoints, you can now choose or change the author of a note:  </p>
      
      <ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Notes/post_notes">POST /notes</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Notes/put_notes_id">PUT /notes/{id}</a></code></li></ul><br>
      
      
      <p>For example, this <code>user_id</code> parameter might come in handy when importing data to Pipedrive. Please keep in mind that only an <b>admin</b> can change the author. </p>
      
       <p class="published-on"><i>Published on October 17, 2019</i></p>
    </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 17, 2019</span>
    </div>
    
   <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-parameter-in-notes-post-and-put-endpoints"></div>
        <div class="heading-text"><div id="new-parameter-in-notes-post-and-put-endpoints" class="heading-anchor_backwardsCompatibility">
          </div>New parameter in Notes <code>POST</code> and <code>PUT</code> endpoints</div>
        <a aria-label="Skip link to New parameter in Notes POST and PUT endpoints " class="heading-anchor-icon fa fa-anchor" 
           href="#new-parameter-in-notes-post-and-put-endpoints"></a></h3>

         
      <p> We have added a new parameter <code>user_id</code> to the <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Notes/post_notes">POST /notes</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Notes/put_notes_id">PUT /notes/{id}</a></code> endpoints.
</p>
      <p>By inserting the ID of a user into the <code>user_id</code> parameter when making requests against the following endpoints, you can now choose or change the author of a note:  </p>
      
      <ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Notes/post_notes">POST /notes</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Notes/put_notes_id">PUT /notes/{id}</a></code></li></ul><br>
      
      
      <p>For example, this <code>user_id</code> parameter might come in handy when importing data to Pipedrive. Please keep in mind that only an <b>admin</b> can change the author. </p>
      
       <p class="published-on"><i>Published on October 17, 2019</i></p>
    </div>
</div>


New parameter in Notes <code>POST</code> and <code>PUT</code> endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 7, 2019</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="breaking-change-in-/searchresults-and-/organizations/find-endpoints"></div>
        <div class="heading-text"><div id="breaking-change-in-/searchresults-and-/organizations/find-endpoints" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in <code>/searchResults</code> and <code>/organizations/find</code> endpoints</div>
        <a aria-label="Skip link to Breaking change in /searchResults and /organizations/find endpoints" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-/searchresults-and-/organizations/find-endpoints"></a></h3>
      
        
      <p><b>Endpoints directly affected:</b></p>
        <ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/SearchResults/get_searchResults">GET /searchResults</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Organizations/get_organizations_find" target="_self">GET /organizations/find</a></code></li></ul><br>
      <p><b>What will change?</b></p>
<p>
When the <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/SearchResults/get_searchResults">/searchResults</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Organizations/get_organizations_find" target="_self">/organizations/find</a></code> endpoints return an organization with no details, the organization details field will return an empty object <code>{}</code> instead of an empty string <code>""</code>.
</p>
      <p><b>Why?</b></p>
  <p>This change will make endpoint responses more consistent by forcing the returned organization details field to always be an object. </p><p>The responses will be more consistent with results that do have organization details, which currently have the following format:  </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">"org_address"</span>: <span class="cm-string">"organization's address"</span>
}
</div></code></pre></div></div>
      <p><b>Who is affected?</b></p>
 <p> Any integration with  functionality built on top of the previous behavior might need to alter their code.</p>
      
       <p class="published-on"><i>Published on September 23, 2019</i></p>
    </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 7, 2019</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="breaking-change-in-/searchresults-and-/organizations/find-endpoints"></div>
        <div class="heading-text"><div id="breaking-change-in-/searchresults-and-/organizations/find-endpoints" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in <code>/searchResults</code> and <code>/organizations/find</code> endpoints</div>
        <a aria-label="Skip link to Breaking change in /searchResults and /organizations/find endpoints" class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-/searchresults-and-/organizations/find-endpoints"></a></h3>
      
        
      <p><b>Endpoints directly affected:</b></p>
        <ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/SearchResults/get_searchResults">GET /searchResults</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Organizations/get_organizations_find" target="_self">GET /organizations/find</a></code></li></ul><br>
      <p><b>What will change?</b></p>
<p>
When the <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/SearchResults/get_searchResults">/searchResults</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Organizations/get_organizations_find" target="_self">/organizations/find</a></code> endpoints return an organization with no details, the organization details field will return an empty object <code>{}</code> instead of an empty string <code>""</code>.
</p>
      <p><b>Why?</b></p>
  <p>This change will make endpoint responses more consistent by forcing the returned organization details field to always be an object. </p><p>The responses will be more consistent with results that do have organization details, which currently have the following format:  </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">"org_address"</span>: <span class="cm-string">"organization's address"</span>
}
</div></code></pre></div></div>
      <p><b>Who is affected?</b></p>
 <p> Any integration with  functionality built on top of the previous behavior might need to alter their code.</p>
      
       <p class="published-on"><i>Published on September 23, 2019</i></p>
    </div>
</div>


Breaking change in <code>/searchResults</code> and <code>/organizations/find</code> endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 17, 2019</span>
    </div>
<div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="removal-of-access-level-feature"></div>
        <div class="heading-text"><div id="removal-of-access-level-feature" class="heading-anchor_backwardsCompatibility">
          </div>Removal of <code>access_level</code> feature </div>
        <a aria-label="Skip link to Removal of access_level feature " class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-access-level-feature"></a></h3>
    
        
      <p>We have chosen to delete the <code>access_level</code> feature due to it being an older and not fully implemented feature. </p>
      <p>It was previously available in the following endpoints under Roles:</p>
<ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Roles/get_roles_id_settings" target="_self">GET /roles/{id}/settings</a></code></li><li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Roles/post_roles_id_settings" target="_self">POST    /roles/{id}/settings</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Roles/get_roles_id" target="_self">GET    /roles/{id}</a></code></li></ul>
<p>And there was a possibility to change it separately under Deal, Organization, Person, Product:</p>
<ul>
<li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Deals/get_deals_id_permittedUsers" target="_self">GET /deals/{id}/permittedUsers</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Organizations/get_organizations_id_permittedUsers" target="_self">GET    /organizations/{id}/permittedUsers</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Persons/get_persons_id_permittedUsers" target="_self">GET    /persons/{id}/permittedUsers</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Products/get_products_id_permittedUsers" target="_self">GET    /products/{id}/permittedUsers</a></code> </li></ul>

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

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 17, 2019</span>
    </div>
<div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="removal-of-access-level-feature"></div>
        <div class="heading-text"><div id="removal-of-access-level-feature" class="heading-anchor_backwardsCompatibility">
          </div>Removal of <code>access_level</code> feature </div>
        <a aria-label="Skip link to Removal of access_level feature " class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-access-level-feature"></a></h3>
    
        
      <p>We have chosen to delete the <code>access_level</code> feature due to it being an older and not fully implemented feature. </p>
      <p>It was previously available in the following endpoints under Roles:</p>
<ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Roles/get_roles_id_settings" target="_self">GET /roles/{id}/settings</a></code></li><li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Roles/post_roles_id_settings" target="_self">POST    /roles/{id}/settings</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Roles/get_roles_id" target="_self">GET    /roles/{id}</a></code></li></ul>
<p>And there was a possibility to change it separately under Deal, Organization, Person, Product:</p>
<ul>
<li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Deals/get_deals_id_permittedUsers" target="_self">GET /deals/{id}/permittedUsers</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Organizations/get_organizations_id_permittedUsers" target="_self">GET    /organizations/{id}/permittedUsers</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Persons/get_persons_id_permittedUsers" target="_self">GET    /persons/{id}/permittedUsers</a></code></li><li><code> <a href="https://developers.pipedrive.com/docs/api/v1/#!/Products/get_products_id_permittedUsers" target="_self">GET    /products/{id}/permittedUsers</a></code> </li></ul>

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


Removal of <code>access_level</code> feature

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 3, 2019</span>
    </div>
<div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="bugfix-in-/activities-endpoint"></div>
        <div class="heading-text"><div id="bugfix-in-/activities-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Bugfix in <code>/activities</code> endpoint</div>
        <a aria-label="Skip link to Bugfix in <code>/activities</code> endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#bugfix-in-/activities-endpoint"></a></h3>
        
      <p>In <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Activities">/activities</a></code> endpoint,
        additional information about pagination will now return correct values for the <code>more_items_in_collection</code> when the <code>related_objects=0</code> parameter is passed with the request.</p>
       <p class="published-on"><i>Published on September 3, 2019</i></p>
    </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 3, 2019</span>
    </div>
<div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="bugfix-in-/activities-endpoint"></div>
        <div class="heading-text"><div id="bugfix-in-/activities-endpoint" class="heading-anchor_backwardsCompatibility">
          </div>Bugfix in <code>/activities</code> endpoint</div>
        <a aria-label="Skip link to Bugfix in <code>/activities</code> endpoint" class="heading-anchor-icon fa fa-anchor" 
           href="#bugfix-in-/activities-endpoint"></a></h3>
        
      <p>In <code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Activities">/activities</a></code> endpoint,
        additional information about pagination will now return correct values for the <code>more_items_in_collection</code> when the <code>related_objects=0</code> parameter is passed with the request.</p>
       <p class="published-on"><i>Published on September 3, 2019</i></p>
    </div>
</div>


Bugfix in <code>/activities</code> endpoint

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 23, 2019</span>
    </div>
     <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="breaking-change-in-the-JSON-response-structure-of-the-Delete-Person-webhook"></div>
        <div class="heading-text"><div id="breaking-change-in-the-JSON-response-structure-of-the-Delete-Person-webhook" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in the JSON response structure of the Delete Person webhook</div>
        <a aria-label="Skip link to Breaking change in the JSON response structure of the Delete Person webhook " class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-the-JSON-response-structure-of-the-Delete-Person-webhook"></a></h3>
       
         
      <p><b>What?</b></p>
<p>We will be introducing a breaking change in the JSON response structure of the Delete Person webhook.</p>
<p>Currently the data for a Delete Person webhook is incomplete. For example, if a user has saved more than one email/phone nr on a Contact, then only the primary email/phone nr. will appear in the webhook data. Because of this, we will change the property type from a string to an array and add additional values (e.g. secondary email/phone nr) into the array when they are present.</p>
 
 <p><b>Why?</b></p>
<p>If our customers remove a Person, they can then use webhook data to delete the same information on their end. We would like to make sure when information is removed from Pipedrive, it can also be seamlessly removed from our customers’ databases.</p>
<p><b>Who is affected?</b></p>
<p>Anyone who has set up a webhook for a Person Delete event. If you or your team has built functionality on top of a previous response structure, then please make sure your code is changed accordingly.</p>
       <p class="published-on"><i>Published on August 23, 2019</i></p>
    </div>
</div>
`}</HTMLBlock>


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 23, 2019</span>
    </div>
     <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="breaking-change-in-the-JSON-response-structure-of-the-Delete-Person-webhook"></div>
        <div class="heading-text"><div id="breaking-change-in-the-JSON-response-structure-of-the-Delete-Person-webhook" class="heading-anchor_backwardsCompatibility">
          </div>Breaking change in the JSON response structure of the Delete Person webhook</div>
        <a aria-label="Skip link to Breaking change in the JSON response structure of the Delete Person webhook " class="heading-anchor-icon fa fa-anchor" 
           href="#breaking-change-in-the-JSON-response-structure-of-the-Delete-Person-webhook"></a></h3>
       
         
      <p><b>What?</b></p>
<p>We will be introducing a breaking change in the JSON response structure of the Delete Person webhook.</p>
<p>Currently the data for a Delete Person webhook is incomplete. For example, if a user has saved more than one email/phone nr on a Contact, then only the primary email/phone nr. will appear in the webhook data. Because of this, we will change the property type from a string to an array and add additional values (e.g. secondary email/phone nr) into the array when they are present.</p>
 
 <p><b>Why?</b></p>
<p>If our customers remove a Person, they can then use webhook data to delete the same information on their end. We would like to make sure when information is removed from Pipedrive, it can also be seamlessly removed from our customers’ databases.</p>
<p><b>Who is affected?</b></p>
<p>Anyone who has set up a webhook for a Person Delete event. If you or your team has built functionality on top of a previous response structure, then please make sure your code is changed accordingly.</p>
       <p class="published-on"><i>Published on August 23, 2019</i></p>
    </div>
</div>


Breaking change in the JSON response structure of the Delete Person webhook

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 24, 2019</span>
    </div>
     <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="websocket-functionality-deprecation"></div>
        <div class="heading-text"><div id="websocket-functionality-deprecation" class="heading-anchor_backwardsCompatibility">
          </div>Websocket functionality deprecation </div>
        <a aria-label="Skip link to Websocket functionality deprecation " class="heading-anchor-icon fa fa-anchor" 
           href="#websocket-functionality-deprecation"></a></h3>

       <p>We are going to deprecate the websocket usage in client-nodejs for third-party developers <a href="https://github.com/pipedrive/client-nodejs/pull/94">https://github.com/pipedrive/client-nodejs/pull/94</a>.</p>  
      <p>The current library will stop working on September 24, 2019. In case of any dependency affected by this deprecation, please keep in mind this is <b>a breaking change</b>. It is very urgent for you to update your library and migrate to using webhooks.</p>
     
       <p class="published-on"><i>Published on July 30, 2019</i></p>
    </div>
</div>
`}</HTMLBlock>

{"product": ["Developer Platform"], "features": ["SDK"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 24, 2019</span>
    </div>
     <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="websocket-functionality-deprecation"></div>
        <div class="heading-text"><div id="websocket-functionality-deprecation" class="heading-anchor_backwardsCompatibility">
          </div>Websocket functionality deprecation </div>
        <a aria-label="Skip link to Websocket functionality deprecation " class="heading-anchor-icon fa fa-anchor" 
           href="#websocket-functionality-deprecation"></a></h3>

       <p>We are going to deprecate the websocket usage in client-nodejs for third-party developers <a href="https://github.com/pipedrive/client-nodejs/pull/94">https://github.com/pipedrive/client-nodejs/pull/94</a>.</p>  
      <p>The current library will stop working on September 24, 2019. In case of any dependency affected by this deprecation, please keep in mind this is <b>a breaking change</b>. It is very urgent for you to update your library and migrate to using webhooks.</p>
     
       <p class="published-on"><i>Published on July 30, 2019</i></p>
    </div>
</div>


Websocket functionality deprecation

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 15, 2019</span>
    </div>
 <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="change-in-how-future-activities-behave"></div>
        <div class="heading-text"><div id="change-in-how-future-activities-behave" class="heading-anchor_backwardsCompatibility">
          </div>Change in how future Activities behave</div>
        <a aria-label="Skip link to Change in how future Activities behave" class="heading-anchor-icon fa fa-anchor" 
           href="#change-in-how-future-activities-behave"></a></h3>
   
       
      <p>
        Endpoints directly affected: </p>
      <ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Activities/put_activities_id" target="_self">PUT /activities/{id}</code></a></li><li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Activities/get_activities" target="_self">GET /activities</code></a></li></ul>
            <br>
      <p><b>What will change?</b></p>
<p>Currently, if future activities (<code>due_date</code> and <code>due_time</code> in the future) have been marked as done, those activities’ <code>due_date</code> and <code>due_time</code> have been overwritten with the <code>marked_as_done_time</code>. This behaviour will be changed.
Starting from August 15, the <code>due_date</code> and <code>due_time</code> will remain as they were initially set, different from the <code>marked_as_done_time</code>.</p>

<p><b>Why?</b></p>
<p>We are working on improving Pipedrive’s integrations with external calendars and this is a necessary change. Overall, this was an unexpected behaviour and we are bringing it into line with how calendars usually behave.</p>

<p><b>Who is affected?</b></p>
<p>Anyone creating statistics based on activities.<br>
Anyone marking future activities as done.<br>
  <br>
If there is functionality built on top of the previous behaviour, it will have to be altered.</p>
      <p class="published-on"><i>Published on July 15, 2019</i></p>
    </div>
</div>
`}</HTMLBlock>


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 15, 2019</span>
    </div>
 <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="change-in-how-future-activities-behave"></div>
        <div class="heading-text"><div id="change-in-how-future-activities-behave" class="heading-anchor_backwardsCompatibility">
          </div>Change in how future Activities behave</div>
        <a aria-label="Skip link to Change in how future Activities behave" class="heading-anchor-icon fa fa-anchor" 
           href="#change-in-how-future-activities-behave"></a></h3>
   
       
      <p>
        Endpoints directly affected: </p>
      <ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Activities/put_activities_id" target="_self">PUT /activities/{id}</code></a></li><li><code><a href="https://developers.pipedrive.com/docs/api/v1/#!/Activities/get_activities" target="_self">GET /activities</code></a></li></ul>
            <br>
      <p><b>What will change?</b></p>
<p>Currently, if future activities (<code>due_date</code> and <code>due_time</code> in the future) have been marked as done, those activities’ <code>due_date</code> and <code>due_time</code> have been overwritten with the <code>marked_as_done_time</code>. This behaviour will be changed.
Starting from August 15, the <code>due_date</code> and <code>due_time</code> will remain as they were initially set, different from the <code>marked_as_done_time</code>.</p>

<p><b>Why?</b></p>
<p>We are working on improving Pipedrive’s integrations with external calendars and this is a necessary change. Overall, this was an unexpected behaviour and we are bringing it into line with how calendars usually behave.</p>

<p><b>Who is affected?</b></p>
<p>Anyone creating statistics based on activities.<br>
Anyone marking future activities as done.<br>
  <br>
If there is functionality built on top of the previous behaviour, it will have to be altered.</p>
      <p class="published-on"><i>Published on July 15, 2019</i></p>
    </div>
</div>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog