<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Jul 15th, 2025</span>
    </div>
    <div class="change-area">
      <p>We are changing the behaviour of existing deals and leads endpoints to <b>no longer return archived items</b>. Requesting archived deals and leads will be available through <b>new dedicated API endpoints</b> instead. In addition, <b>archived deals and leads will not be editable through the API</b>.</p>
      <p>For a full overview of how archiving deals and leads works in Pipedrive, see our <a href="https://support.pipedrive.com/en/article/archive-deals-leads">Archiving Knowledge Base article</a>.</p>
      
      <h2>Summary of the changing endpoints</h2>
      <p>The following endpoints will be affected:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals">GET /v1/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals">GET /v2/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline">GET /v1/deals/timeline</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsSummary">GET /v1/deals/summary</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationDeals">GET /v1/organizations/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonDeals">GET /v1/persons/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductDeals">GET /v1/products/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelineDeals">GET /v1/pipelines/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Stages#getStageDeals">GET /v1/stages/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads">GET /v1/leads</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead">PATCH /v1/leads/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PUT /v1/deals/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PATCH /v2/deals/{id}</a></li>
      </ul>
      
      <h2>What is changing?</h2>
      <p><b>1. Archived deals will not be returned in deals and organizations, persons, products, pipelines and stages linked deals endpoints</b></p>
      
      <p>From Jul 15th, 2025 the following endpoints will not return archived deals by default:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals">GET /api/v1/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals">GET /api/v2/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline">GET /api/v1/deals/timeline</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsSummary">GET /api/v1/deals/summary</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationDeals">GET /api/v1/organizations/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonDeals">GET /api/v1/persons/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductDeals">GET /api/v1/products/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelineDeals">GET /api/v1/pipelines/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Stages#getStageDeals">GET /api/v1/stages/{id}/deals</a></li>
      </ul>
      
      <p>To retrieve archived deals, please use the following new API V2 endpoint instead:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getArchivedDeals">GET /api/v2/deals/archived</a></li>
      </ul>
      
      <p>Archived deals linked to a given organization, person, product, pipeline or stage can be fetched instead from the <a href="#">GET /api/v2/deals/archived</a> endpoint that support the following query parameters:</p>
      <ul>
        <li><code>org_id</code></li>
        <li><code>person_id</code></li>
        <li><code>pipeline_id</code></li>
        <li><code>stage_id</code></li>
      </ul>
      <p><i>Example: GET /api/v2/deals/archived?org_id=1</i></p>
      
      <b>Temporary support for V1 endpoints</b>
      <p>As announced in the <a href="https://developers.pipedrive.com/changelog/post/deprecation-of-selected-api-v1-endpoints">Deprecation of selected API v1 endpoints changelog post</a>, we are deprecating a number V1 endpoints related to deals by the end of 2025. To support a smooth transition, we are still providing temporary support for archived item endpoints in V1, allowing existing integrations to begin using archiving without immediately requiring a V2 migration.</p>
      
      <p>The following V1 endpoints will be available until the end of 2025:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getArchivedDeals">GET /v1/deals/archived</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getArchivedDealsTimeline">GET /v1/deals/timeline/archived</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getArchivedDealsSummary">GET /v1/deals/summary/archived</a></li>
      </ul>
      
      <br />
      <p><b>2. Archived leads will not be returned by default in leads endpoint</b></p>
      <p>From Jul 15th, 2025 the <a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads">GET /v1/leads</a> endpoint will not return archived deals by default and will only return. Instead the new <a href="#">GET /v1/leads/archived</a> endpoint can be used to fetch archived leads.</p>
      
      <br />
      <p><b>3. <code>archived_status</code> query parameter deprecation for leads endpoint</b></p>
      <p>From Jul 15th, 2025 the <a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads">GET /v1/leads</a> endpoint will ignore the <code>archived_status</code> query parameter and will only return not-archived leads.</p>
      
      <br />
      <p><b>4. Archived leads cannot be edited</b></p>
      <p>From Jul 15th, 2025 archived leads will not be editable through <a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead">PATCH /v1/leads/{id}</a> endpoint. Only the <code>is_archived</code> property can be edited to unarchive the lead.</p>
      
      <p>Here's an example of the <code>403</code> error response:<br />
        
      <div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar" role="tablist"><button aria-selected="true" class="CodeTabs_active" role="tab" type="button">JSON</button></div><div class="CodeTabs-inner" role="tabpanel"><pre><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><code class="rdmd-code lang-json theme-light" data-lang="json" name="" tabindex="0"><div class="cm-s-neo">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Archived lead cannot be updated."</span>,
  <span class="cm-property">"code"</span>: <span class="cm-string">"ERR_LEAD_ARCHIVED"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
  
  		<br />
		  <p><b>5. Archived deals cannot be edited</b></p>
		  <p>From Jul 15th, 2025 archived deals will no longer be editable through <a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PUT /v1/deals/{id}</a> and <a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PATCH /v2/deals/{id}</a> endpoints. Only the <code>is_archived</code> property can be edited to unarchive the deal.</p>
  
        <p>Here's an example of the <code>403</code> error response:<br />
          
           <div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar" role="tablist"><button aria-selected="true" class="CodeTabs_active" role="tab" type="button">JSON</button></div><div class="CodeTabs-inner" role="tabpanel"><pre><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><code class="rdmd-code lang-json theme-light" data-lang="json" name="" tabindex="0"><div class="cm-s-neo">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Archived deal cannot be updated"</span>,
  <span class="cm-property">"code"</span>: <span class="cm-string">"ERR_DEAL_ARCHIVED"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>

			<b>Temporary support for V1 endpoints</b>
      <p>As outlined in <a href="https://developers.pipedrive.com/changelog/post/deprecation-of-selected-api-v1-endpoints">this deprecation announcement</a>, API V1 endpoint for editing deals is also deprecated, and we recommend using the <a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PATCH /v2/deals/{id}</a> API V2 endpoint for updating deals going forward.
</p>
        <p>However, to support a smooth transition, temporary support for <a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PUT /v1/deals/{id}</a> will continue until the end of 2025.</p>

<br /><br />
     
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": [“Deals”, “Leads”, “Persons”,“Organizations", “Pipelines”, “Stages”], "email_description": “We are changing archived deals and leads to not be returned and archived deals and leads to not be editable in existing endpoints" }


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Jul 15th, 2025</span>
    </div>
    <div class="change-area">
      <p>We are changing the behaviour of existing deals and leads endpoints to <b>no longer return archived items</b>. Requesting archived deals and leads will be available through <b>new dedicated API endpoints</b> instead. In addition, <b>archived deals and leads will not be editable through the API</b>.</p>
      <p>For a full overview of how archiving deals and leads works in Pipedrive, see our <a href="https://support.pipedrive.com/en/article/archive-deals-leads">Archiving Knowledge Base article</a>.</p>
      
      <h2>Summary of the changing endpoints</h2>
      <p>The following endpoints will be affected:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals">GET /v1/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals">GET /v2/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline">GET /v1/deals/timeline</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsSummary">GET /v1/deals/summary</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationDeals">GET /v1/organizations/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonDeals">GET /v1/persons/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductDeals">GET /v1/products/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelineDeals">GET /v1/pipelines/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Stages#getStageDeals">GET /v1/stages/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads">GET /v1/leads</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead">PATCH /v1/leads/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PUT /v1/deals/{id}</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PATCH /v2/deals/{id}</a></li>
      </ul>
      
      <h2>What is changing?</h2>
      <p><b>1. Archived deals will not be returned in deals and organizations, persons, products, pipelines and stages linked deals endpoints</b></p>
      
      <p>From Jul 15th, 2025 the following endpoints will not return archived deals by default:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals">GET /api/v1/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals">GET /api/v2/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline">GET /api/v1/deals/timeline</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsSummary">GET /api/v1/deals/summary</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationDeals">GET /api/v1/organizations/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonDeals">GET /api/v1/persons/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductDeals">GET /api/v1/products/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelineDeals">GET /api/v1/pipelines/{id}/deals</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Stages#getStageDeals">GET /api/v1/stages/{id}/deals</a></li>
      </ul>
      
      <p>To retrieve archived deals, please use the following new API V2 endpoint instead:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getArchivedDeals">GET /api/v2/deals/archived</a></li>
      </ul>
      
      <p>Archived deals linked to a given organization, person, product, pipeline or stage can be fetched instead from the <a href="#">GET /api/v2/deals/archived</a> endpoint that support the following query parameters:</p>
      <ul>
        <li><code>org_id</code></li>
        <li><code>person_id</code></li>
        <li><code>pipeline_id</code></li>
        <li><code>stage_id</code></li>
      </ul>
      <p><i>Example: GET /api/v2/deals/archived?org_id=1</i></p>
      
      <b>Temporary support for V1 endpoints</b>
      <p>As announced in the <a href="https://developers.pipedrive.com/changelog/post/deprecation-of-selected-api-v1-endpoints">Deprecation of selected API v1 endpoints changelog post</a>, we are deprecating a number V1 endpoints related to deals by the end of 2025. To support a smooth transition, we are still providing temporary support for archived item endpoints in V1, allowing existing integrations to begin using archiving without immediately requiring a V2 migration.</p>
      
      <p>The following V1 endpoints will be available until the end of 2025:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getArchivedDeals">GET /v1/deals/archived</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getArchivedDealsTimeline">GET /v1/deals/timeline/archived</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getArchivedDealsSummary">GET /v1/deals/summary/archived</a></li>
      </ul>
      
      <br />
      <p><b>2. Archived leads will not be returned by default in leads endpoint</b></p>
      <p>From Jul 15th, 2025 the <a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads">GET /v1/leads</a> endpoint will not return archived deals by default and will only return. Instead the new <a href="#">GET /v1/leads/archived</a> endpoint can be used to fetch archived leads.</p>
      
      <br />
      <p><b>3. <code>archived_status</code> query parameter deprecation for leads endpoint</b></p>
      <p>From Jul 15th, 2025 the <a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeads">GET /v1/leads</a> endpoint will ignore the <code>archived_status</code> query parameter and will only return not-archived leads.</p>
      
      <br />
      <p><b>4. Archived leads cannot be edited</b></p>
      <p>From Jul 15th, 2025 archived leads will not be editable through <a href="https://developers.pipedrive.com/docs/api/v1/Leads#updateLead">PATCH /v1/leads/{id}</a> endpoint. Only the <code>is_archived</code> property can be edited to unarchive the lead.</p>
      
      <p>Here's an example of the <code>403</code> error response:<br />
        
      <div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar" role="tablist"><button aria-selected="true" class="CodeTabs_active" role="tab" type="button">JSON</button></div><div class="CodeTabs-inner" role="tabpanel"><pre><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><code class="rdmd-code lang-json theme-light" data-lang="json" name="" tabindex="0"><div class="cm-s-neo">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Archived lead cannot be updated."</span>,
  <span class="cm-property">"code"</span>: <span class="cm-string">"ERR_LEAD_ARCHIVED"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>
  
  		<br />
		  <p><b>5. Archived deals cannot be edited</b></p>
		  <p>From Jul 15th, 2025 archived deals will no longer be editable through <a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PUT /v1/deals/{id}</a> and <a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PATCH /v2/deals/{id}</a> endpoints. Only the <code>is_archived</code> property can be edited to unarchive the deal.</p>
  
        <p>Here's an example of the <code>403</code> error response:<br />
          
           <div class="CodeTabs CodeTabs_initial theme-light"><div class="CodeTabs-toolbar" role="tablist"><button aria-selected="true" class="CodeTabs_active" role="tab" type="button">JSON</button></div><div class="CodeTabs-inner" role="tabpanel"><pre><button aria-label="Copy Code" class="rdmd-code-copy fa"></button><code class="rdmd-code lang-json theme-light" data-lang="json" name="" tabindex="0"><div class="cm-s-neo">{
  <span class="cm-property">"success"</span>: <span class="cm-atom">false</span>,
  <span class="cm-property">"error"</span>: <span class="cm-string">"Archived deal cannot be updated"</span>,
  <span class="cm-property">"code"</span>: <span class="cm-string">"ERR_DEAL_ARCHIVED"</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"data"</span>: <span class="cm-atom">null</span>,
  <span class="cm-property">"additional_data</span>: <span class="cm-atom">null</span>
}

</div></code></pre></div></div>
			</p>

			<b>Temporary support for V1 endpoints</b>
      <p>As outlined in <a href="https://developers.pipedrive.com/changelog/post/deprecation-of-selected-api-v1-endpoints">this deprecation announcement</a>, API V1 endpoint for editing deals is also deprecated, and we recommend using the <a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PATCH /v2/deals/{id}</a> API V2 endpoint for updating deals going forward.
</p>
        <p>However, to support a smooth transition, temporary support for <a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PUT /v1/deals/{id}</a> will continue until the end of 2025.</p>

<br /><br />
     
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Breaking change: archived deals and leads will not be returned and archived deals and leads will not be editable in existing endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Jan 1st, 2026</span>
    </div>
    <div class="change-area">
      <p>We are deprecating a set of legacy API v1 endpoints following the release of their more performant, efficient, and modern <a href="https://pipedrive.readme.io/docs/pipedrive-api-v2">API v2 equivalents</a>. This is part of our ongoing efforts to improve the reliability, scalability, and developer experience of our <a href="https://pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api">API platform</a>.</p>
      
      <h2>What will change?</h2>
      <p>We are deprecating specific API v1 endpoints (listed below) that now have direct replacements in API v2 — this does not affect the entire API v1 platform. These API v2 endpoints offer improved performance and consume 50% fewer tokens under our <a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting">Token-Based Rate Limiting system</a>. Deprecated endpoints will remain accessible until <b>December 31, 2025</b>. After this date, their availability and functionality will no longer be guaranteed.</p>
      
      <h3>Deprecated endpoints:</h3>
      
      <b>Activities</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/activities</code> in favor of <code>GET /api/v2/activities</code></li>
        <li>Deprecated <code>GET /v1/activities/collection</code> in favor of <code>GET /api/v2/activities</code></li>
        <li>Deprecated <code>GET /v1/activities/{id}</code> in favor of <code>GET /api/v2/activities/{id}</code></li>
        <li>Deprecated <code>POST /v1/activities</code> in favor of <code>POST /api/v2/activities</code></li>
        <li>Deprecated <code>PUT /v1/activities/{id}</code> in favor of <code>PATCH /api/v2/activities/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/activities/{id}</code> in favor of <code>DELETE /api/v2/activities/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/activities</code> in favor of <code>DELETE /api/v2/activities/{id}</code></li>
      </ul>
      
      <b>Deals</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/deals</code> in favor of <code>GET /api/v2/deals</code></li>
        <li>Deprecated <code>GET /v1/deals/collection</code> in favor of <code>GET /api/v2/deals</code></li>
        <li>Deprecated <code>GET /v1/deals/{id}</code> in favor of <code>GET /api/v2/deals/{id}</code></li>
        <li>Deprecated <code>GET /v1/deals/search</code> in favor of <code>GET /api/v2/deals/search</code></li>
        <li>Deprecated <code>POST /v1/deals</code> in favor of <code>POST /api/v2/deals</code></li>
        <li>Deprecated <code>PUT /v1/deals/{id}</code> in favor of <code>PATCH /api/v2/deals</code></li>
        <li>Deprecated <code>DELETE /v1/deals/{id}</code> in favor of <code>DELETE /api/v2/deals/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/deals</code> in favor of <code>DELETE /api/v2/deals/{id}</code></li>
        <li>Deprecated <code>GET /v1/deals/{id}/activities</code> in favor of <code>GET /api/v2/activities?deal_id={id}</code></li>
        <li>Deprecated <code>GET /v1/deals/{id}/persons</code> in favor of <code>GET /api/v2/persons?deal_id={id}</code></li>
        <li>Deprecated <code>GET /v1/deals/{id}/products</code> in favor of <code>GET /api/v2/deals/{id}/products</code></li>
      </ul>
      
			<b>Persons</b><br />
			<ul>
        <li>Deprecated <code>GET /v1/persons</code> in favor of <code>GET /api/v2/persons</code></li>
        <li>Deprecated <code>GET /v1/persons/collection</code> in favor of <code>GET /api/v2/persons</code></li>
        <li>Deprecated <code>GET /v1/persons/{id}</code> in favor of <code>GET /api/v2/persons/{id}</code></li>
        <li>Deprecated <code>GET /v1/persons/search</code> in favor of <code>GET /api/v2/persons/search</code></li>
        <li>Deprecated <code>POST /v1/persons</code> in favor of <code>POST /api/v2/persons</code></li>
        <li>Deprecated <code>PUT /v1/persons/{id}</code> in favor of <code>PATCH /api/v2/persons/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/persons/{id}</code> in favor of <code>DELETE /api/v2/persons/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/persons</code> in favor of <code>DELETE /api/v2/persons/{id}</code></li>
        <li>Deprecated <code>GET /v1/persons/{id}/deals</code> in favor of <code>GET /api/v2/deals?person_id={id}</code></li>
        <li>Deprecated <code>GET /v1/persons/{id}/activities</code> in favor of <code>GET /api/v2/activities?person_id={id}</code></li>
      </ul>
      
      <b>Organizations</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/organizations</code> in favor of <code>GET /api/v2/organizations</code></li>
        <li>Deprecated <code>GET /v1/organizations/collection</code> in favor of <code>GET /api/v2/organizations</code></li>
        <li>Deprecated <code>GET /v1/organizations/{id}</code> in favor of <code>GET /api/v2/organizations/{id}</code></li>
        <li>Deprecated <code>GET /v1/organizations/search</code> in favor of <code>GET /api/v2/organizations/search</code></li>
        <li>Deprecated <code>POST /v1/organizations</code> in favor of <code>POST /api/v2/organizations</code></li>
        <li>Deprecated <code>PUT /v1/organizations/{id}</code> in favor of <code>PATCH /api/v2/organizations/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/organizations/{id}</code> in favor of <code>DELETE /api/v2/organizations/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/organizations</code> in favor of <code>DELETE /api/v2/organizations/{id}</code></li>
        <li>Deprecated <code>GET /v1/organizations/{id}/deals</code> in favor of <code>GET /api/v2/deals?org_id={id}</code></li>
        <li>Deprecated <code>GET /v1/organizations/{id}/activities</code> in favor of <code>GET /api/v2/activities?org_id={id}</code></li>
        <li>Deprecated <code>GET /v1/organizations/{id}/persons</code> in favor of <code>GET /api/v2/persons?org_id={id}</code></li>
      </ul>
      
      <b>Products</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/products</code> in favor of <code>GET /api/v2/products</code></li>
        <li>Deprecated <code>GET /v1/products/{id}</code> in favor of <code>GET /api/v2/products/{id}</code></li>
        <li>Deprecated <code>GET /v1/products/search</code> in favor of <code>GET /api/v2/products/search</code></li>
        <li>Deprecated <code>POST /v1/products</code> in favor of <code>POST /api/v2/products</code></li>
        <li>Deprecated <code>PUT /v1/products/{id}</code> in favor of <code>PATCH /api/v2/products/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/products/{id}</code> in favor of <code>DELETE /api/v2/products/{id}</code></li>
      </ul>
      
      <b>Pipelines</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/pipelines</code> in favor of <code>GET /api/v2/pipelines</code></li>
        <li>Deprecated <code>GET /v1/pipelines/{id}</code> in favor of <code>GET /api/v2/pipelines/{id}</code></li>
        <li>Deprecated <code>POST /v1/pipelines</code> in favor of <code>POST /api/v2/pipelines</code></li>
        <li>Deprecated <code>PUT /v1/pipelines/{id}</code> in favor of <code>PATCH /api/v2/pipelines/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/pipelines/{id}</code> in favor of <code>DELETE /api/v2/pipelines/{id}</code></li>
      </ul>
      
      <b>Stages</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/stages</code> in favor of <code>GET /api/v2/stages</code></li>
        <li>Deprecated <code>GET /v1/stages/{id}</code> in favor of <code>GET /api/v2/stages/{id}</code></li>
        <li>Deprecated <code>POST /v1/stages</code> in favor of <code>POST /api/v2/stages</code></li>
        <li>Deprecated <code>PUT /v1/stages/{id}</code> in favor of <code>PATCH /api/v2/stages/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/stages/{id}</code> in favor of <code>DELETE /api/v2/stages/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/stages</code> in favor of <code>DELETE /api/v2/stages/{id}</code></li>
      </ul>
      
      <b>Search</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/itemSearch</code> in favor of <code>GET /api/v2/itemSearch</code></li>
        <li>Deprecated <code>GET /v1/itemSearch/field</code> in favor of <code>GET /api/v2/itemSearch/field</code></li>
      </ul>
      
      <h2>Why is it changing?</h2>
      <p>We’ve introduced API v2 as a faster, more consistent, and token-efficient evolution of our platform. These endpoints deliver enhanced performance, a better developer experience, and help reduce token consumption under <a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting">Token Based Rate Limiting</a>. By gradually deprecating older endpoints, we can focus our development efforts on continuing to improve and expand API v2.</p>
      
      <h2>Who is affected?</h2>
      <p>This change affects any customer, partner, or vendor currently using the deprecated API v1 endpoints.</p>
      
      <h2>What should you do?</h2>
      <p>No immediate action is required — your existing integrations using these endpoints will continue to work until the end of 2025.</p>
      
      <p>To ensure a smooth transition:
	      <ul>
          <li>We recommend <b>starting to migrate to API v2 equivalents as soon as possible</b> to take full advantage of performance improvements and avoid future disruption.</li>
          <li>You can use the <a href="https://app.pipedrive.com/settings/usage-caps/api-usage">API Usage Dashboard</a> in your company settings to identify if your organization is actively using any of the deprecated endpoints.</li>
          <li>A step-by-step <a href="https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide">API v2 Migration Guide</a> is available to help your development team plan and implement changes.</li>
	      </ul>
      </p>
  
	  	<p>If you work with a Pipedrive Partner or Customer Success contact, feel free to reach out for additional guidance or migration support.</p>
  
  	<h2>When is it happening?</h2>
	  <p>Deprecation takes effect as of today’s announcement. The affected API v1 endpoints will remain available until <b>December 31, 2025</b>, after which their availability and functionality will no longer be guaranteed.</p>
  
  <h2>Additional resources</h2>
  <ul>
    <li><a href="https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide">API v2 migration guide</a></li>
    <li><a href="https://developers.pipedrive.com/docs/api/v1">API reference</a></li>
    <li><a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting">Token based rate limiting</a></li>
  </ul>
        
  </div>
</div>
`}</HTMLBlock>

Breaking change: Deprecation of selected API v1 endpoints


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Jan 1st, 2026</span>
    </div>
    <div class="change-area">
      <p>We are deprecating a set of legacy API v1 endpoints following the release of their more performant, efficient, and modern <a href="https://pipedrive.readme.io/docs/pipedrive-api-v2">API v2 equivalents</a>. This is part of our ongoing efforts to improve the reliability, scalability, and developer experience of our <a href="https://pipedrive.readme.io/docs/core-api-concepts-about-pipedrive-api">API platform</a>.</p>
      
      <h2>What will change?</h2>
      <p>We are deprecating specific API v1 endpoints (listed below) that now have direct replacements in API v2 — this does not affect the entire API v1 platform. These API v2 endpoints offer improved performance and consume 50% fewer tokens under our <a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting">Token-Based Rate Limiting system</a>. Deprecated endpoints will remain accessible until <b>December 31, 2025</b>. After this date, their availability and functionality will no longer be guaranteed.</p>
      
      <h3>Deprecated endpoints:</h3>
      
      <b>Activities</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/activities</code> in favor of <code>GET /api/v2/activities</code></li>
        <li>Deprecated <code>GET /v1/activities/collection</code> in favor of <code>GET /api/v2/activities</code></li>
        <li>Deprecated <code>GET /v1/activities/{id}</code> in favor of <code>GET /api/v2/activities/{id}</code></li>
        <li>Deprecated <code>POST /v1/activities</code> in favor of <code>POST /api/v2/activities</code></li>
        <li>Deprecated <code>PUT /v1/activities/{id}</code> in favor of <code>PATCH /api/v2/activities/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/activities/{id}</code> in favor of <code>DELETE /api/v2/activities/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/activities</code> in favor of <code>DELETE /api/v2/activities/{id}</code></li>
      </ul>
      
      <b>Deals</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/deals</code> in favor of <code>GET /api/v2/deals</code></li>
        <li>Deprecated <code>GET /v1/deals/collection</code> in favor of <code>GET /api/v2/deals</code></li>
        <li>Deprecated <code>GET /v1/deals/{id}</code> in favor of <code>GET /api/v2/deals/{id}</code></li>
        <li>Deprecated <code>GET /v1/deals/search</code> in favor of <code>GET /api/v2/deals/search</code></li>
        <li>Deprecated <code>POST /v1/deals</code> in favor of <code>POST /api/v2/deals</code></li>
        <li>Deprecated <code>PUT /v1/deals/{id}</code> in favor of <code>PATCH /api/v2/deals</code></li>
        <li>Deprecated <code>DELETE /v1/deals/{id}</code> in favor of <code>DELETE /api/v2/deals/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/deals</code> in favor of <code>DELETE /api/v2/deals/{id}</code></li>
        <li>Deprecated <code>GET /v1/deals/{id}/activities</code> in favor of <code>GET /api/v2/activities?deal_id={id}</code></li>
        <li>Deprecated <code>GET /v1/deals/{id}/persons</code> in favor of <code>GET /api/v2/persons?deal_id={id}</code></li>
        <li>Deprecated <code>GET /v1/deals/{id}/products</code> in favor of <code>GET /api/v2/deals/{id}/products</code></li>
      </ul>
      
			<b>Persons</b><br />
			<ul>
        <li>Deprecated <code>GET /v1/persons</code> in favor of <code>GET /api/v2/persons</code></li>
        <li>Deprecated <code>GET /v1/persons/collection</code> in favor of <code>GET /api/v2/persons</code></li>
        <li>Deprecated <code>GET /v1/persons/{id}</code> in favor of <code>GET /api/v2/persons/{id}</code></li>
        <li>Deprecated <code>GET /v1/persons/search</code> in favor of <code>GET /api/v2/persons/search</code></li>
        <li>Deprecated <code>POST /v1/persons</code> in favor of <code>POST /api/v2/persons</code></li>
        <li>Deprecated <code>PUT /v1/persons/{id}</code> in favor of <code>PATCH /api/v2/persons/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/persons/{id}</code> in favor of <code>DELETE /api/v2/persons/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/persons</code> in favor of <code>DELETE /api/v2/persons/{id}</code></li>
        <li>Deprecated <code>GET /v1/persons/{id}/deals</code> in favor of <code>GET /api/v2/deals?person_id={id}</code></li>
        <li>Deprecated <code>GET /v1/persons/{id}/activities</code> in favor of <code>GET /api/v2/activities?person_id={id}</code></li>
      </ul>
      
      <b>Organizations</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/organizations</code> in favor of <code>GET /api/v2/organizations</code></li>
        <li>Deprecated <code>GET /v1/organizations/collection</code> in favor of <code>GET /api/v2/organizations</code></li>
        <li>Deprecated <code>GET /v1/organizations/{id}</code> in favor of <code>GET /api/v2/organizations/{id}</code></li>
        <li>Deprecated <code>GET /v1/organizations/search</code> in favor of <code>GET /api/v2/organizations/search</code></li>
        <li>Deprecated <code>POST /v1/organizations</code> in favor of <code>POST /api/v2/organizations</code></li>
        <li>Deprecated <code>PUT /v1/organizations/{id}</code> in favor of <code>PATCH /api/v2/organizations/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/organizations/{id}</code> in favor of <code>DELETE /api/v2/organizations/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/organizations</code> in favor of <code>DELETE /api/v2/organizations/{id}</code></li>
        <li>Deprecated <code>GET /v1/organizations/{id}/deals</code> in favor of <code>GET /api/v2/deals?org_id={id}</code></li>
        <li>Deprecated <code>GET /v1/organizations/{id}/activities</code> in favor of <code>GET /api/v2/activities?org_id={id}</code></li>
        <li>Deprecated <code>GET /v1/organizations/{id}/persons</code> in favor of <code>GET /api/v2/persons?org_id={id}</code></li>
      </ul>
      
      <b>Products</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/products</code> in favor of <code>GET /api/v2/products</code></li>
        <li>Deprecated <code>GET /v1/products/{id}</code> in favor of <code>GET /api/v2/products/{id}</code></li>
        <li>Deprecated <code>GET /v1/products/search</code> in favor of <code>GET /api/v2/products/search</code></li>
        <li>Deprecated <code>POST /v1/products</code> in favor of <code>POST /api/v2/products</code></li>
        <li>Deprecated <code>PUT /v1/products/{id}</code> in favor of <code>PATCH /api/v2/products/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/products/{id}</code> in favor of <code>DELETE /api/v2/products/{id}</code></li>
      </ul>
      
      <b>Pipelines</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/pipelines</code> in favor of <code>GET /api/v2/pipelines</code></li>
        <li>Deprecated <code>GET /v1/pipelines/{id}</code> in favor of <code>GET /api/v2/pipelines/{id}</code></li>
        <li>Deprecated <code>POST /v1/pipelines</code> in favor of <code>POST /api/v2/pipelines</code></li>
        <li>Deprecated <code>PUT /v1/pipelines/{id}</code> in favor of <code>PATCH /api/v2/pipelines/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/pipelines/{id}</code> in favor of <code>DELETE /api/v2/pipelines/{id}</code></li>
      </ul>
      
      <b>Stages</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/stages</code> in favor of <code>GET /api/v2/stages</code></li>
        <li>Deprecated <code>GET /v1/stages/{id}</code> in favor of <code>GET /api/v2/stages/{id}</code></li>
        <li>Deprecated <code>POST /v1/stages</code> in favor of <code>POST /api/v2/stages</code></li>
        <li>Deprecated <code>PUT /v1/stages/{id}</code> in favor of <code>PATCH /api/v2/stages/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/stages/{id}</code> in favor of <code>DELETE /api/v2/stages/{id}</code></li>
        <li>Deprecated <code>DELETE /v1/stages</code> in favor of <code>DELETE /api/v2/stages/{id}</code></li>
      </ul>
      
      <b>Search</b><br />
      <ul>
        <li>Deprecated <code>GET /v1/itemSearch</code> in favor of <code>GET /api/v2/itemSearch</code></li>
        <li>Deprecated <code>GET /v1/itemSearch/field</code> in favor of <code>GET /api/v2/itemSearch/field</code></li>
      </ul>
      
      <h2>Why is it changing?</h2>
      <p>We’ve introduced API v2 as a faster, more consistent, and token-efficient evolution of our platform. These endpoints deliver enhanced performance, a better developer experience, and help reduce token consumption under <a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting">Token Based Rate Limiting</a>. By gradually deprecating older endpoints, we can focus our development efforts on continuing to improve and expand API v2.</p>
      
      <h2>Who is affected?</h2>
      <p>This change affects any customer, partner, or vendor currently using the deprecated API v1 endpoints.</p>
      
      <h2>What should you do?</h2>
      <p>No immediate action is required — your existing integrations using these endpoints will continue to work until the end of 2025.</p>
      
      <p>To ensure a smooth transition:
	      <ul>
          <li>We recommend <b>starting to migrate to API v2 equivalents as soon as possible</b> to take full advantage of performance improvements and avoid future disruption.</li>
          <li>You can use the <a href="https://app.pipedrive.com/settings/usage-caps/api-usage">API Usage Dashboard</a> in your company settings to identify if your organization is actively using any of the deprecated endpoints.</li>
          <li>A step-by-step <a href="https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide">API v2 Migration Guide</a> is available to help your development team plan and implement changes.</li>
	      </ul>
      </p>
  
	  	<p>If you work with a Pipedrive Partner or Customer Success contact, feel free to reach out for additional guidance or migration support.</p>
  
  	<h2>When is it happening?</h2>
	  <p>Deprecation takes effect as of today’s announcement. The affected API v1 endpoints will remain available until <b>December 31, 2025</b>, after which their availability and functionality will no longer be guaranteed.</p>
  
  <h2>Additional resources</h2>
  <ul>
    <li><a href="https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide">API v2 migration guide</a></li>
    <li><a href="https://developers.pipedrive.com/docs/api/v1">API reference</a></li>
    <li><a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting">Token based rate limiting</a></li>
  </ul>
        
  </div>
</div>


Deprecation of selected API v1 endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Mar 31st, 2025</span>
    </div>
    <div class="change-area">
      <p>We released new set of API v2 endpoints for entity followers:</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealFollowers" target="_blank">GET /api/v2/deals/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealFollowersChangelog" target="_blank">GET /api/v2/deals/:id/followers/changelog</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealFollower" target="_blank">POST /api/v2/deals/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#deleteDealFollower" target="_blank">DELETE /api/v2/deals/:id/followers/:id</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFollowers" target="_blank">GET /api/v2/persons/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFollowersChangelog" target="_blank">GET /api/v2/persons/:id/followers/changelog</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#addPersonFollower" target="_blank">POST /api/v2/persons/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#deletePersonFollower" target="_blank">DELETE /api/v2/persons/:id/followers/:id</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationFollowers" target="_blank">GET /api/v2/organizations/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationFollowersChangelog" target="_blank">GET /api/v2/organizations/:id/followers/changelog</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganizationFollower" target="_blank">POST /api/v2/organizations/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#deleteOrganizationFollower" target="_blank">DELETE /api/v2/organizations/:id/followers/:id</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductFollowers" target="_blank">GET /api/v2/products/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductFollowersChangelog" target="_blank">GET /api/v2/products/:id/followers/changelog</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProductFollower" target="_blank">POST /api/v2/products/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#deleteProductFollower" target="_blank">DELETE /api/v2/products/:id/followers/:id</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserFollowers" target="_blank">GET /api/v2/users/:id/followers</a></li>
      </ul>      
     
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Mar 31st, 2025</span>
    </div>
    <div class="change-area">
      <p>We released new set of API v2 endpoints for entity followers:</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealFollowers" target="_blank">GET /api/v2/deals/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealFollowersChangelog" target="_blank">GET /api/v2/deals/:id/followers/changelog</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealFollower" target="_blank">POST /api/v2/deals/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#deleteDealFollower" target="_blank">DELETE /api/v2/deals/:id/followers/:id</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFollowers" target="_blank">GET /api/v2/persons/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonFollowersChangelog" target="_blank">GET /api/v2/persons/:id/followers/changelog</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#addPersonFollower" target="_blank">POST /api/v2/persons/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#deletePersonFollower" target="_blank">DELETE /api/v2/persons/:id/followers/:id</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationFollowers" target="_blank">GET /api/v2/organizations/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationFollowersChangelog" target="_blank">GET /api/v2/organizations/:id/followers/changelog</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganizationFollower" target="_blank">POST /api/v2/organizations/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#deleteOrganizationFollower" target="_blank">DELETE /api/v2/organizations/:id/followers/:id</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductFollowers" target="_blank">GET /api/v2/products/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductFollowersChangelog" target="_blank">GET /api/v2/products/:id/followers/changelog</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#addProductFollower" target="_blank">POST /api/v2/products/:id/followers</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#deleteProductFollower" target="_blank">DELETE /api/v2/products/:id/followers/:id</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Users#getUserFollowers" target="_blank">GET /api/v2/users/:id/followers</a></li>
      </ul>      
     
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Releasing new API v2 endpoints for followers

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Jun 27th, 2025</span>
    </div>
    <div class="change-area">
      <p>As the Recurring Revenue feature will be deprecated and replaced by the new Revenue Management (Products as Subscriptions & Product Revenue Forecast Report), all the endpoints from Subscriptions API will be removed. The current Products API and the new Installments API should be used instead to support the new Revenue Management feature.</p>
      
      <h2>What will change? </h2>
      <p>We have now deprecated the following 9 API endpoints which will be removed starting on <b>Jun 27, 2025</b>:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#getSubscription" target="_blank">GET /v1/subscriptions/{id}</a> - Returns details of an installment or a recurring subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#findSubscriptionByDeal" target="_blank">GET /v1/subscriptions/find/{dealId}</a> - Returns details of an installment or a recurring subscription by the deal ID.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#getSubscriptionPayments" target="_blank">GET /v1/subscriptions/{id}/payments</a> - Returns all payments of an installment or recurring subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#addRecurringSubscription" target="_blank">POST /v1/subscriptions/recurring</a> - Adds a new recurring subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#addSubscriptionInstallment" target="_blank">POST /v1/subscriptions/installment</a> - Adds a new installment subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#updateRecurringSubscription" target="_blank">PUT /v1/subscriptions/recurring/{id}</a> - Updates a recurring subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#updateSubscriptionInstallment" target="_blank">PUT /v1/subscriptions/installment/{id}</a> - Updates an installment subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#cancelRecurringSubscription" target="_blank">PUT /v1/subscriptions/recurring/{id}/cancel</a> - Cancels a recurring subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#deleteSubscription" target="_blank">DELETE /v1/subscriptions/{id}</a> - Marks an installment or a recurring subscription as deleted.</li>
      </ul>

      <h2>Why is it changing?</h2>
      <p>Current Recurring Revenue is a detached feature from Pipedrive with low usage. The current feature has several limitations that block customers from adopting the feature and from successfully using it to track all the recurring and one-time products that they are selling, impacting the end-to-end workflow of subscription based businesses.
For this reason, we have a new alternative on the top of Products Feature in the context of the Revenue Management Concept (Products as Subscriptions & Product Revenue Forecasting Report).</p>
      
      <h2>Who is affected?</h2>
      <p>In case you are using the previously listed 9 deprecated API endpoints in your code or 3rd party app/integration, please remove any dependency on these endpoints as soon as possible or by <b>June 27, 2025</b> the latest.</p>

			<p>For any help needed to migrate to Products and Installments API, check out our <a href="https://pipedrive.readme.io/docs/subscriptions-api-migration-guide">Subscription API migration guide</a></p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
        <li><a href="https://pipedrive.readme.io/docs/subscriptions-api-migration-guide">Subscription API migration guide</a></li>
        
      </ul>      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Subscriptions”], "email_description": "We are deprecating the Subscriptions API" }


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Jun 27th, 2025</span>
    </div>
    <div class="change-area">
      <p>As the Recurring Revenue feature will be deprecated and replaced by the new Revenue Management (Products as Subscriptions & Product Revenue Forecast Report), all the endpoints from Subscriptions API will be removed. The current Products API and the new Installments API should be used instead to support the new Revenue Management feature.</p>
      
      <h2>What will change? </h2>
      <p>We have now deprecated the following 9 API endpoints which will be removed starting on <b>Jun 27, 2025</b>:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#getSubscription" target="_blank">GET /v1/subscriptions/{id}</a> - Returns details of an installment or a recurring subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#findSubscriptionByDeal" target="_blank">GET /v1/subscriptions/find/{dealId}</a> - Returns details of an installment or a recurring subscription by the deal ID.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#getSubscriptionPayments" target="_blank">GET /v1/subscriptions/{id}/payments</a> - Returns all payments of an installment or recurring subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#addRecurringSubscription" target="_blank">POST /v1/subscriptions/recurring</a> - Adds a new recurring subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#addSubscriptionInstallment" target="_blank">POST /v1/subscriptions/installment</a> - Adds a new installment subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#updateRecurringSubscription" target="_blank">PUT /v1/subscriptions/recurring/{id}</a> - Updates a recurring subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#updateSubscriptionInstallment" target="_blank">PUT /v1/subscriptions/installment/{id}</a> - Updates an installment subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#cancelRecurringSubscription" target="_blank">PUT /v1/subscriptions/recurring/{id}/cancel</a> - Cancels a recurring subscription.</li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Subscriptions#deleteSubscription" target="_blank">DELETE /v1/subscriptions/{id}</a> - Marks an installment or a recurring subscription as deleted.</li>
      </ul>

      <h2>Why is it changing?</h2>
      <p>Current Recurring Revenue is a detached feature from Pipedrive with low usage. The current feature has several limitations that block customers from adopting the feature and from successfully using it to track all the recurring and one-time products that they are selling, impacting the end-to-end workflow of subscription based businesses.
For this reason, we have a new alternative on the top of Products Feature in the context of the Revenue Management Concept (Products as Subscriptions & Product Revenue Forecasting Report).</p>
      
      <h2>Who is affected?</h2>
      <p>In case you are using the previously listed 9 deprecated API endpoints in your code or 3rd party app/integration, please remove any dependency on these endpoints as soon as possible or by <b>June 27, 2025</b> the latest.</p>

			<p>For any help needed to migrate to Products and Installments API, check out our <a href="https://pipedrive.readme.io/docs/subscriptions-api-migration-guide">Subscription API migration guide</a></p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
        <li><a href="https://pipedrive.readme.io/docs/subscriptions-api-migration-guide">Subscription API migration guide</a></li>
        
      </ul>      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Removal of Subscriptions API, replaced by Product Subscriptions API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 18th, 2025</span>
    </div>
    <div class="change-area">
      <p>We are removing undocumented <code>deals_summary</code> property from <code>/v1/pipelines/:id</code> and <code>/v1/stages/:id</code> endpoints.</p>
      
      <h2>Why is it changing?</h2>
      <p>To improve the performance of the endpoints.</p>

      <h2>What is changing?</h2>
      <p>From <b>May 18th, 2025</b> the <code>deals_summary</code> property will be removed from the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Stages#getStage" target="_blank"><code>GET /v1/stages/{id}</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipeline" target="_blank"><code>GET /v1/pipelines/{id}</code></a></li>
      </ul>  
      <p>For fetching deal summary please use the dedicated <a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsSummary" target="_blank"><code>GET /v1/deals/summary</code></a> endpoint.</p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Pipelines”, “Stages”], "email_description": "We are removing deals_summary property from stages & pipelines endpoints" }


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">May 18th, 2025</span>
    </div>
    <div class="change-area">
      <p>We are removing undocumented <code>deals_summary</code> property from <code>/v1/pipelines/:id</code> and <code>/v1/stages/:id</code> endpoints.</p>
      
      <h2>Why is it changing?</h2>
      <p>To improve the performance of the endpoints.</p>

      <h2>What is changing?</h2>
      <p>From <b>May 18th, 2025</b> the <code>deals_summary</code> property will be removed from the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Stages#getStage" target="_blank"><code>GET /v1/stages/{id}</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipeline" target="_blank"><code>GET /v1/pipelines/{id}</code></a></li>
      </ul>  
      <p>For fetching deal summary please use the dedicated <a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsSummary" target="_blank"><code>GET /v1/deals/summary</code></a> endpoint.</p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

  </div>
</div>


Breaking change: removal of deals_summary property from pipelines/{id} and stages/{id} endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">March 13th, 2025</span>
    </div>
    <div class="change-area">
      <p>We are excited to announce that a set of API v2 endpoints has officially moved out of BETA status and is now stable. These endpoints provide a more efficient and performant way to interact with Pipedrive, replacing specific APIv1 endpoints.</p>
      
      <h2>Why This Matters?</h2>
      <ul>
        <li><b>Better Performance</b>: API v2 endpoints are optimized for speed and reliability.</li>
        <li><b>Lower Token Costs</b>: These endpoints consume fewer API tokens per request, making them a more cost-effective option.</li>
        <li><b>Improved Stability</b>: As stable endpoints, they are fully supported and ready for production use.</li>
      </ul>
      
      <h2>Optimize API Usage with Token-Based Rate Limiting</h2>
      <p>Since the introduction of <a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting#token-based-rate-limiting" target="_blank">Token-Based Rate Limiting</a> last year, we encourage all developers to migrate to available stable API v2 endpoints. Doing so will help you stay within your API token budget while maintaining seamless integration or even allow you to make more requests within the same budget.</p>

      <h2>What's Changing?</h2>
      <p>The following API v2 endpoints are now stable:</p>
      <ul>
        <li><code>GET /api/v2/activities</code></li>
        <li><code>GET /api/v2/activities/:id</code></li>
        <li><code>POST /api/v2/activities</code></li>
        <li><code>PATCH /api/v2/activities/:id</code></li>
        <li><code>DELETE /api/v2/activities/:id</code></li>
        <li><code>GET /api/v2/deals</code></li>
        <li><code>GET /api/v2/deals/:id</code></li>
        <li><code>POST /api/v2/deals</code></li>
        <li><code>PATCH /api/v2/deals/:id</code></li>
        <li><code>DELETE /api/v2/deals/:id</code></li>
        <li><code>GET /api/v2/persons</code></li>
        <li><code>GET /api/v2/persons/:id</code></li>
        <li><code>POST /api/v2/persons</code></li>
        <li><code>PATCH /api/v2/persons/:id</code></li>
        <li><code>DELETE /api/v2/persons/:id</code></li>
        <li><code>GET /api/v2/organizations</code></li>
        <li><code>GET /api/v2/organizations/:id</code></li>
        <li><code>POST /api/v2/organizations</code></li>
        <li><code>PATCH /api/v2/organizations/:id</code></li>
        <li><code>DELETE /api/v2/organizations/:id</code></li>
        <li><code>GET /api/v2/products</code></li>
        <li><code>GET /api/v2/products/:id</code></li>
        <li><code>POST /api/v2/products</code></li>
        <li><code>PATCH /api/v2/products/:id</code></li>
        <li><code>DELETE /api/v2/products/:id</code></li>
        <li><code>GET /api/v2/products/:id/variations</code></li>
        <li><code>GET /api/v2/products/variations</code></li>
        <li><code>POST /api/v2/products/:id/variations</code></li>
        <li><code>PATCH /api/v2/products/:id/variations/:id</code></li>
        <li><code>DELETE /api/v2/products/:id/variations/:id</code></li>
        <li><code>GET /api/v2/deals/:id/products</code></li>
        <li><code>GET /api/v2/deals/products</code></li>
        <li><code>POST /api/v2/persons/:id/products</code></li>
        <li><code>PATCH /api/v2/persons/:id/products</code></li>
        <li><code>DELETE /api/v2/persons/:id/products/:id</code></li>
        <li><code>GET /api/v2/itemSearch</code></li>
        <li><code>GET /api/v2/itemSearch/field</code></li>
        <li><code>GET /api/v2/deals/search</code></li>
        <li><code>GET /api/v2/leads/search</code></li>
        <li><code>GET /api/v2/persons/search</code></li>
        <li><code>GET /api/v2/organizations/search</code></li>
        <li><code>GET /api/v2/products/search</code></li>
        <li><code>GET /api/v2/pipelines</code></li>
        <li><code>GET /api/v2/pipelines/:id</code></li>
        <li><code>POST /api/v2/pipelines</code></li>
        <li><code>PATCH /api/v2/pipelines/:id</code></li>
        <li><code>DELETE /api/v2/pipelines/:id</code></li>
        <li><code>GET /api/v2/stages</code></li>
        <li><code>GET /api/v2/stages/:id</code></li>
        <li><code>POST /api/v2/stages</code></li>
        <li><code>PATCH /api/v2/stages/:id</code></li>
        <li><code>DELETE /api/v2/stages/:id</code></li>
      </ul>
      <p>If you’re still using API v1 for these actions, we strongly recommend switching to API v2 to take advantage of its improved efficiency and reduced token consumption.</p>
  
      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
        <li><a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting">Developer documentation</a></li>
        <li><a href="https://pipedrive.readme.io/docs/guide-for-optimizing-api-usage">API usage optimization</a></li>
        <li><a href="https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide">API v2 Migration Guide</a></li>
      </ul>      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>
       
  </div>
</div>
`}</HTMLBlock>


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">March 13th, 2025</span>
    </div>
    <div class="change-area">
      <p>We are excited to announce that a set of API v2 endpoints has officially moved out of BETA status and is now stable. These endpoints provide a more efficient and performant way to interact with Pipedrive, replacing specific APIv1 endpoints.</p>
      
      <h2>Why This Matters?</h2>
      <ul>
        <li><b>Better Performance</b>: API v2 endpoints are optimized for speed and reliability.</li>
        <li><b>Lower Token Costs</b>: These endpoints consume fewer API tokens per request, making them a more cost-effective option.</li>
        <li><b>Improved Stability</b>: As stable endpoints, they are fully supported and ready for production use.</li>
      </ul>
      
      <h2>Optimize API Usage with Token-Based Rate Limiting</h2>
      <p>Since the introduction of <a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting#token-based-rate-limiting" target="_blank">Token-Based Rate Limiting</a> last year, we encourage all developers to migrate to available stable API v2 endpoints. Doing so will help you stay within your API token budget while maintaining seamless integration or even allow you to make more requests within the same budget.</p>

      <h2>What's Changing?</h2>
      <p>The following API v2 endpoints are now stable:</p>
      <ul>
        <li><code>GET /api/v2/activities</code></li>
        <li><code>GET /api/v2/activities/:id</code></li>
        <li><code>POST /api/v2/activities</code></li>
        <li><code>PATCH /api/v2/activities/:id</code></li>
        <li><code>DELETE /api/v2/activities/:id</code></li>
        <li><code>GET /api/v2/deals</code></li>
        <li><code>GET /api/v2/deals/:id</code></li>
        <li><code>POST /api/v2/deals</code></li>
        <li><code>PATCH /api/v2/deals/:id</code></li>
        <li><code>DELETE /api/v2/deals/:id</code></li>
        <li><code>GET /api/v2/persons</code></li>
        <li><code>GET /api/v2/persons/:id</code></li>
        <li><code>POST /api/v2/persons</code></li>
        <li><code>PATCH /api/v2/persons/:id</code></li>
        <li><code>DELETE /api/v2/persons/:id</code></li>
        <li><code>GET /api/v2/organizations</code></li>
        <li><code>GET /api/v2/organizations/:id</code></li>
        <li><code>POST /api/v2/organizations</code></li>
        <li><code>PATCH /api/v2/organizations/:id</code></li>
        <li><code>DELETE /api/v2/organizations/:id</code></li>
        <li><code>GET /api/v2/products</code></li>
        <li><code>GET /api/v2/products/:id</code></li>
        <li><code>POST /api/v2/products</code></li>
        <li><code>PATCH /api/v2/products/:id</code></li>
        <li><code>DELETE /api/v2/products/:id</code></li>
        <li><code>GET /api/v2/products/:id/variations</code></li>
        <li><code>GET /api/v2/products/variations</code></li>
        <li><code>POST /api/v2/products/:id/variations</code></li>
        <li><code>PATCH /api/v2/products/:id/variations/:id</code></li>
        <li><code>DELETE /api/v2/products/:id/variations/:id</code></li>
        <li><code>GET /api/v2/deals/:id/products</code></li>
        <li><code>GET /api/v2/deals/products</code></li>
        <li><code>POST /api/v2/persons/:id/products</code></li>
        <li><code>PATCH /api/v2/persons/:id/products</code></li>
        <li><code>DELETE /api/v2/persons/:id/products/:id</code></li>
        <li><code>GET /api/v2/itemSearch</code></li>
        <li><code>GET /api/v2/itemSearch/field</code></li>
        <li><code>GET /api/v2/deals/search</code></li>
        <li><code>GET /api/v2/leads/search</code></li>
        <li><code>GET /api/v2/persons/search</code></li>
        <li><code>GET /api/v2/organizations/search</code></li>
        <li><code>GET /api/v2/products/search</code></li>
        <li><code>GET /api/v2/pipelines</code></li>
        <li><code>GET /api/v2/pipelines/:id</code></li>
        <li><code>POST /api/v2/pipelines</code></li>
        <li><code>PATCH /api/v2/pipelines/:id</code></li>
        <li><code>DELETE /api/v2/pipelines/:id</code></li>
        <li><code>GET /api/v2/stages</code></li>
        <li><code>GET /api/v2/stages/:id</code></li>
        <li><code>POST /api/v2/stages</code></li>
        <li><code>PATCH /api/v2/stages/:id</code></li>
        <li><code>DELETE /api/v2/stages/:id</code></li>
      </ul>
      <p>If you’re still using API v1 for these actions, we strongly recommend switching to API v2 to take advantage of its improved efficiency and reduced token consumption.</p>
  
      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
        <li><a href="https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting">Developer documentation</a></li>
        <li><a href="https://pipedrive.readme.io/docs/guide-for-optimizing-api-usage">API usage optimization</a></li>
        <li><a href="https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide">API v2 Migration Guide</a></li>
      </ul>      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>
       
  </div>
</div>


API v2 endpoints now stable: improved performance & lower token costs

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">March 12th, 2025</span>
    </div>
    <div class="change-area">
      <p>Introducing new Installment API</p>
      
      <h2>What is changing?</h2>
      <p>We have added a brand new Installments resource to our API which represents the Installments in the new Revenue Management feature.</p>

			<p>Installments represent the information about payments throughout the duration of the project or services delivered.</p>
      
      <h2>Summary of the new endpoints:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getInstallments" target="_blank"><code>GET /api/v2/deals/{id}/installments</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#postInstallment" target="_blank"><code>POST /api/v2/deals/{id}/installments</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateInstallment" target="_blank"><code>PATCH /api/v2/deals/{id}/installments/{installment_id}</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#deleteInstallment" target="_blank"><code>DELETE /api/v2/deals/{id}/installments/{installment_id}</code></a></li>
      </ul>
  
      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>     
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>
       
  </div>
</div>
`}</HTMLBlock>

{"product": ["API"], "features": ["Installments”], "email_description": "We are introducing new Installments API" }


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">March 12th, 2025</span>
    </div>
    <div class="change-area">
      <p>Introducing new Installment API</p>
      
      <h2>What is changing?</h2>
      <p>We have added a brand new Installments resource to our API which represents the Installments in the new Revenue Management feature.</p>

			<p>Installments represent the information about payments throughout the duration of the project or services delivered.</p>
      
      <h2>Summary of the new endpoints:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getInstallments" target="_blank"><code>GET /api/v2/deals/{id}/installments</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#postInstallment" target="_blank"><code>POST /api/v2/deals/{id}/installments</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateInstallment" target="_blank"><code>PATCH /api/v2/deals/{id}/installments/{installment_id}</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#deleteInstallment" target="_blank"><code>DELETE /api/v2/deals/{id}/installments/{installment_id}</code></a></li>
      </ul>
  
      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>     
      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>
       
  </div>
</div>


Introducing new Installment API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">February 20th, 2025</span>
    </div>
    <div class="change-area">
      <p>Updating validation for Stages, Pipeline and Deals POST/PUT endpoints</p>
      
      <h2>What is changing?</h2>
      <p>It was possible to add stage/deal with unrealistic probability, add stages to non-existing pipeline, have empty names for stages and pipelines.</p>
      
      <h2>Affected endpoints:</h2>
      <ul>
        <li><code><b>POST /v1/stages</b></code>: Added validation for <code>deal_probability</code> to be within the range of 0 to 100 and <code>pipeline_id</code> to match an existing Pipeline.</li>
        <li><code><b>PUT /v1/stages/{id}</b></code>: Added validation for <code>deal_probability</code> to be within the range of 0 to 100, name value not to be null or empty, and <code>pipeline_id</code> to match an existing Pipeline.</li>
        <li><code><b>PUT /v1/pipelines/{id}/</b></code>: Implemented validation for <code>name</code> not to be null or empty.</li>
        <li><code><b>POST /v1/deals</b></code>: Enhanced validation for <code>probability</code> to be within the range of 0 to 100.</li>
      </ul>
		
      <h2>Why it is changing?</h2>
			<p>To improve API's reliability. This ensures only valid data is accepted, enhancing overall quality and usability.</p>
  
      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</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 20th, 2025</span>
    </div>
    <div class="change-area">
      <p>Updating validation for Stages, Pipeline and Deals POST/PUT endpoints</p>
      
      <h2>What is changing?</h2>
      <p>It was possible to add stage/deal with unrealistic probability, add stages to non-existing pipeline, have empty names for stages and pipelines.</p>
      
      <h2>Affected endpoints:</h2>
      <ul>
        <li><code><b>POST /v1/stages</b></code>: Added validation for <code>deal_probability</code> to be within the range of 0 to 100 and <code>pipeline_id</code> to match an existing Pipeline.</li>
        <li><code><b>PUT /v1/stages/{id}</b></code>: Added validation for <code>deal_probability</code> to be within the range of 0 to 100, name value not to be null or empty, and <code>pipeline_id</code> to match an existing Pipeline.</li>
        <li><code><b>PUT /v1/pipelines/{id}/</b></code>: Implemented validation for <code>name</code> not to be null or empty.</li>
        <li><code><b>POST /v1/deals</b></code>: Enhanced validation for <code>probability</code> to be within the range of 0 to 100.</li>
      </ul>
		
      <h2>Why it is changing?</h2>
			<p>To improve API's reliability. This ensures only valid data is accepted, enhancing overall quality and usability.</p>
  
      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1">API Reference</a></li>
      </ul>      
      <p>If you have any questions or comments, feel free to let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>
       
  </div>
</div>


Updating validation for Stages, Pipeline and Deals POST/PUT endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 19, 2024</span>
    </div>
    <div class="change-area">
        <p>We are happy to announce new v2 endpoints for Activities API to offer a fast and performant way for interacting with the Pipedrive API. See our <a href="https://developers.pipedrive.com/docs/api/v1/Activities">API Reference</a> for more information.</p>
        <h3><b>What is the benefit of the new endpoints?</b></h3>
        <p>We are introducing API v2 to eventually replace v1 endpoints. API v2 is more performant and offers better developer experience. See more information here:</p>
        <ul>
            <li><a href="https://pipedrive.readme.io/docs/pipedrive-api-v2" target="blank">Pipedrive API v2 overview</a></li>
            <li><a href="https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide#activities-api" target="blank">Pipedrive API v2 migration guide</a></li>
        </ul>
        <h3><b>Timeline of the launch</b></h3>
        <p>We’re releasing the public BETA on December 19th, and the API will be available for usage and testing on all accounts. We’ll notify you here in the changelog once the full version of the API is released, so remember to subscribe. Keep in mind that between the BETA and the full release of the API, the endpoints are subject to changes.</p>
        <p>We are eager to hear your feedback, questions or comments in the <a href="https://devcommunity.pipedrive.com/">Developers’ Community.</a></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 19, 2024</span>
    </div>
    <div class="change-area">
        <p>We are happy to announce new v2 endpoints for Activities API to offer a fast and performant way for interacting with the Pipedrive API. See our <a href="https://developers.pipedrive.com/docs/api/v1/Activities">API Reference</a> for more information.</p>
        <h3><b>What is the benefit of the new endpoints?</b></h3>
        <p>We are introducing API v2 to eventually replace v1 endpoints. API v2 is more performant and offers better developer experience. See more information here:</p>
        <ul>
            <li><a href="https://pipedrive.readme.io/docs/pipedrive-api-v2" target="blank">Pipedrive API v2 overview</a></li>
            <li><a href="https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide#activities-api" target="blank">Pipedrive API v2 migration guide</a></li>
        </ul>
        <h3><b>Timeline of the launch</b></h3>
        <p>We’re releasing the public BETA on December 19th, and the API will be available for usage and testing on all accounts. We’ll notify you here in the changelog once the full version of the API is released, so remember to subscribe. Keep in mind that between the BETA and the full release of the API, the endpoints are subject to changes.</p>
        <p>We are eager to hear your feedback, questions or comments in the <a href="https://devcommunity.pipedrive.com/">Developers’ Community.</a></p>
    </div>
</div>


Introducing new Activities API v2 endpoints in public BETA

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">March 17th, 2025</span>
    </div>
    <div class="change-area">      
      <h2>What is changing?</h2>
      <p>From <b>March 17, 2025</b>, all new webhooks created via API will be <b>version 2.0</b> by default. Legacy v1 webhooks can still be created by specifying the <code>version</code> parameter in the API request body until further notice.</p>
      
      <h2>Why it is changing?</h2>
			<p>We introduced webhooks v2 at the beginning of 2023 to bring <b>added reliability and stability</b> by <b>reducing duplicate and missing webhook triggers</b> and <b>delays</b>. In addition, <code>lead</code> webhooks are supported in v2. Webhooks v2 have proven their maturity and it is time to start sunsetting v1.</p>
      
      <h2>Things to know about webhooks v2</h2>
      <ol>
        <li>Webhooks v2 and v1 will continue to run in parallel for the time being but <b>v1 will be deprecated completely by the end of 2025</b>. You will be notified of any changes via our <a href="https://developers.pipedrive.com/changelog">Changelog</a>, so make sure you subscribe to it.</li>
        <li>Please review the <a href="https://pipedrive.readme.io/docs/webhooks-v2-migration-guide">v1 to v2 migration guide</a> closely as there are significant differences in webhooks v2’s payload.</li>
        <li>Should a field no longer be available in the payload of a v2 webhook, please query it from our API.</li>
      </ol>

      <br />
      <p>Learn about webhooks v2 <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2">here</a> and how to migrate your webhooks from v1 to v2 <a href="https://pipedrive.readme.io/docs/webhooks-v2-migration-guide">here</a>. If you have any feedback or run into any issues, please do let us know in our <a href="https://devcommunity.pipedrive.com/">Developers’ Community</a>!</p>
       
  </div>
</div>
`}</HTMLBlock>


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">March 17th, 2025</span>
    </div>
    <div class="change-area">      
      <h2>What is changing?</h2>
      <p>From <b>March 17, 2025</b>, all new webhooks created via API will be <b>version 2.0</b> by default. Legacy v1 webhooks can still be created by specifying the <code>version</code> parameter in the API request body until further notice.</p>
      
      <h2>Why it is changing?</h2>
			<p>We introduced webhooks v2 at the beginning of 2023 to bring <b>added reliability and stability</b> by <b>reducing duplicate and missing webhook triggers</b> and <b>delays</b>. In addition, <code>lead</code> webhooks are supported in v2. Webhooks v2 have proven their maturity and it is time to start sunsetting v1.</p>
      
      <h2>Things to know about webhooks v2</h2>
      <ol>
        <li>Webhooks v2 and v1 will continue to run in parallel for the time being but <b>v1 will be deprecated completely by the end of 2025</b>. You will be notified of any changes via our <a href="https://developers.pipedrive.com/changelog">Changelog</a>, so make sure you subscribe to it.</li>
        <li>Please review the <a href="https://pipedrive.readme.io/docs/webhooks-v2-migration-guide">v1 to v2 migration guide</a> closely as there are significant differences in webhooks v2’s payload.</li>
        <li>Should a field no longer be available in the payload of a v2 webhook, please query it from our API.</li>
      </ol>

      <br />
      <p>Learn about webhooks v2 <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2">here</a> and how to migrate your webhooks from v1 to v2 <a href="https://pipedrive.readme.io/docs/webhooks-v2-migration-guide">here</a>. If you have any feedback or run into any issues, please do let us know in our <a href="https://devcommunity.pipedrive.com/">Developers’ Community</a>!</p>
       
  </div>
</div>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog