<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br />
        <span class="from-date">Mar 25th, 2026</span>
    </div>
    <div class="change-area">
        <h2>What is changing?</h2>
        <p>1. We're adding a new Assignees field (<code>assignee_ids</code>), with the type <code>array</code> for the following Project Tasks API endpoints (<i>The Assignees field can store up to 10 values per task.</i>):</p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Projects#getProjectTasks" target="_blank">GET /v1/projects/{id}/tasks</a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#getTasks" target="_blank">GET /v1/tasks</a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#getTask" target="_blank">GET /v1/tasks/{id}</a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#addTask" target="_blank">POST /v1/tasks</a></li>      
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#updateTask" target="_blank">PUT /v1/tasks/{id}</a></li>            
        </ul>
      
      <p>2. The old Assignee field and the new Assignees field are updated synchronously based on these rules:</p>
			<ul>
            <li>When the Assignees field is updated, the Assignee field value will be set to the first value of the Assignees field</li>
            <li>When the Assignee field is updated, the Assignees field value will be overwritten by the Assignee field value</li>            
      </ul>
      
      <h2>Why it is changing?</h2>
			<p>We’re changing the behavior of the existing Label field to prevent data inconsistency between the old and new fields.</p>

        <h2>Additional resources:</h2>
        <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>

<br />

{"product": ["API"], "features": ["Product assignees”], "email_description": "We're adding a new "assignees" field to the Projects" }


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br />
        <span class="from-date">Mar 25th, 2026</span>
    </div>
    <div class="change-area">
        <h2>What is changing?</h2>
        <p>1. We're adding a new Assignees field (<code>assignee_ids</code>), with the type <code>array</code> for the following Project Tasks API endpoints (<i>The Assignees field can store up to 10 values per task.</i>):</p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Projects#getProjectTasks" target="_blank">GET /v1/projects/{id}/tasks</a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#getTasks" target="_blank">GET /v1/tasks</a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#getTask" target="_blank">GET /v1/tasks/{id}</a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#addTask" target="_blank">POST /v1/tasks</a></li>      
            <li><a href="https://developers.pipedrive.com/docs/api/v1/Tasks#updateTask" target="_blank">PUT /v1/tasks/{id}</a></li>            
        </ul>
      
      <p>2. The old Assignee field and the new Assignees field are updated synchronously based on these rules:</p>
			<ul>
            <li>When the Assignees field is updated, the Assignee field value will be set to the first value of the Assignees field</li>
            <li>When the Assignee field is updated, the Assignees field value will be overwritten by the Assignee field value</li>            
      </ul>
      
      <h2>Why it is changing?</h2>
			<p>We’re changing the behavior of the existing Label field to prevent data inconsistency between the old and new fields.</p>

        <h2>Additional resources:</h2>
        <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 a new Assignees field in Projects API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area"> <span class="from-label">Effective from:</span>


      <span class="from-date">April 1st, 2026</span>
    </div>
    <div class="change-area">
      <p>We’ve identified an inconsistency in our v2 product webhooks where date fields are deviating from our documented specifications. Currently, v2 product webhooks use <code>YYYY-MM-DD HH:mm:ss</code> format. To ensure consistency across our ecosystem, we are updating these to the RFC 3339 format (e.g., <code>2026-01-01T12:00:00Z</code>).</p>

      <p>On April 1st, 2026, this behavior will be updated. All date-related fields within v2 product webhooks will transition to the RFC 3339 standard with UTC timezones.</p>

      <h2>What does it mean for me?</h2>

      <p>If you consume v2 product webhooks, you must ensure your integration can handle RFC 3339 formatted strings. The
        following fields (and any other product-specific date fields) are included in this update:</p>
      <ul>
        <li><code>timestamp</code> in the event meta object</li>
        <li><code>add_time</code></li>
        <li><code>update_time</code></li>
      </ul>

      <p>We recommend updating your date parsing logic to be RFC 3339 compliant before the effective date to
        avoid any disruptions in data processing.</p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a
            href="[https://pipedrive.readme.io/docs/guide-for-webhooks-v2](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/](https://devcommunity.pipedrive.com/)">the Developer’s
          Community</a>.</p>
    </div>
  </div> 
`}</HTMLBlock>

<br />

We are updating date fields in v2 product webhooks to RFC 3339 format


<div class="chlog-box">
    <div class="from-area"> <span class="from-label">Effective from:</span>


      <span class="from-date">April 1st, 2026</span>
    </div>
    <div class="change-area">
      <p>We’ve identified an inconsistency in our v2 product webhooks where date fields are deviating from our documented specifications. Currently, v2 product webhooks use <code>YYYY-MM-DD HH:mm:ss</code> format. To ensure consistency across our ecosystem, we are updating these to the RFC 3339 format (e.g., <code>2026-01-01T12:00:00Z</code>).</p>

      <p>On April 1st, 2026, this behavior will be updated. All date-related fields within v2 product webhooks will transition to the RFC 3339 standard with UTC timezones.</p>

      <h2>What does it mean for me?</h2>

      <p>If you consume v2 product webhooks, you must ensure your integration can handle RFC 3339 formatted strings. The
        following fields (and any other product-specific date fields) are included in this update:</p>
      <ul>
        <li><code>timestamp</code> in the event meta object</li>
        <li><code>add_time</code></li>
        <li><code>update_time</code></li>
      </ul>

      <p>We recommend updating your date parsing logic to be RFC 3339 compliant before the effective date to
        avoid any disruptions in data processing.</p>

      <h2>Additional resources:</h2>
      <ul>
        <li><a
            href="[https://pipedrive.readme.io/docs/guide-for-webhooks-v2](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/](https://devcommunity.pipedrive.com/)">the Developer’s
          Community</a>.</p>
    </div>
  </div> 


Bug fix in v2 product webhooks payload

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br />
        <span class="from-date">Dec 10th, 2025</span>
    </div>
    <div class="change-area">
        <p>We have added a comprehensive Fields API v2 for managing custom fields across multiple entity types. This release includes full CRUD operations for deal, person, organization, and product fields, along with bulk options management for enum and set field types.</p>
        <h2>Summary of the new endpoints:</h2>
        <p>The Fields API v2 includes the following endpoints:</p>
        <p><strong>Activity Fields:</strong></p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ActivityFields#getActivityFields" target="_blank"><code>GET /api/v2/activityFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ActivityFields#getActivityField" target="_blank"><code>GET /api/v2/activityFields/{field_code}</code></a></li>
        </ul>
        <p><strong>Deal Fields:</strong></p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#getDealFields" target="_blank"><code>GET /api/v2/dealFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField" target="_blank"><code>POST /api/v2/dealFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#getDealField" target="_blank"><code>GET /api/v2/dealFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealField" target="_blank"><code>PATCH /api/v2/dealFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#deleteDealField" target="_blank"><code>DELETE /api/v2/dealFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealFieldOptions" target="_blank"><code>POST /api/v2/dealFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealFieldOptions" target="_blank"><code>PATCH /api/v2/dealFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#deleteDealFieldOptions" target="_blank"><code>DELETE /api/v2/dealFields/{field_code}/options</code></a></li>
        </ul>
        <p><strong>Person Fields:</strong></p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#getPersonFields" target="_blank"><code>GET /api/v2/personFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField" target="_blank"><code>POST /api/v2/personFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#getPersonField" target="_blank"><code>GET /api/v2/personFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonField" target="_blank"><code>PATCH /api/v2/personFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#deletePersonField" target="_blank"><code>DELETE /api/v2/personFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonFieldOptions" target="_blank"><code>POST /api/v2/personFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonFieldOptions" target="_blank"><code>PATCH /api/v2/personFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#deletePersonFieldOptions" target="_blank"><code>DELETE /api/v2/personFields/{field_code}/options</code></a></li>
        </ul>
        <p><strong>Organization Fields:</strong></p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#getOrganizationFields" target="_blank"><code>GET /api/v2/organizationFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField" target="_blank"><code>POST /api/v2/organizationFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#getOrganizationField" target="_blank"><code>GET /api/v2/organizationFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationField" target="_blank"><code>PATCH /api/v2/organizationFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#deleteOrganizationField" target="_blank"><code>DELETE /api/v2/organizationFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationFieldOptions" target="_blank"><code>POST /api/v2/organizationFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationFieldOptions" target="_blank"><code>PATCH /api/v2/organizationFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#deleteOrganizationFieldOptions" target="_blank"><code>DELETE /api/v2/organizationFields/{field_code}/options</code></a></li>
        </ul>
        <p><strong>Product Fields:</strong></p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#getProductFields" target="_blank"><code>GET /api/v2/productFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField" target="_blank"><code>POST /api/v2/productFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#getProductField" target="_blank"><code>GET /api/v2/productFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#updateProductField" target="_blank"><code>PATCH /api/v2/productFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#deleteProductField" target="_blank"><code>DELETE /api/v2/productFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductFieldOptions" target="_blank"><code>POST /api/v2/productFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#updateProductFieldOptions" target="_blank"><code>PATCH /api/v2/productFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#deleteProductFieldOptions" target="_blank"><code>DELETE /api/v2/productFields/{field_code}/options</code></a></li>
        </ul>
        <h2>Additional resources:</h2>
        <ul>
            <li><a href="https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide#fields-api">Fields 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>

<br />

We are introducing Fields v2 endpoints for managing custom fields across multiple entity types


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br />
        <span class="from-date">Dec 10th, 2025</span>
    </div>
    <div class="change-area">
        <p>We have added a comprehensive Fields API v2 for managing custom fields across multiple entity types. This release includes full CRUD operations for deal, person, organization, and product fields, along with bulk options management for enum and set field types.</p>
        <h2>Summary of the new endpoints:</h2>
        <p>The Fields API v2 includes the following endpoints:</p>
        <p><strong>Activity Fields:</strong></p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ActivityFields#getActivityFields" target="_blank"><code>GET /api/v2/activityFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ActivityFields#getActivityField" target="_blank"><code>GET /api/v2/activityFields/{field_code}</code></a></li>
        </ul>
        <p><strong>Deal Fields:</strong></p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#getDealFields" target="_blank"><code>GET /api/v2/dealFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealField" target="_blank"><code>POST /api/v2/dealFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#getDealField" target="_blank"><code>GET /api/v2/dealFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealField" target="_blank"><code>PATCH /api/v2/dealFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#deleteDealField" target="_blank"><code>DELETE /api/v2/dealFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#addDealFieldOptions" target="_blank"><code>POST /api/v2/dealFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#updateDealFieldOptions" target="_blank"><code>PATCH /api/v2/dealFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/DealFields#deleteDealFieldOptions" target="_blank"><code>DELETE /api/v2/dealFields/{field_code}/options</code></a></li>
        </ul>
        <p><strong>Person Fields:</strong></p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#getPersonFields" target="_blank"><code>GET /api/v2/personFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonField" target="_blank"><code>POST /api/v2/personFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#getPersonField" target="_blank"><code>GET /api/v2/personFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonField" target="_blank"><code>PATCH /api/v2/personFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#deletePersonField" target="_blank"><code>DELETE /api/v2/personFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#addPersonFieldOptions" target="_blank"><code>POST /api/v2/personFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#updatePersonFieldOptions" target="_blank"><code>PATCH /api/v2/personFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/PersonFields#deletePersonFieldOptions" target="_blank"><code>DELETE /api/v2/personFields/{field_code}/options</code></a></li>
        </ul>
        <p><strong>Organization Fields:</strong></p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#getOrganizationFields" target="_blank"><code>GET /api/v2/organizationFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationField" target="_blank"><code>POST /api/v2/organizationFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#getOrganizationField" target="_blank"><code>GET /api/v2/organizationFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationField" target="_blank"><code>PATCH /api/v2/organizationFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#deleteOrganizationField" target="_blank"><code>DELETE /api/v2/organizationFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#addOrganizationFieldOptions" target="_blank"><code>POST /api/v2/organizationFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#updateOrganizationFieldOptions" target="_blank"><code>PATCH /api/v2/organizationFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/OrganizationFields#deleteOrganizationFieldOptions" target="_blank"><code>DELETE /api/v2/organizationFields/{field_code}/options</code></a></li>
        </ul>
        <p><strong>Product Fields:</strong></p>
        <ul>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#getProductFields" target="_blank"><code>GET /api/v2/productFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductField" target="_blank"><code>POST /api/v2/productFields</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#getProductField" target="_blank"><code>GET /api/v2/productFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#updateProductField" target="_blank"><code>PATCH /api/v2/productFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#deleteProductField" target="_blank"><code>DELETE /api/v2/productFields/{field_code}</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#addProductFieldOptions" target="_blank"><code>POST /api/v2/productFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#updateProductFieldOptions" target="_blank"><code>PATCH /api/v2/productFields/{field_code}/options</code></a></li>
            <li><a href="https://developers.pipedrive.com/docs/api/v1/ProductFields#deleteProductFieldOptions" target="_blank"><code>DELETE /api/v2/productFields/{field_code}/options</code></a></li>
        </ul>
        <h2>Additional resources:</h2>
        <ul>
            <li><a href="https://pipedrive.readme.io/docs/pipedrive-api-v2-migration-guide#fields-api">Fields 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>


Introducing new Fields API v2

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Nov 24th, 2025</span>
    </div>
    <div class="change-area">
      <p>We have added a brand new Product Duplication resource to our API. This will allow a product to be duplicated, as well as its prices, variations and image.</p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The Products resource includes the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#duplicateProduct">POST /api/v2/products/{id}/duplicate</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>

<br />

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


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Nov 24th, 2025</span>
    </div>
    <div class="change-area">
      <p>We have added a brand new Product Duplication resource to our API. This will allow a product to be duplicated, as well as its prices, variations and image.</p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The Products resource includes the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Products#duplicateProduct">POST /api/v2/products/{id}/duplicate</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 Duplication API

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Nov 24th, 2025</span>
    </div>
    <div class="change-area">
      <p>Added a new query parameter to the <code>GET /api/v2/persons</code> API. If supplied, only persons linked to the specified deal are returned.</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/Persons#getPersons">GET /api/v2/persons</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>

<br />

{"product": ["API"], "features": ["Persons”], "email_description": "We are adding deal_id parameter to GET /api/v2/persons" }


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Nov 24th, 2025</span>
    </div>
    <div class="change-area">
      <p>Added a new query parameter to the <code>GET /api/v2/persons</code> API. If supplied, only persons linked to the specified deal are returned.</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/Persons#getPersons">GET /api/v2/persons</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 deal_id parameter for GET /api/v2/persons endpoint

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Feb 1st, 2026</span>
    </div>
    <div class="change-area">
      
      <h2>Deprecation of Channels API</h2>
      <p>We are deprecating the Channel API to concentrate on developing the next generation of our CRM. All conversation data will remain preserved — any existing messages linked to deals or other entities will continue to be available in your account as notes, ensuring your communication history is not lost.</p>
      
      <h2>What will change?</h2>
      <p>We are deprecating Channel API endpoints (listed below). These endpoints will remain accessible until <b>February 1st, 2026</b>.</p>
      
      <h3>Deprecated endpoints:</h3>
      
      <ul>
        <li><code>POST /v1/channels</code></li>
        <li><code>POST /v1/channels/messages/receive</code></li>
        <li><code>DELETE /v1/channels/{id}</code></li>
        <li><code>DELETE /v1/channels/{channel-id}/conversations/{conversation-id}</code></li>
      </ul>
      
      <h2>Who is affected?</h2>
      <p>If you currently use the Omnichannel API beta, you'll need to transition to an alternative solution before deprecation date to avoid any service disruptions.</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>

<br />

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

Deprecation of Channels API


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">Feb 1st, 2026</span>
    </div>
    <div class="change-area">
      
      <h2>Deprecation of Channels API</h2>
      <p>We are deprecating the Channel API to concentrate on developing the next generation of our CRM. All conversation data will remain preserved — any existing messages linked to deals or other entities will continue to be available in your account as notes, ensuring your communication history is not lost.</p>
      
      <h2>What will change?</h2>
      <p>We are deprecating Channel API endpoints (listed below). These endpoints will remain accessible until <b>February 1st, 2026</b>.</p>
      
      <h3>Deprecated endpoints:</h3>
      
      <ul>
        <li><code>POST /v1/channels</code></li>
        <li><code>POST /v1/channels/messages/receive</code></li>
        <li><code>DELETE /v1/channels/{id}</code></li>
        <li><code>DELETE /v1/channels/{channel-id}/conversations/{conversation-id}</code></li>
      </ul>
      
      <h2>Who is affected?</h2>
      <p>If you currently use the Omnichannel API beta, you'll need to transition to an alternative solution before deprecation date to avoid any service disruptions.</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: Deprecation of Channels API

<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>We have added new bulk operation endpoints to our Deal Products API. These new endpoints allow you to efficiently manage multiple products attached to deals in a single request, enabling streamlined deal composition and product management workflows. </p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The Deal Products bulk operations include the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addManyDealProducts">POST /api/v2/deals/{id}/products/bulk</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#deleteManyDealProducts">DELETE /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 new Deal Products bulk operations API endpoints


<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>We have added new bulk operation endpoints to our Deal Products API. These new endpoints allow you to efficiently manage multiple products attached to deals in a single request, enabling streamlined deal composition and product management workflows. </p>
      
      <h2>Summary of the changed endpoints</h2>
			<p>The Deal Products bulk operations include the following endpoints:</p>
      <ul>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addManyDealProducts">POST /api/v2/deals/{id}/products/bulk</a></li>
        <li><a href="https://developers.pipedrive.com/docs/api/v1/Deals#deleteManyDealProducts">DELETE /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 Deal Products bulk operations API

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


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog