<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Oct 1st, 2025</span>
    </div>
    <div class="change-area">
      <p>Added a new query parameter to the API v2 that allows sorting products within deals. Users can now sort products by their order number when fetching them.</p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The new option was added to the following endpoint:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts">GET /api/v2/deals/{id}/products</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>

We are introducing order_nr as new sorting query parameter for Products API v2


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Oct 1st, 2025</span>
    </div>
    <div class="change-area">
      <p>Added a new query parameter to the API v2 that allows sorting products within deals. Users can now sort products by their order number when fetching them.</p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The new option was added to the following endpoint:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts">GET /api/v2/deals/{id}/products</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 sorting parameter for Products API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 25th, 2025</span>
    </div>
    <div class="change-area">
      <p>We have added a brand new Product Images resource to our API.</p>
			<p>Product Images represent the image associated with the Product. Each product can have one image to represent it better visually. </p>
      
      <h2>Summary of the new endpoints</h2>
      <p>The Installments resource includes the following endpoints:</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductImage" target="_blank"><code>GET /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#uploadProductImage" target="_blank"><code>POST /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProductImage" target="_blank"><code>PUT /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#deleteProductImage" target="_blank"><code>DELETE/api/v2/products/{id}/images</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": ["Product Images”], "email_description": "We are introducing new Product Images API" }


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">August 25th, 2025</span>
    </div>
    <div class="change-area">
      <p>We have added a brand new Product Images resource to our API.</p>
			<p>Product Images represent the image associated with the Product. Each product can have one image to represent it better visually. </p>
      
      <h2>Summary of the new endpoints</h2>
      <p>The Installments resource includes the following endpoints:</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductImage" target="_blank"><code>GET /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#uploadProductImage" target="_blank"><code>POST /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#updateProductImage" target="_blank"><code>PUT /api/v2/products/{id}/images</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#deleteProductImage" target="_blank"><code>DELETE/api/v2/products/{id}/images</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 Product Images API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 21st, 2025</span>
    </div>
    <div class="change-area">
      <h2>What is changing?</h2>
			<p>From <b>Sep 21, 2025</b> we are changing the size limit of the activity note field for <code>POST  v1/activities</code> request to be <b>100kb</b>.</p>

      <h2>Why is it changing?</h2>
			<p>We’re adding a 100 KB cap to activity notes to keep the database lean, prevent oversized payloads, and make Activities consistent with the limits already used for other entities.</p>

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

We are changing the  activities notes size limit POST v1/activities endpoint


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 21st, 2025</span>
    </div>
    <div class="change-area">
      <h2>What is changing?</h2>
			<p>From <b>Sep 21, 2025</b> we are changing the size limit of the activity note field for <code>POST  v1/activities</code> request to be <b>100kb</b>.</p>

      <h2>Why is it changing?</h2>
			<p>We’re adding a 100 KB cap to activity notes to keep the database lean, prevent oversized payloads, and make Activities consistent with the limits already used for other entities.</p>

      <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: updating activities note field limit sizing for POST v1/activities

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">June 30th, 2025</span>
    </div>
    <div class="change-area">
      <p>We’ve identified an issue where the v2 user webhooks are deviating from the documented specification. According to our <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2" target="_blank">Webhooks v2 documentation</a>, the <code>timestamp</code> field in the event meta object should be an RFC 3339 formatted timestamp (e.g., "2025-01-01T00:00:00.000Z"). However, the current implementation returns timestamps as UNIX timestamps (seconds since 1970) instead.</p>
      
     <p>On June 30th this behaviour will be rectified to reflect our documentation and user webhooks meta timestamp will be switched to RFC 3339 format.</p>
      
      <h2>What does it mean for me?</h2>

			<p>If you are consuming v2 user webhooks and rely on the <code>timestamp</code> field in the event meta object, make sure your application can process the updated RFC 3339 format. This change only affects v2 <b>user</b> webhooks — all other v2 webhooks (including activity, deal, lead, note, organization, person, pipeline, product, and stage) are already using the correct timestamp format and are not impacted by this fix.</p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2">Guide for Webhooks v2</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">June 30th, 2025</span>
    </div>
    <div class="change-area">
      <p>We’ve identified an issue where the v2 user webhooks are deviating from the documented specification. According to our <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2" target="_blank">Webhooks v2 documentation</a>, the <code>timestamp</code> field in the event meta object should be an RFC 3339 formatted timestamp (e.g., "2025-01-01T00:00:00.000Z"). However, the current implementation returns timestamps as UNIX timestamps (seconds since 1970) instead.</p>
      
     <p>On June 30th this behaviour will be rectified to reflect our documentation and user webhooks meta timestamp will be switched to RFC 3339 format.</p>
      
      <h2>What does it mean for me?</h2>

			<p>If you are consuming v2 user webhooks and rely on the <code>timestamp</code> field in the event meta object, make sure your application can process the updated RFC 3339 format. This change only affects v2 <b>user</b> webhooks — all other v2 webhooks (including activity, deal, lead, note, organization, person, pipeline, product, and stage) are already using the correct timestamp format and are not impacted by this fix.</p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2">Guide for Webhooks v2</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>


Bug fix in v2 user webhooks payload

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Apr 22nd, 2025</span>
    </div>
    <div class="change-area">
      <p>We’ve identified an issue where the following endpoints were returning data for entities that had already been deleted:</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersons" target="_blank"><code>GET /api/v2/persons</code></a></li>
				<li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizations" target="_blank"><code>GET /api/v2/organizations</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Activities#getActivities" target="_blank"><code>GET /api/v2/activities</code></a></li>
      </ul>  
      
     <p>These endpoints now correctly return only active (non-deleted) entities in their responses.</p>
      
      <h2>What does it mean for me?</h2>

			<p>If you were filtering or processing data returned by these endpoints, you may now notice a smaller or more accurate result set, as deleted entities are no longer included.</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>

We’ve identified an issue where the following endpoints were returning data for entities that had already been deleted


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Apr 22nd, 2025</span>
    </div>
    <div class="change-area">
      <p>We’ve identified an issue where the following endpoints were returning data for entities that had already been deleted:</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersons" target="_blank"><code>GET /api/v2/persons</code></a></li>
				<li><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizations" target="_blank"><code>GET /api/v2/organizations</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Activities#getActivities" target="_blank"><code>GET /api/v2/activities</code></a></li>
      </ul>  
      
     <p>These endpoints now correctly return only active (non-deleted) entities in their responses.</p>
      
      <h2>What does it mean for me?</h2>

			<p>If you were filtering or processing data returned by these endpoints, you may now notice a smaller or more accurate result set, as deleted entities are no longer included.</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>


Bug fix in data returned by three endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Apr 22nd, 2025</span>
    </div>
    <div class="change-area">
      <p>We are introducing the possibility of initiating a conversion between Deals and Leads.</p>
      
      <h2>What is being added?</h2>
      <p>Four new endpoints to enable conversion between Deals and Leads have been released. Those endpoints allow the initialization of a conversion and getting the status of an ongoing conversion.</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#convertDealToLead" target="_blank"><code>POST /api/v2/deals/{id}/convert/lead</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#convertLeadToDeal" target="_blank"><code>POST /api/v2/leads/{id}/convert/deal</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealConversionStatus" target="_blank"><code>GET /api/v2/deals/{id}/convert/status/{conversion_id}</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeadConversionStatus" target="_blank"><code>GET /api/v2/leads/{id}/convert/status/{conversion_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>

New endpoints to convert Deals to Leads and Leads to Deals


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Apr 22nd, 2025</span>
    </div>
    <div class="change-area">
      <p>We are introducing the possibility of initiating a conversion between Deals and Leads.</p>
      
      <h2>What is being added?</h2>
      <p>Four new endpoints to enable conversion between Deals and Leads have been released. Those endpoints allow the initialization of a conversion and getting the status of an ongoing conversion.</p>
      
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#convertDealToLead" target="_blank"><code>POST /api/v2/deals/{id}/convert/lead</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#convertLeadToDeal" target="_blank"><code>POST /api/v2/leads/{id}/convert/deal</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealConversionStatus" target="_blank"><code>GET /api/v2/deals/{id}/convert/status/{conversion_id}</code></a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Leads#getLeadConversionStatus" target="_blank"><code>GET /api/v2/leads/{id}/convert/status/{conversion_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>{`
<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>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog