<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">February 28, 2022</span>
    </div>
    <div class="change-area">
      <p>1. We updated the description of the <code>visible_to</code> body parameter for the following endpoints:
</p>
      <ul>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_self">POST /deals</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_self">PUT /deals/{id}</a></code></li>
               <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead" target="_self">POST /leads</a></code></li>
                  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead" target="_self">PATCH /leads/{id}</a></code></li>
                     <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization" target="_self">POST /organizations</a></code></li>
                        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#updateOrganization" target="_self">PUT /organizations/{id}</a></code></li>
                           <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#addPerson" target="_self">POST /persons</a></code></li>
                              <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#updatePerson" target="_self">PUT /persons/{id}</a></code></li>
                                 <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_self">POST /products</a></code></li>
                                    <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_self">PUT /products/{id}</a></code></li>
                                      
      </ul>
      <p>Similarly, the description of the <code>value</code> body parameter was updated for the <code><a href="hhttps://developers.pipedrive.com/docs/api/v1/Roles#addOrUpdateRoleSetting" target="_self">POST /roles/{id}/settings</a></code> endpoint.
</p>
      
      <p>Possible values for the visibility setting are <code>1</code>, <code>3</code>, <code>5</code> and <code>7</code>:</p>
      <p><b>Essential / Advanced plan</b></p>
      <div class="rdmd-table"><div class="rdmd-table-inner"><table><thead><tr><th style="text-align:left"><p>Value</p></th><th style="text-align:left"><p>Description</p></th></tr></thead><tbody><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">1</span></code></p></td><td style="text-align:left"><p>Owner &amp; followers</p></td></tr><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">3</span></code></p></td><td style="text-align:left"><p>Entire company</p></td></tr></tbody></table></div></div>
      <br>
      <p><b>Professional / Enterprise plan</b></p>
      <div class="rdmd-table"><div class="rdmd-table-inner"><table><thead><tr><th style="text-align:left"><p>Value</p></th><th style="text-align:left"><p>Description</p></th></tr></thead><tbody><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">1</span></code></p></td><td style="text-align:left"><p>Owner only</p></td></tr><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">3</span></code></p></td><td style="text-align:left"><p>Owner's visibility group</p></td></tr><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">5</span></code></p></td><td style="text-align:left"><p>Owner's visibility group and sub-groups</p></td></tr><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">7</span></code></p></td><td style="text-align:left"><p>Entire company</p></td></tr></tbody></table></div></div>
      <br>
      <p>2. We removed the deprecated <code>write_flag</code> property from the responses of all Mailbox endpoints:</p>
      <ul>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#getMailMessage" target="_self">GET /mailbox/mailMessages/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#getMailThreads" target="_self">GET /mailbox/mailThreads</a></code></li>
          <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#getMailThread" target="_self">GET /mailbox/mailThreads/{id}</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#getMailThreadMessages" target="_self">GET /mailbox/mailThreads/{id}/mailMessages</a></code></li>
              <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#updateMailThreadDetails" target="_self">PUT /mailbox/mailThreads/{id}</a></code></li>
                <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#deleteMailThread" target="_self">DELETE /mailbox/mailThreads/{id}</a></code></li>
      </ul>
      <br>
      <p>3. We documented <code>required</code> labels for the body parameters of the following endpoints:
</p><ul>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_self">POST /deals/{id}/products</a></code> - <code>item_price</code> and <code>quantity</code> are required
</li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_self">PUT /deals/{id}/products/{product_attachment_id}</a></code>- <code>item_price</code> and <code>quantity</code> are required
</li>
          <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#addNote" target="_self">POST /notes</a></code> - <code>content</code> is required
</li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization" target="_self">POST /organizations</a></code> - <code>name</code> is required
</li>
              <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#addPerson" target="_self">POST /persons</a></code> -<code> name</code> is required
</li>
                <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#deletePersons" target="_self">DELETE /persons</a></code> - <code>ids</code> is required</li>
                  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_self">POST /products</a></code> -<code> name</code> is required</li>
                 
      </ul>
      </div>
</div>
`}</HTMLBlock>


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">February 28, 2022</span>
    </div>
    <div class="change-area">
      <p>1. We updated the description of the <code>visible_to</code> body parameter for the following endpoints:
</p>
      <ul>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_self">POST /deals</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="_self">PUT /deals/{id}</a></code></li>
               <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#addLead" target="_self">POST /leads</a></code></li>
                  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead" target="_self">PATCH /leads/{id}</a></code></li>
                     <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization" target="_self">POST /organizations</a></code></li>
                        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#updateOrganization" target="_self">PUT /organizations/{id}</a></code></li>
                           <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#addPerson" target="_self">POST /persons</a></code></li>
                              <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#updatePerson" target="_self">PUT /persons/{id}</a></code></li>
                                 <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_self">POST /products</a></code></li>
                                    <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_self">PUT /products/{id}</a></code></li>
                                      
      </ul>
      <p>Similarly, the description of the <code>value</code> body parameter was updated for the <code><a href="hhttps://developers.pipedrive.com/docs/api/v1/Roles#addOrUpdateRoleSetting" target="_self">POST /roles/{id}/settings</a></code> endpoint.
</p>
      
      <p>Possible values for the visibility setting are <code>1</code>, <code>3</code>, <code>5</code> and <code>7</code>:</p>
      <p><b>Essential / Advanced plan</b></p>
      <div class="rdmd-table"><div class="rdmd-table-inner"><table><thead><tr><th style="text-align:left"><p>Value</p></th><th style="text-align:left"><p>Description</p></th></tr></thead><tbody><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">1</span></code></p></td><td style="text-align:left"><p>Owner &amp; followers</p></td></tr><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">3</span></code></p></td><td style="text-align:left"><p>Entire company</p></td></tr></tbody></table></div></div>
      <br>
      <p><b>Professional / Enterprise plan</b></p>
      <div class="rdmd-table"><div class="rdmd-table-inner"><table><thead><tr><th style="text-align:left"><p>Value</p></th><th style="text-align:left"><p>Description</p></th></tr></thead><tbody><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">1</span></code></p></td><td style="text-align:left"><p>Owner only</p></td></tr><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">3</span></code></p></td><td style="text-align:left"><p>Owner's visibility group</p></td></tr><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">5</span></code></p></td><td style="text-align:left"><p>Owner's visibility group and sub-groups</p></td></tr><tr><td style="text-align:left"><p><code class="rdmd-code lang- theme-light" data-lang="" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><span class="cm-s-neo">7</span></code></p></td><td style="text-align:left"><p>Entire company</p></td></tr></tbody></table></div></div>
      <br>
      <p>2. We removed the deprecated <code>write_flag</code> property from the responses of all Mailbox endpoints:</p>
      <ul>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#getMailMessage" target="_self">GET /mailbox/mailMessages/{id}</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#getMailThreads" target="_self">GET /mailbox/mailThreads</a></code></li>
          <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#getMailThread" target="_self">GET /mailbox/mailThreads/{id}</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#getMailThreadMessages" target="_self">GET /mailbox/mailThreads/{id}/mailMessages</a></code></li>
              <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#updateMailThreadDetails" target="_self">PUT /mailbox/mailThreads/{id}</a></code></li>
                <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Mailbox#deleteMailThread" target="_self">DELETE /mailbox/mailThreads/{id}</a></code></li>
      </ul>
      <br>
      <p>3. We documented <code>required</code> labels for the body parameters of the following endpoints:
</p><ul>
      <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_self">POST /deals/{id}/products</a></code> - <code>item_price</code> and <code>quantity</code> are required
</li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_self">PUT /deals/{id}/products/{product_attachment_id}</a></code>- <code>item_price</code> and <code>quantity</code> are required
</li>
          <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Notes#addNote" target="_self">POST /notes</a></code> - <code>content</code> is required
</li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization" target="_self">POST /organizations</a></code> - <code>name</code> is required
</li>
              <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#addPerson" target="_self">POST /persons</a></code> -<code> name</code> is required
</li>
                <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#deletePersons" target="_self">DELETE /persons</a></code> - <code>ids</code> is required</li>
                  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_self">POST /products</a></code> -<code> name</code> is required</li>
                 
      </ul>
      </div>
</div>


February 2022 release notes

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">February 25, 2022</span>
    </div>
    <div class="change-area">
      
      <p>The Account Settings access is a free seat in Pipedrive without access to Deals, but allows access to user management, billing details, company settings, security settings, and personal settings.</p>
      <p><b>What is changing?</b></p>

      <ul>
        <li><p>Users without access to Deals can now access all <code>GET</code> endpoints of the 
          Users API to view users’ data. This includes the following endpoints:</p>
          <ul>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUsers" target="_self">GET /users</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#findUsersByName" target="_self">GET /users/find</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getCurrentUser" target="_self">GET /users/me</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUser" target="_self">GET /users/{id}</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserFollowers" target="_self">GET /users/{id}/followers</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserPermissions" target="_self">GET /users/{id}/permissions</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserRoleAssignments" target="_self">GET /users/{id}/roleAssignments</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserRoleSettings" target="_self">GET /users/{id}/roleSettings</a></code></li>
          
          </ul>
        </li>
        <br>
        <li><p>Endpoints for adding and modifying users now require the user to have the Account Settings access. 
            It means that being an <b>admin</b> type user only, you'll no longer have access to the <code>POST</code>, <code>PUT</code> and <code>DELETE</code> endpoints of the Users API, including:
          </p>
          <ul>
          <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#addUser" target="_self">POST /users</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#addUserRoleAssignment" target="_self">POST /users/{id}/roleAssignments</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#updateUser" target="_self">PUT /users/{id}</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#deleteUserRoleAssignment" target="_self">DELETE /users/{id}/roleAssignments</a></code></li>
          </ul>

        </li>
      </ul>
      
 <p><b>Why is it changing?</b></p>
      <p>This change unifies the Users API’s access to the Account Settings functionality of the Pipedrive web app to ensure consistency between the API and the web app.
</p>
      
       <p><b>Who will be affected?</b></p>
      <p>Anyone without Deals access who wishes to view users’ data or who relies on the modifying and adding endpoints of the Users API as an admin user only.
You can read more about <a href="https://support.pipedrive.com/en/article/global-user-management">user types in Pipedrive</a> and <a href="https://support.pipedrive.com/en/article/user-types-in-pipedrive-account-settings">the Account Settings user type</a> in our Knowledge Base.
</p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">February 25, 2022</span>
    </div>
    <div class="change-area">
      
      <p>The Account Settings access is a free seat in Pipedrive without access to Deals, but allows access to user management, billing details, company settings, security settings, and personal settings.</p>
      <p><b>What is changing?</b></p>

      <ul>
        <li><p>Users without access to Deals can now access all <code>GET</code> endpoints of the 
          Users API to view users’ data. This includes the following endpoints:</p>
          <ul>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUsers" target="_self">GET /users</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#findUsersByName" target="_self">GET /users/find</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getCurrentUser" target="_self">GET /users/me</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUser" target="_self">GET /users/{id}</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserFollowers" target="_self">GET /users/{id}/followers</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserPermissions" target="_self">GET /users/{id}/permissions</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserRoleAssignments" target="_self">GET /users/{id}/roleAssignments</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserRoleSettings" target="_self">GET /users/{id}/roleSettings</a></code></li>
          
          </ul>
        </li>
        <br>
        <li><p>Endpoints for adding and modifying users now require the user to have the Account Settings access. 
            It means that being an <b>admin</b> type user only, you'll no longer have access to the <code>POST</code>, <code>PUT</code> and <code>DELETE</code> endpoints of the Users API, including:
          </p>
          <ul>
          <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#addUser" target="_self">POST /users</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#addUserRoleAssignment" target="_self">POST /users/{id}/roleAssignments</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#updateUser" target="_self">PUT /users/{id}</a></code></li>
            <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Users#deleteUserRoleAssignment" target="_self">DELETE /users/{id}/roleAssignments</a></code></li>
          </ul>

        </li>
      </ul>
      
 <p><b>Why is it changing?</b></p>
      <p>This change unifies the Users API’s access to the Account Settings functionality of the Pipedrive web app to ensure consistency between the API and the web app.
</p>
      
       <p><b>Who will be affected?</b></p>
      <p>Anyone without Deals access who wishes to view users’ data or who relies on the modifying and adding endpoints of the Users API as an admin user only.
You can read more about <a href="https://support.pipedrive.com/en/article/global-user-management">user types in Pipedrive</a> and <a href="https://support.pipedrive.com/en/article/user-types-in-pipedrive-account-settings">the Account Settings user type</a> in our Knowledge Base.
</p>
  </div>
</div>


Account Settings access for Users API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 28, 2022</span>
    </div>
    <div class="change-area">
      
      
     <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 added <code>required</code> labels to reflect reality for the 
        <code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationRelationships#addOrganizationRelationship" target="_self">POST /organizationRelationships</a></code> endpoint.</p>
        <p><b>2.</b> We updated the response status code from <code>200</code> “OK” to <code>201</code> “Created” to reflect reality for the following 3 endpoints: 
   <p>   <ul><ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization" target="_self">POST /organizations</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#addPerson" target="_self">POST /persons</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_self">POST /deals</a></code></li>
      </ul></p></ul>
  <p><b>3.</b>  We added <code>leadField</code> to <code>field_type</code> parameter value options for the
<code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItemByField" target="_self">GET /itemSearch/field</a></code> endpoint.</p>
    <p><b>4.</b> We updated the response structure to reflect reality for the <code><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#findSubscriptionByDeal" target="_self">GET /subscriptions/find/{dealId}</a></code> endpoint.</p>
  <p>Previously, the response was documented as: <code>response -> recurring -> value -> data -> id</code>.
    In reality, the structure is: <code>response -> data -> id</code>.</p>
  <p>Here’s the code example of the correct response structure:</p>
  <div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar"><button type="button">JSON</button></div><div class="CodeTabs-inner"><pre><code class="rdmd-code lang-json theme-light" data-lang="json" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><div class="cm-s-neo">{
   <span class="cm-property">"success"</span>: <span class="cm-atom">true</span>,
   <span class="cm-property">"data"</span>: {
      <span class="cm-property">"id"</span>: <span class="cm-number">21</span>,
      <span class="cm-property">"user_id"</span>: <span class="cm-number">10382754</span>,
      <span class="cm-property">"deal_id"</span>: <span class="cm-number">1121</span>,
      <span class="cm-property">"is_active"</span>: <span class="cm-atom">true</span>,
      <span class="cm-property">"cycle_amount"</span>: <span class="cm-number">100.3</span>,
      <span class="cm-property">"cycles_count"</span>: <span class="cm-number">15</span>,
      <span class="cm-property">"infinite"</span>: <span class="cm-atom">true</span>,
      <span class="cm-property">"currency"</span>: <span class="cm-string">"USD"</span>,
      <span class="cm-property">"start_date"</span>: <span class="cm-string">"2020-10-20"</span>,
      <span class="cm-property">"end_date"</span>: <span class="cm-string">"2022-01-20"</span>,
      <span class="cm-property">"description"</span>: <span class="cm-string">"pizza delivery"</span>,
      <span class="cm-property">"add_time"</span>: <span class="cm-string">"2020-07-07 08:32:57"</span>,
      <span class="cm-property">"update_time"</span>: <span class="cm-string">"2020-07-07 08:32:57"</span>,
      <span class="cm-property">"lifetime_value"</span>: <span class="cm-number">1504.5</span>,
      <span class="cm-property">"cadence_type"</span>: <span class="cm-string">"monthly"</span>,
      <span class="cm-property">"final_status"</span>: <span class="cm-atom">null</span>
   }
};
</div></code></pre></div></div>
     
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 28, 2022</span>
    </div>
    <div class="change-area">
      
      
     <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 added <code>required</code> labels to reflect reality for the 
        <code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationRelationships#addOrganizationRelationship" target="_self">POST /organizationRelationships</a></code> endpoint.</p>
        <p><b>2.</b> We updated the response status code from <code>200</code> “OK” to <code>201</code> “Created” to reflect reality for the following 3 endpoints: 
   <p>   <ul><ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization" target="_self">POST /organizations</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#addPerson" target="_self">POST /persons</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="_self">POST /deals</a></code></li>
      </ul></p></ul>
  <p><b>3.</b>  We added <code>leadField</code> to <code>field_type</code> parameter value options for the
<code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItemByField" target="_self">GET /itemSearch/field</a></code> endpoint.</p>
    <p><b>4.</b> We updated the response structure to reflect reality for the <code><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#findSubscriptionByDeal" target="_self">GET /subscriptions/find/{dealId}</a></code> endpoint.</p>
  <p>Previously, the response was documented as: <code>response -> recurring -> value -> data -> id</code>.
    In reality, the structure is: <code>response -> data -> id</code>.</p>
  <p>Here’s the code example of the correct response structure:</p>
  <div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar"><button type="button">JSON</button></div><div class="CodeTabs-inner"><pre><code class="rdmd-code lang-json theme-light" data-lang="json" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><div class="cm-s-neo">{
   <span class="cm-property">"success"</span>: <span class="cm-atom">true</span>,
   <span class="cm-property">"data"</span>: {
      <span class="cm-property">"id"</span>: <span class="cm-number">21</span>,
      <span class="cm-property">"user_id"</span>: <span class="cm-number">10382754</span>,
      <span class="cm-property">"deal_id"</span>: <span class="cm-number">1121</span>,
      <span class="cm-property">"is_active"</span>: <span class="cm-atom">true</span>,
      <span class="cm-property">"cycle_amount"</span>: <span class="cm-number">100.3</span>,
      <span class="cm-property">"cycles_count"</span>: <span class="cm-number">15</span>,
      <span class="cm-property">"infinite"</span>: <span class="cm-atom">true</span>,
      <span class="cm-property">"currency"</span>: <span class="cm-string">"USD"</span>,
      <span class="cm-property">"start_date"</span>: <span class="cm-string">"2020-10-20"</span>,
      <span class="cm-property">"end_date"</span>: <span class="cm-string">"2022-01-20"</span>,
      <span class="cm-property">"description"</span>: <span class="cm-string">"pizza delivery"</span>,
      <span class="cm-property">"add_time"</span>: <span class="cm-string">"2020-07-07 08:32:57"</span>,
      <span class="cm-property">"update_time"</span>: <span class="cm-string">"2020-07-07 08:32:57"</span>,
      <span class="cm-property">"lifetime_value"</span>: <span class="cm-number">1504.5</span>,
      <span class="cm-property">"cadence_type"</span>: <span class="cm-string">"monthly"</span>,
      <span class="cm-property">"final_status"</span>: <span class="cm-atom">null</span>
   }
};
</div></code></pre></div></div>
     
  </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">January 10, 2022</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-endpoints-in-deals-and-contacts-scopes"></div>
        <div class="heading-text"><div id="new-endpoints-in-deals-and-contacts-scopes" class="heading-anchor_backwardsCompatibility">
          </div>New endpoints in Deals and Contacts scopes</div>
        <a aria-label="Skip link to New endpoints in Deals and Contacts scopes" class="heading-anchor-icon fa fa-anchor" 
           href="#new-endpoints-in-deals-and-contacts-scopes"></a></h3>

      <p><code>Deals:read</code>, <code>deals:full</code>, <code>contacts:read</code> and <code>contacts:full</code> scopes now allow apps to have access to new endpoints.</p>
      <h4><code>Deals:read</code> and <code>deals:full</code></h4>
      <p> By selecting the <code>deals:read</code> and/or <code>deals:full</code> scope(s),
        an app can now have access to the following endpoint, which allows the app to list users permitted to access a deal:</p>
<ul>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealUsers" target="_self">GET /deals/{id}/permittedUsers</a></code></li>
      </ul>    
      <h4><code>Contacts:read</code></h4>
      <p> By selecting the <code> contacts:read</code>scope, an app can now have access to the following endpoints, which allow the app to list products associated with a person 
        and list users permitted to access a person and an organization:</p>
<ul>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonProducts" target="_self">GET /persons/{id}/products</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFollowers" target="_self">GET /persons/{id}/permittedUsers</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationUsers" target="_self">GET /organizations/{id}/permittedUsers</a></code></li>
      </ul>
      <h4><code>Contacts:full</code></h4>
      <p> By selecting the <code> contacts:full</code>scope, an app can now have access to the following endpoints, which allow the app to list products associated with a person, 
        list users permitted to access a person and an organization and delete followers from a person and an organization:</p>
<ul>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonProducts" target="_self">GET /persons/{id}/products</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFollowers" target="_self">GET /persons/{id}/permittedUsers</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationUsers" target="_self">GET /organizations/{id}/permittedUsers</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#deletePersonFollower" target="_self">DELETE /persons/{id}/followers/{follower_id}</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#deleteOrganizationFollower" target="_self">DELETE /organizations/{id}/followers/{follower_id}</a></code></li>
      </ul>
<p>You can read more about the scopes and permission explanations <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations">here</a>.</p> 
     <p>If you wish to add or remove scopes of an already approved or published app, be sure to <a href="https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app#changing-the-scopes">learn how changing the scopes will affect your app's existing users</a>.</p>


      
      <p class="published-on"><i>Published on January 10, 2022</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">January 10, 2022</span>
    </div>
    <div class="change-area">
      <h3 class="heading heading-3 header-scroll" align="">
      <div class="heading-anchor anchor waypoint" id="new-endpoints-in-deals-and-contacts-scopes"></div>
        <div class="heading-text"><div id="new-endpoints-in-deals-and-contacts-scopes" class="heading-anchor_backwardsCompatibility">
          </div>New endpoints in Deals and Contacts scopes</div>
        <a aria-label="Skip link to New endpoints in Deals and Contacts scopes" class="heading-anchor-icon fa fa-anchor" 
           href="#new-endpoints-in-deals-and-contacts-scopes"></a></h3>

      <p><code>Deals:read</code>, <code>deals:full</code>, <code>contacts:read</code> and <code>contacts:full</code> scopes now allow apps to have access to new endpoints.</p>
      <h4><code>Deals:read</code> and <code>deals:full</code></h4>
      <p> By selecting the <code>deals:read</code> and/or <code>deals:full</code> scope(s),
        an app can now have access to the following endpoint, which allows the app to list users permitted to access a deal:</p>
<ul>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealUsers" target="_self">GET /deals/{id}/permittedUsers</a></code></li>
      </ul>    
      <h4><code>Contacts:read</code></h4>
      <p> By selecting the <code> contacts:read</code>scope, an app can now have access to the following endpoints, which allow the app to list products associated with a person 
        and list users permitted to access a person and an organization:</p>
<ul>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonProducts" target="_self">GET /persons/{id}/products</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFollowers" target="_self">GET /persons/{id}/permittedUsers</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationUsers" target="_self">GET /organizations/{id}/permittedUsers</a></code></li>
      </ul>
      <h4><code>Contacts:full</code></h4>
      <p> By selecting the <code> contacts:full</code>scope, an app can now have access to the following endpoints, which allow the app to list products associated with a person, 
        list users permitted to access a person and an organization and delete followers from a person and an organization:</p>
<ul>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonProducts" target="_self">GET /persons/{id}/products</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFollowers" target="_self">GET /persons/{id}/permittedUsers</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationUsers" target="_self">GET /organizations/{id}/permittedUsers</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#deletePersonFollower" target="_self">DELETE /persons/{id}/followers/{follower_id}</a></code></li>
  <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#deleteOrganizationFollower" target="_self">DELETE /organizations/{id}/followers/{follower_id}</a></code></li>
      </ul>
<p>You can read more about the scopes and permission explanations <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations">here</a>.</p> 
     <p>If you wish to add or remove scopes of an already approved or published app, be sure to <a href="https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app#changing-the-scopes">learn how changing the scopes will affect your app's existing users</a>.</p>


      
      <p class="published-on"><i>Published on January 10, 2022</i></p>
    </div>
</div>


New endpoints in Deals and Contacts scopes

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 29, 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-dec-21"></div>
        <div class="heading-text"><div id="documentation-updates-for-api-reference-dec-21" 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-dec-21"></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 improved the description of the <code>follower_id</code> path parameter within the 
        <code><a href="https://developers.pipedrive.com/docs/api/v1/Products#deleteProductFollower" target="_self">DELETE /products/{id}/followers/{follower_id}</a></code> endpoint.</p>
        <p><b>2.</b> We added the body parameter <code>tax</code> to the following two endpoints: 
   <p>   <ul><ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_self">POST /deals/{id}/products</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_self">PUT /deals/{id}/products/{product_attachment_id}</a></code></li>
      </ul></p></ul>
  <p><b>3.</b> We updated the response status code from <code>200</code> “OK” to <code>201</code> “Created” to reflect reality for the
<code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#addActivity" target="_self">POST /activities</a></code> endpoint.</p>
    <p><b>4.</b> We added support for searching leads by <code>custom_fields</code> and <code>notes</code>  within the
<code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem" target="_self">GET /itemSearch</a></code> endpoint.</p>  
       <br>
      <p class="published-on"><i>Published on December 29, 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">December 29, 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-dec-21"></div>
        <div class="heading-text"><div id="documentation-updates-for-api-reference-dec-21" 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-dec-21"></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 improved the description of the <code>follower_id</code> path parameter within the 
        <code><a href="https://developers.pipedrive.com/docs/api/v1/Products#deleteProductFollower" target="_self">DELETE /products/{id}/followers/{follower_id}</a></code> endpoint.</p>
        <p><b>2.</b> We added the body parameter <code>tax</code> to the following two endpoints: 
   <p>   <ul><ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct" target="_self">POST /deals/{id}/products</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct" target="_self">PUT /deals/{id}/products/{product_attachment_id}</a></code></li>
      </ul></p></ul>
  <p><b>3.</b> We updated the response status code from <code>200</code> “OK” to <code>201</code> “Created” to reflect reality for the
<code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#addActivity" target="_self">POST /activities</a></code> endpoint.</p>
    <p><b>4.</b> We added support for searching leads by <code>custom_fields</code> and <code>notes</code>  within the
<code><a href="https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem" target="_self">GET /itemSearch</a></code> endpoint.</p>  
       <br>
      <p class="published-on"><i>Published on December 29, 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">February 7, 2022</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="update-to-the-breaking-change-in-products-endpoint-and-webhook"></div>
        <div class="heading-text"><div id="update-to-the-breaking-change-in-products-endpoint-and-webhook" class="heading-anchor_backwardsCompatibility">
          </div>Update to the breaking change in Products endpoint and webhook</div>
        <a aria-label="Skip link to Update to the breaking change in Products endpoint and webhook" class="heading-anchor-icon fa fa-anchor" 
           href="#update-to-the-breaking-change-in-products-endpoint-and-webhook"></a></h3>
      
    <p>Regarding the <a href="https://pipedrive.readme.io/docs/changelog#breaking-change-in-products-endpoint-and-webhook">breaking change in Products endpoint and webhook</a> we communicated on September 24, 2021, 
      we will be updating the response schema of the <code><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_self">PUT /v1/products/{id}</a></code> 
      endpoint and the response payload of the <code>updated.product</code> webhook.
      The updated structure follows a consistent pattern and is unified with the responses of the Products endpoint.
      </p>
      

      <p>The current response structure:
<div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar"><button type="button">JSON</button></div><div class="CodeTabs-inner"><pre><code class="rdmd-code lang-json theme-light" data-lang="json" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><div class="cm-s-neo">{
   <span class="cm-meta">...</span>
   <span class="cm-string">“id”</span>: <span class="cm-number">1</span>,
   <span class="cm-string">"add_time"</span>: <span class="cm-string">"2019-12-19 11:36:49"</span>,
   <span class="cm-string">"update_time"</span>: <span class="cm-string">"2019-12-26 13:35:17"</span>,
   <span class="cm-property">"prices"</span>:  {
         <span class="cm-property">"EUR"</span>: {
            <span class="cm-property">"id"</span>: <span class="cm-number">1</span>,
            <span class="cm-property">"product_id"</span>: <span class="cm-number">1</span>,
            <span class="cm-property">"price"</span>: <span class="cm-number">5</span>,
            <span class="cm-property">"currency"</span>: <span class="cm-string">"EUR"</span>,
            <span class="cm-property">"cost"</span>: <span class="cm-number">2</span>,
            <span class="cm-property">"overhead_cost"</span>: <span class="cm-number">3</span>
          }
    }
   <span class="cm-meta">...</span>
};
</div></code></pre></div></div>
</p> 
  
        <p>The updated response structure:
<div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar"><button type="button">JSON</button></div><div class="CodeTabs-inner"><pre><code class="rdmd-code lang-json theme-light" data-lang="json" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><div class="cm-s-neo">{
   <span class="cm-meta">...</span>
   <span class="cm-string">“id”</span>: <span class="cm-number">123</span>,
   <span class="cm-string">“add_time”</span>: <span class="cm-string">"2019-12-19 11:36:49"</span>,
   <span class="cm-string">“update_time”</span>: <span class="cm-string">"2019-12-26 13:35:17"</span>,
   <span class="cm-property">“prices”</span>: [
      {
         <span class="cm-property">“id”</span>: <span class="cm-number">1</span>,
         <span class="cm-property">“product_id”</span>: <span class="cm-number">123</span>,
         <span class="cm-property">“price”</span>: <span class="cm-number">5</span>,
         <span class="cm-property">“currency”</span>: <span class="cm-string">"EUR"</span>,
         <span class="cm-property">“cost”</span>: <span class="cm-number">2</span>,
         <span class="cm-property">“overhead_cost”</span>: <span class="cm-number">3</span>,
      },
   ],
   <span class="cm-meta">...</span>
};
</div></code></pre></div></div>
</p> 

<p>The updated response structure ensures consistency with the <code><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_self">POST /v1/products</a></code> endpoint. The prices property is now represented in the same way - as an array of price objects.
          
       <br>
      <p class="published-on"><i>Published on December 8, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">February 7, 2022</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="update-to-the-breaking-change-in-products-endpoint-and-webhook"></div>
        <div class="heading-text"><div id="update-to-the-breaking-change-in-products-endpoint-and-webhook" class="heading-anchor_backwardsCompatibility">
          </div>Update to the breaking change in Products endpoint and webhook</div>
        <a aria-label="Skip link to Update to the breaking change in Products endpoint and webhook" class="heading-anchor-icon fa fa-anchor" 
           href="#update-to-the-breaking-change-in-products-endpoint-and-webhook"></a></h3>
      
    <p>Regarding the <a href="/changelog/post/breaking-change-in-products-endpoint-and-webhook">breaking change in Products endpoint and webhook</a> we communicated on September 24, 2021, 
      we will be updating the response schema of the <code><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProduct" target="_self">PUT /v1/products/{id}</a></code> 
      endpoint and the response payload of the <code>updated.product</code> webhook.
      The updated structure follows a consistent pattern and is unified with the responses of the Products endpoint.
      </p>
      

      <p>The current response structure:
<div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar"><button type="button">JSON</button></div><div class="CodeTabs-inner"><pre><code class="rdmd-code lang-json theme-light" data-lang="json" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><div class="cm-s-neo">{
   <span class="cm-meta">...</span>
   <span class="cm-string">“id”</span>: <span class="cm-number">1</span>,
   <span class="cm-string">"add_time"</span>: <span class="cm-string">"2019-12-19 11:36:49"</span>,
   <span class="cm-string">"update_time"</span>: <span class="cm-string">"2019-12-26 13:35:17"</span>,
   <span class="cm-property">"prices"</span>:  {
         <span class="cm-property">"EUR"</span>: {
            <span class="cm-property">"id"</span>: <span class="cm-number">1</span>,
            <span class="cm-property">"product_id"</span>: <span class="cm-number">1</span>,
            <span class="cm-property">"price"</span>: <span class="cm-number">5</span>,
            <span class="cm-property">"currency"</span>: <span class="cm-string">"EUR"</span>,
            <span class="cm-property">"cost"</span>: <span class="cm-number">2</span>,
            <span class="cm-property">"overhead_cost"</span>: <span class="cm-number">3</span>
          }
    }
   <span class="cm-meta">...</span>
};
</div></code></pre></div></div>
</p> 
  
        <p>The updated response structure:
<div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar"><button type="button">JSON</button></div><div class="CodeTabs-inner"><pre><code class="rdmd-code lang-json theme-light" data-lang="json" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><div class="cm-s-neo">{
   <span class="cm-meta">...</span>
   <span class="cm-string">“id”</span>: <span class="cm-number">123</span>,
   <span class="cm-string">“add_time”</span>: <span class="cm-string">"2019-12-19 11:36:49"</span>,
   <span class="cm-string">“update_time”</span>: <span class="cm-string">"2019-12-26 13:35:17"</span>,
   <span class="cm-property">“prices”</span>: [
      {
         <span class="cm-property">“id”</span>: <span class="cm-number">1</span>,
         <span class="cm-property">“product_id”</span>: <span class="cm-number">123</span>,
         <span class="cm-property">“price”</span>: <span class="cm-number">5</span>,
         <span class="cm-property">“currency”</span>: <span class="cm-string">"EUR"</span>,
         <span class="cm-property">“cost”</span>: <span class="cm-number">2</span>,
         <span class="cm-property">“overhead_cost”</span>: <span class="cm-number">3</span>,
      },
   ],
   <span class="cm-meta">...</span>
};
</div></code></pre></div></div>
</p> 

<p>The updated response structure ensures consistency with the <code><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_self">POST /v1/products</a></code> endpoint. The prices property is now represented in the same way - as an array of price objects.
          
       <br>
      <p class="published-on"><i>Published on December 8, 2021</i></p>
  </div>
</div>


Update to the breaking change in Products endpoint and Webhook

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 22, 2021</span>
    </div>
    <div class="change-area">
       
      
      <p><b>What is changing?</b></p>
      <p>In order to protect ourselves from online attacks, 
        users abusing our system by not respecting our <a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting">rate limits</a> and keeping up 
        the high volume of traffic despite getting the <code>429</code> response code, 
        will also start getting the <code>403</code> response code. When getting the <code>403</code> response code, 
        the answer will be an HTML error page informing the user that one’s access has been denied:</p>

  <span aria-label="" class="img" role="button" tabindex="0">
    <img src="https://files.readme.io/4818f6b-Ratelimiting.png" alt="" title="Ratelimiting.png" class="" align="" caption="" height="auto" width="auto">
    <span autofocus="" class="lightbox" role="dialog" tabindex="0">
      <span class="lightbox-inner">
      
      <img src="https://files.readme.io/4818f6b-Ratelimiting.png" title="Click to close..." class="lightbox-img" align="" caption="" height="auto" >
    </span>
      </span>
      
  <p><b>Why is it changing?</b></p>
      <p>This <a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting#blocking-high-volume-traffic">improvement</a> is designed to prevent undesired loads on our systems 
    from misconfigured API integrations or abuse. Our goal is to protect the 
    Pipedrive infrastructure and make our service more reliable to users not 
    busing our system.
</p>
  
  <p><b>Who is affected?</b></p>
      <p>
Please note that this improvement will not impact the vast majority of users, 
        even if there is heavy usage of our API. If you are impacted by this, 
        please review your integration and remove any misconfiguration that might 
        lead you to be blocked.
</p>  
  </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Rate limiting"]}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 22, 2021</span>
    </div>
    <div class="change-area">
       
      
      <p><b>What is changing?</b></p>
      <p>In order to protect ourselves from online attacks, 
        users abusing our system by not respecting our <a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting">rate limits</a> and keeping up 
        the high volume of traffic despite getting the <code>429</code> response code, 
        will also start getting the <code>403</code> response code. When getting the <code>403</code> response code, 
        the answer will be an HTML error page informing the user that one’s access has been denied:</p>

  <span aria-label="" class="img" role="button" tabindex="0">
    <img src="https://files.readme.io/4818f6b-Ratelimiting.png" alt="" title="Ratelimiting.png" class="" align="" caption="" height="auto" width="auto">
    <span autofocus="" class="lightbox" role="dialog" tabindex="0">
      <span class="lightbox-inner">
      
      <img src="https://files.readme.io/4818f6b-Ratelimiting.png" title="Click to close..." class="lightbox-img" align="" caption="" height="auto" >
    </span>
      </span>
      
  <p><b>Why is it changing?</b></p>
      <p>This <a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting#blocking-high-volume-traffic">improvement</a> is designed to prevent undesired loads on our systems 
    from misconfigured API integrations or abuse. Our goal is to protect the 
    Pipedrive infrastructure and make our service more reliable to users not 
    busing our system.
</p>
  
  <p><b>Who is affected?</b></p>
      <p>
Please note that this improvement will not impact the vast majority of users, 
        even if there is heavy usage of our API. If you are impacted by this, 
        please review your integration and remove any misconfiguration that might 
        lead you to be blocked.
</p>  
  </div>
</div>


Blocking high volume traffic

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 26, 2022</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="removal-of-follower-count-updates-in-webhooks"></div>
        <div class="heading-text"><div id="removal-of-follower-count-updates-in-webhooks" class="heading-anchor_backwardsCompatibility">
          </div>Removal of  <code>follower_count</code> updates in Webhooks</div>
        <a aria-label="Skip link to Removal of follower_count updates in Webhooks" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-follower-count-updates-in-webhooks"></a></h3>
      
      <p><b>What is changing?</b></p>
      <p>The following types of Webhooks will no longer be triggered when a follower is added or removed:</p>
   <p>   <ul><ul>
<li><code>updated.deal</code></li>
<li><code>updated.person</code></li>
<li><code>updated.organization</code></li>
<li><code>updated.product</code></li>
      </ul></p></ul>
  <p>Previously, when a follower was added or removed, a webhook was triggered with new <code>update_time</code> and <code>follower_count</code> values for the entity.</p>
  
  <p><b>Why is it changing?</b></p>
  <p>The logic that handles <code>follower_count</code> was built on an old technological platform that is not reliable enough, 
  which resulted in webhooks not triggering and <code>follower_count</code> values being incorrect.
  We’re doing this change to enable moving to a more reliable platform.</p>
  
  <p><b>Who is affected?</b></p>
  <p>Anyone who relies on active Webhooks that are triggered when a follower is added or removed from the previous 4 Webhooks.</p>
  
  <p class="published-on"><i>Published on December 6, 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">January 26, 2022</span>
    </div>
    <div class="change-area">
       <h3 class="heading heading-3 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="removal-of-follower-count-updates-in-webhooks"></div>
        <div class="heading-text"><div id="removal-of-follower-count-updates-in-webhooks" class="heading-anchor_backwardsCompatibility">
          </div>Removal of  <code>follower_count</code> updates in Webhooks</div>
        <a aria-label="Skip link to Removal of follower_count updates in Webhooks" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-follower-count-updates-in-webhooks"></a></h3>
      
      <p><b>What is changing?</b></p>
      <p>The following types of Webhooks will no longer be triggered when a follower is added or removed:</p>
   <p>   <ul><ul>
<li><code>updated.deal</code></li>
<li><code>updated.person</code></li>
<li><code>updated.organization</code></li>
<li><code>updated.product</code></li>
      </ul></p></ul>
  <p>Previously, when a follower was added or removed, a webhook was triggered with new <code>update_time</code> and <code>follower_count</code> values for the entity.</p>
  
  <p><b>Why is it changing?</b></p>
  <p>The logic that handles <code>follower_count</code> was built on an old technological platform that is not reliable enough, 
  which resulted in webhooks not triggering and <code>follower_count</code> values being incorrect.
  We’re doing this change to enable moving to a more reliable platform.</p>
  
  <p><b>Who is affected?</b></p>
  <p>Anyone who relies on active Webhooks that are triggered when a follower is added or removed from the previous 4 Webhooks.</p>
  
  <p class="published-on"><i>Published on December 6, 2021</i></p>
  </div>
</div>


Removal of <code>follower_count</code> updates in Webhooks

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 30, 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-nov-21"></div>
        <div class="heading-text"><div id="documentation-updates-for-api-reference-nov-21" 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-nov-21"></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 added the <code>start</code> and <code>limit</code> query parameters for the following 4 endpoints so you can control pagination better:</p>
   <p>   <ul><ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#getDealFields" target="_self">GET /v1/dealFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#getOrganizationFields" target="_self">GET /v1/organizationFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#getPersonFields" target="_self">GET /v1/personFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#getProductFields" target="_self">GET /v1/productFields</a></code></li>
      </ul></p></ul>
        <p><b>2.</b> We updated the <code>subscription_url</code> body parameter for the
<code><a href="https://developers.pipedrive.com/docs/api/v1/Webhooks#addWebhook" target="_self">POST /v1/webhooks</a></code>
          endpoint to reflect the <a href="https://pipedrive.readme.io/docs/changelog#removal-of-webhooks-redirection-support" target="_self">removal of the Webhooks redirection support</a>.</p>
  <p><b>3.</b> Duplicate <code>name</code> and <code>options</code> body parameters were removed from the
<code><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField" target="_self">POST /v1/productFields</a></code> endpoint.</p>
    <p><b>4.</b> We documented the <code>ids</code> query parameter for the
<code><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProducts" target="_self">GET /v1/products</a></code>
      endpoint. You can now specify an array of integers with the IDs of the Products that should be returned in the response.</p>
<p><b>5.</b> The response status code for the following endpoints has been updated from <code>200</code> “OK” to  <code>201</code> “Created” to reflect reality:</p>
   <p>   <ul><ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField" target="_self">POST /v1/productFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProductFollower" target="_self">POST /v1/products/{id}/followers</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_self">POST /v1/products</a></code></li>
      </ul></p></ul>
    <p><b>6.</b> We updated the <code><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductFollowers" target="_self">GET /v1/products/{id}/followers</a></code>
       endpoint response schema so that the <code>data</code> property is a ProductFollower object.
      Previously, the <code>data</code> property was an array of user IDs.</p>
<p>Here’s the code example of the improved response in JSON:
<div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar"><button type="button">JSON</button></div><div class="CodeTabs-inner"><pre><code class="rdmd-code lang-json theme-light" data-lang="json" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><div class="cm-s-neo">{
<span class="cm-property">"success"</span>: <span class="cm-atom">true</span>,
<span class="cm-property">"data"</span>: [ <span class="cm-variable">…</span> ]
   { <span class="cm-variable">…</span> }
   <span class="cm-string">"user_id"</span>: <span class="cm-number">123</span>,
   <span class="cm-string">"id"</span>: <span class="cm-number">456</span>,
   <span class="cm-string">"product_id"</span>: <span class="cm-number">789</span>,
   <span class="cm-string">"add_time"</span>: <span class="cm-string">"2021-08-03 12:07:05"</span>
   <span class="cm-string">"additional_data"</span>: { <span class="cm-property">…</span> }
   <span class="cm-string">"pagination"</span>: { <span class="cm-property">…</span> }
     <span class="cm-string">"start"</span>: <span class="cm-number">0</span>,
     <span class="cm-string">"limit"</span>: <span class="cm-number">100</span>,
     <span class="cm-string">"more_items_in_collection"</span>: <span class="cm-atom">false</span>
}
</div></code></pre></div></div>
</p>      

          
       <br>
      <p class="published-on"><i>Published on November 30, 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">November 30, 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-nov-21"></div>
        <div class="heading-text"><div id="documentation-updates-for-api-reference-nov-21" 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-nov-21"></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 added the <code>start</code> and <code>limit</code> query parameters for the following 4 endpoints so you can control pagination better:</p>
   <p>   <ul><ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#getDealFields" target="_self">GET /v1/dealFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#getOrganizationFields" target="_self">GET /v1/organizationFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#getPersonFields" target="_self">GET /v1/personFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#getProductFields" target="_self">GET /v1/productFields</a></code></li>
      </ul></p></ul>
        <p><b>2.</b> We updated the <code>subscription_url</code> body parameter for the
<code><a href="https://developers.pipedrive.com/docs/api/v1/Webhooks#addWebhook" target="_self">POST /v1/webhooks</a></code>
          endpoint to reflect the <a href="/changelog/post/removal-of-webhooks-redirection-support" target="_self">removal of the Webhooks redirection support</a>.</p>
  <p><b>3.</b> Duplicate <code>name</code> and <code>options</code> body parameters were removed from the
<code><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField" target="_self">POST /v1/productFields</a></code> endpoint.</p>
    <p><b>4.</b> We documented the <code>ids</code> query parameter for the
<code><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProducts" target="_self">GET /v1/products</a></code>
      endpoint. You can now specify an array of integers with the IDs of the Products that should be returned in the response.</p>
<p><b>5.</b> The response status code for the following endpoints has been updated from <code>200</code> “OK” to  <code>201</code> “Created” to reflect reality:</p>
   <p>   <ul><ul>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField" target="_self">POST /v1/productFields</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProductFollower" target="_self">POST /v1/products/{id}/followers</a></code></li>
<li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProduct" target="_self">POST /v1/products</a></code></li>
      </ul></p></ul>
    <p><b>6.</b> We updated the <code><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductFollowers" target="_self">GET /v1/products/{id}/followers</a></code>
       endpoint response schema so that the <code>data</code> property is a ProductFollower object.
      Previously, the <code>data</code> property was an array of user IDs.</p>
<p>Here’s the code example of the improved response in JSON:
<div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar"><button type="button">JSON</button></div><div class="CodeTabs-inner"><pre><code class="rdmd-code lang-json theme-light" data-lang="json" name=""><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><div class="cm-s-neo">{
<span class="cm-property">"success"</span>: <span class="cm-atom">true</span>,
<span class="cm-property">"data"</span>: [ <span class="cm-variable">…</span> ]
   { <span class="cm-variable">…</span> }
   <span class="cm-string">"user_id"</span>: <span class="cm-number">123</span>,
   <span class="cm-string">"id"</span>: <span class="cm-number">456</span>,
   <span class="cm-string">"product_id"</span>: <span class="cm-number">789</span>,
   <span class="cm-string">"add_time"</span>: <span class="cm-string">"2021-08-03 12:07:05"</span>
   <span class="cm-string">"additional_data"</span>: { <span class="cm-property">…</span> }
   <span class="cm-string">"pagination"</span>: { <span class="cm-property">…</span> }
     <span class="cm-string">"start"</span>: <span class="cm-number">0</span>,
     <span class="cm-string">"limit"</span>: <span class="cm-number">100</span>,
     <span class="cm-string">"more_items_in_collection"</span>: <span class="cm-atom">false</span>
}
</div></code></pre></div></div>
</p>      

          
       <br>
      <p class="published-on"><i>Published on November 30, 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">January 27, 2022</span>
    </div>
    <div class="change-area">
      
      <h3 class="heading heading-2 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="removal-of-webhooks-redirection-support"></div>
        <div class="heading-text"><div id="removal-of-webhooks-redirection-support" class="heading-anchor_backwardsCompatibility">
          </div>Removal of Webhooks redirection support</div>
        <a aria-label="Skip link to Removal of webhooks redirection support" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-webhooks-redirection-support"></a></h3>
  
      <p><b>What is changing?</b></p>

<p>We are increasing the security of our Webhooks to provide more established and secure connections for our customers and partners.
  In order to eliminate the possibility for Webhook interceptions and unknown redirections to unauthorized destinations, we will be removing the support of webhooks using indirect URLs that redirect to another URL.</p>

      <p>Starting from <b>January 27, 2022</b>, we will begin to block webhooks that use indirect URL values for the webhook’s <code>subcription_url</code> if it redirects to another destination.</p>

<p><b>Who is affected?</b></p>
<p>Anyone who relies on active Webhooks with an indirect URL set as the <code>subscription_url</code> value.</p>

      <p>If you have any questions or comments, let us know in <a href="https://devcommunity.pipedrive.com/t/removal-of-webhooks-redirection-support/4769" target="_self">the Developer’s Community</a>.</p>
      
      
         <p class="published-on"><i>Published on October 28, 2021</i></p>
  </div>
</div>
`}</HTMLBlock>


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 27, 2022</span>
    </div>
    <div class="change-area">
      
      <h3 class="heading heading-2 header-scroll" align="">
        <div class="heading-anchor anchor waypoint" id="removal-of-webhooks-redirection-support"></div>
        <div class="heading-text"><div id="removal-of-webhooks-redirection-support" class="heading-anchor_backwardsCompatibility">
          </div>Removal of Webhooks redirection support</div>
        <a aria-label="Skip link to Removal of webhooks redirection support" class="heading-anchor-icon fa fa-anchor" 
           href="#removal-of-webhooks-redirection-support"></a></h3>
  
      <p><b>What is changing?</b></p>

<p>We are increasing the security of our Webhooks to provide more established and secure connections for our customers and partners.
  In order to eliminate the possibility for Webhook interceptions and unknown redirections to unauthorized destinations, we will be removing the support of webhooks using indirect URLs that redirect to another URL.</p>

      <p>Starting from <b>January 27, 2022</b>, we will begin to block webhooks that use indirect URL values for the webhook’s <code>subcription_url</code> if it redirects to another destination.</p>

<p><b>Who is affected?</b></p>
<p>Anyone who relies on active Webhooks with an indirect URL set as the <code>subscription_url</code> value.</p>

      <p>If you have any questions or comments, let us know in <a href="https://devcommunity.pipedrive.com/t/removal-of-webhooks-redirection-support/4769" target="_self">the Developer’s Community</a>.</p>
      
      
         <p class="published-on"><i>Published on October 28, 2021</i></p>
  </div>
</div>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog