<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 in 2026</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 in 2026</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>


Breaking change: Webhooks v2 will become the new default version

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 2nd, 2024</span>
    </div>
    <div class="change-area">
      <p>We are introducing token-based rate limits for API requests.</p>
      
      <h2>What is changing?</h2>
      <p><b>Token-Based Rate Limits</b>: API requests will now consume tokens from the company's daily budget, which resets every 24 hours. If the token budget is exceeded, further requests will return a 429 (Too Many Requests) response until the budget resets the next day.</p>
      <p><b>APIv2</b>: We encourage migrating to APIv2, which is more efficient and comes with a lower token cost per request. This can help reduce your token consumption and improve performance.</p>
			
      
      <h2>Why it is changing?</h2>
			<p>We are introducing these new limits in an effort to ensure the optimal performance and stability of our system. We project that these limits will not impact the overwhelming majority of our customers, as they serve to prevent extreme cases, thus keeping our systems stable. </p>
      
      <h2>Timeline of changes</h2>
      <ul>
        <li><b>December 2nd, 2024</b>: Token-based rate limits will apply to all new signups.</li>
        <li><b>March 1st, 2025</b>: The token-based rate limits will begin rolling out for existing customers.</li>
        <li><b>May 31st, 2025</b>: The rollout will be complete, and all existing customers will be subject to the new limits.</li>
      </ul>
  
      <h2>Additional resources:</h2>
      <ul>
        <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">APIv2 Migration Guide</a></li>
      </ul>

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

Breaking changes: Token-Based Rate Limits for API Usage


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 2nd, 2024</span>
    </div>
    <div class="change-area">
      <p>We are introducing token-based rate limits for API requests.</p>
      
      <h2>What is changing?</h2>
      <p><b>Token-Based Rate Limits</b>: API requests will now consume tokens from the company's daily budget, which resets every 24 hours. If the token budget is exceeded, further requests will return a 429 (Too Many Requests) response until the budget resets the next day.</p>
      <p><b>APIv2</b>: We encourage migrating to APIv2, which is more efficient and comes with a lower token cost per request. This can help reduce your token consumption and improve performance.</p>
			
      
      <h2>Why it is changing?</h2>
			<p>We are introducing these new limits in an effort to ensure the optimal performance and stability of our system. We project that these limits will not impact the overwhelming majority of our customers, as they serve to prevent extreme cases, thus keeping our systems stable. </p>
      
      <h2>Timeline of changes</h2>
      <ul>
        <li><b>December 2nd, 2024</b>: Token-based rate limits will apply to all new signups.</li>
        <li><b>March 1st, 2025</b>: The token-based rate limits will begin rolling out for existing customers.</li>
        <li><b>May 31st, 2025</b>: The rollout will be complete, and all existing customers will be subject to the new limits.</li>
      </ul>
  
      <h2>Additional resources:</h2>
      <ul>
        <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">APIv2 Migration Guide</a></li>
      </ul>

      <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 changes: Token-Based Rate Limits for API requests

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 2, 2024</span>
    </div>
    <div class="change-area">
        <p>We are happy to announce new production-ready v2 endpoints for Products, Pipelines and Stages API to offer a fast and performant way for interacting with the Pipedrive API:
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Products" target="blank">Products API</a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines" target="blank">Pipelines API</a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Stages" target="blank">Stages API</a></li>
        </ul>
        </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" target="blank">Pipedrive API v2 migration guide</a></li>
        </ul>

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 2, 2024</span>
    </div>
    <div class="change-area">
        <p>We are happy to announce new production-ready v2 endpoints for Products, Pipelines and Stages API to offer a fast and performant way for interacting with the Pipedrive API:
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Products" target="blank">Products API</a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines" target="blank">Pipelines API</a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Stages" target="blank">Stages API</a></li>
        </ul>
        </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" target="blank">Pipedrive API v2 migration guide</a></li>
        </ul>

    </div>
</div>


Introducing new v2 endpoints for Products, Pipelines and Stages API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 18th, 2024</span>
    </div>
    <div class="change-area">
      <p>Update on new entity count limits for a set of features</p>
  
      <h2>What is changing?</h2>
      <p>The format of the text in the <code>error</code> response field is being updated for entity count limits that were announced previously <a href="https://developers.pipedrive.com/changelog/post/breaking-change-new-entity-count-limits-for-a-set-of-features">in this changelog update</a>.</p>      
      
      <p>Affected endpoints:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ActivityTypes#addActivityType">POST /v1/activityTypes</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField">POST /v1/dealFields</a></li>
					<li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealField">PUT /v1/dealFields/{id}</a></li>
         	<li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField">POST /v1/organizationFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationField">PUT /v1/organizationFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField">POST /v1/personFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonField">PUT /v1/personFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField">POST /v1/productFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#updateProductField">PUT /v1/productFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct">POST /v1/deals/{id}/products</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Filters#addFilter">POST /v1/filters</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#addTask">POST /v1/tasks</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#updateTask">PUT /v1/tasks/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationRelationships#addOrganizationRelationship">POST /v1/organizationRelationships</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationRelationships#updateOrganizationRelationship">PUT /v1/organizationRelationships/{id}</a></li>
      </ul>
            
			<p>
        Here's an example of the <code>403</code> error response for <code>POST</code>request:<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">"Couldn't add activity type. You've reached the activity type per company limit."</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</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>
        Here's an example of the <code>403</code> error response for <code>PUT</code>request:<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">"Couldn't add activity type. You've reached the activity type per company limit."</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</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 />
           
      <h2>Why it is changing?</h2>
<p>This update aims to improve clarity and provide a better user experience by enhancing the wording in error messages.</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>

Update on new entity count limits for a set of features


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">November 18th, 2024</span>
    </div>
    <div class="change-area">
      <p>Update on new entity count limits for a set of features</p>
  
      <h2>What is changing?</h2>
      <p>The format of the text in the <code>error</code> response field is being updated for entity count limits that were announced previously <a href="https://developers.pipedrive.com/changelog/post/breaking-change-new-entity-count-limits-for-a-set-of-features">in this changelog update</a>.</p>      
      
      <p>Affected endpoints:
        <ul>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ActivityTypes#addActivityType">POST /v1/activityTypes</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField">POST /v1/dealFields</a></li>
					<li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealField">PUT /v1/dealFields/{id}</a></li>
         	<li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField">POST /v1/organizationFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationField">PUT /v1/organizationFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField">POST /v1/personFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonField">PUT /v1/personFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField">POST /v1/productFields</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#updateProductField">PUT /v1/productFields/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct">POST /v1/deals/{id}/products</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Filters#addFilter">POST /v1/filters</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#addTask">POST /v1/tasks</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#updateTask">PUT /v1/tasks/{id}</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationRelationships#addOrganizationRelationship">POST /v1/organizationRelationships</a></li>
          <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationRelationships#updateOrganizationRelationship">PUT /v1/organizationRelationships/{id}</a></li>
      </ul>
            
			<p>
        Here's an example of the <code>403</code> error response for <code>POST</code>request:<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">"Couldn't add activity type. You've reached the activity type per company limit."</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</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>
        Here's an example of the <code>403</code> error response for <code>PUT</code>request:<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">"Couldn't add activity type. You've reached the activity type per company limit."</span>,
  <span class="cm-property">"error_info"</span>: <span class="cm-string">"Please check developers.pipedrive.com for more information about Pipedrive API"</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 />
           
      <h2>Why it is changing?</h2>
<p>This update aims to improve clarity and provide a better user experience by enhancing the wording in error messages.</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>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 2nd, 2024</span>
    </div>
    <div class="change-area">
      <p>New custom fields selector in Products endpoint</p>
   
      
			
      <h2>What is changing?</h2>
      <p>We’ve added a new query parameter - <code>custom_fields</code> - to the <a href="https://developers.pipedrive.com/docs/api/v1/Products#getProducts" target="_blank">GET /api/v2/products</a> endpoint that can be used if you are only interested in a particular set of custom fields.
The query parameter is a comma separated string of custom field keys. When included the endpoint response will only include the custom fields defined in the query parameter.
</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>

{"product": ["API"], "features": ["Products”], "email_description": "Added new selector to Products endpoint" }

New custom fields selector in Products endpoint


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 2nd, 2024</span>
    </div>
    <div class="change-area">
      <p>New custom fields selector in Products endpoint</p>
   
      
			
      <h2>What is changing?</h2>
      <p>We’ve added a new query parameter - <code>custom_fields</code> - to the <a href="https://developers.pipedrive.com/docs/api/v1/Products#getProducts" target="_blank">GET /api/v2/products</a> endpoint that can be used if you are only interested in a particular set of custom fields.
The query parameter is a comma separated string of custom field keys. When included the endpoint response will only include the custom fields defined in the query parameter.
</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>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog