<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">February 02, 2024</span>
    </div>
    <div class="change-area">
<p><b>What is changing?</b></p>
<p>We've introduced a new cursor-paginated endpoint to retrieve deal participants' changelog:
</p>

      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealParticipantsChangelog" target="blank">GET /deals/{id}/participantsChangelog</a></code></li>
      </ul>
<p>This new endpoint is specifically tailored for accessing deal participants' changelog data. It's designed to enhance performance and reduce payload size compared to the existing 
      <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealUpdates" target="blank">GET /deals/{id}/flow</a></code> endpoint, which includes changelogs of various entity types.</p>

<p><b>Why is it changing?</b></p>
<p>In response to user feedback and to provide more granular access to changelog data, we're introducing this specialized endpoint. Other similar endpoints will follow suit. By offering dedicated routes for different types of changelog data, we aim to optimize data retrieval processes and improve overall API efficiency.</p>


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

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

We are introducing a new /deals/{id}/participantsChangelog endpoint

New <code>/deals/{id}/participantsChangelog</code> endpoint


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">February 02, 2024</span>
    </div>
    <div class="change-area">
<p><b>What is changing?</b></p>
<p>We've introduced a new cursor-paginated endpoint to retrieve deal participants' changelog:
</p>

      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealParticipantsChangelog" target="blank">GET /deals/{id}/participantsChangelog</a></code></li>
      </ul>
<p>This new endpoint is specifically tailored for accessing deal participants' changelog data. It's designed to enhance performance and reduce payload size compared to the existing 
      <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealUpdates" target="blank">GET /deals/{id}/flow</a></code> endpoint, which includes changelogs of various entity types.</p>

<p><b>Why is it changing?</b></p>
<p>In response to user feedback and to provide more granular access to changelog data, we're introducing this specialized endpoint. Other similar endpoints will follow suit. By offering dedicated routes for different types of changelog data, we aim to optimize data retrieval processes and improve overall API efficiency.</p>


<p>If you have any questions or comments, please 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 4, 2024</span>
    </div>
    <div class="change-area">
      <h3><b>What is changing?</b></h3>
      <p>During the webhook creation via API, all non-reserved fields were stored as part of the webhook <b>“additional_data”</b> object and sent in the API request response.</p>
      <p>Starting from March 4th, this field will be removed from the webhooks API responses.</p>
      
      <h3><b>Why is it changing?</b></h3>
      <p><b>“additional_data”</b> is a legacy field that isn’t used in the webhook payloads delivery, which slows down events processing. Removing it from the webhooks configuration body will improve system performance and stability.</p>

      <p>Reach out to us through the <a href="https://devcommunity.pipedrive.com/" target="blank">Developers’ Community</a> for any questions or comments.</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 4, 2024</span>
    </div>
    <div class="change-area">
      <h3><b>What is changing?</b></h3>
      <p>During the webhook creation via API, all non-reserved fields were stored as part of the webhook <b>“additional_data”</b> object and sent in the API request response.</p>
      <p>Starting from March 4th, this field will be removed from the webhooks API responses.</p>
      
      <h3><b>Why is it changing?</b></h3>
      <p><b>“additional_data”</b> is a legacy field that isn’t used in the webhook payloads delivery, which slows down events processing. Removing it from the webhooks configuration body will improve system performance and stability.</p>

      <p>Reach out to us through the <a href="https://devcommunity.pipedrive.com/" target="blank">Developers’ Community</a> for any questions or comments.</p>
	</div>
</div>


Removing <code>additional_data</code> from webhooks API responses

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">March 25, 2024</span>
    </div>
    <div class="change-area">
      <p>We are changing how deals, leads and projects can be linked to activities.</p>
<br/>
<p><b>What is changing?</b></p>
<p>At the moment when creating or updating an activity via Public API it is possible to link it with a deal, lead and a project at the same time. </p>
<p>After the changes are applied, it will only be possible to link an activity to one of the mentioned entities at once. The change affects the following 2 endpoints:
</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#addActivity" target="blank">POST /v1/activities</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#updateActivity" target="blank">PUT /v1/activities/{id}</a></code></li>
      </ul>
<p>It means that an activity can only be linked either to a deal, lead or a project. </p>
<p>If passing several of the mentioned entities in the payload the following hierarchy for linking will be used:</p>
      <ul>
        <li>If <code>deal_id</code> is passed together with <code>lead_id</code> or <code>project_id</code> the activity will be only linked to the deal</li>
        <li>If <code>lead_id</code> is passed together with <code>project_id</code> the activity will be only linked to the lead</li>
      </ul>

<p><b>What is changing?</b></p>
<p>Activities have always been intended to work like this but this limitation has never been implemented in our public API. This brings confusion for our users because Pipedrive UI has been built considering this limitation.</p>


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

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

We are changing how deals, leads and projects can be linked to activities


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">March 25, 2024</span>
    </div>
    <div class="change-area">
      <p>We are changing how deals, leads and projects can be linked to activities.</p>
<br/>
<p><b>What is changing?</b></p>
<p>At the moment when creating or updating an activity via Public API it is possible to link it with a deal, lead and a project at the same time. </p>
<p>After the changes are applied, it will only be possible to link an activity to one of the mentioned entities at once. The change affects the following 2 endpoints:
</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#addActivity" target="blank">POST /v1/activities</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Activities#updateActivity" target="blank">PUT /v1/activities/{id}</a></code></li>
      </ul>
<p>It means that an activity can only be linked either to a deal, lead or a project. </p>
<p>If passing several of the mentioned entities in the payload the following hierarchy for linking will be used:</p>
      <ul>
        <li>If <code>deal_id</code> is passed together with <code>lead_id</code> or <code>project_id</code> the activity will be only linked to the deal</li>
        <li>If <code>lead_id</code> is passed together with <code>project_id</code> the activity will be only linked to the lead</li>
      </ul>

<p><b>What is changing?</b></p>
<p>Activities have always been intended to work like this but this limitation has never been implemented in our public API. This brings confusion for our users because Pipedrive UI has been built considering this limitation.</p>


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

		</div>
</div>


Changes to activities connected entities

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 26, 2024</span>
    </div>
    <div class="change-area">
      <h3><b>What is changing?</b></h3>
      <p>We’ve introduced new read-only and full-access OAuth scopes for Webhooks, which allow apps to create, fetch and delete webhooks on users’ behalf.</p>
      
      <p><b>webhooks:read</b></p>
      <p>When the <b><code>webhooks:read</code></b> scope is selected, an app can access the endpoint below, allowing it to list webhooks associated with its user.</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Webhooks#getWebhooks" target="blank">GET /v1/webhooks</a></code></li>
      </ul>
      
      <p><b>webhooks:full</b></p>
      <p>When the <b><code>webhooks:full</code></b> scope is selected, an app can access the endpoints below, allowing it to list webhooks associated with its user, create and delete webhooks for them.</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Webhooks#getWebhooks" target="blank">GET /v1/webhooks</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Webhooks#addWebhook" target="blank">POST /v1/webhooks</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Webhooks#deleteWebhook" target="blank">DELETE /v1/webhooks/{id}</a></code></li>
      </ul>
      <p>Learn more about Pipedrive webhooks <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2" target="blank">here</a> and about scopes and permission <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations" target="blank">here</a>.</p>
      
      <h3><b>Why is it changing?</b></h3>
      <p>We’ve implemented this change to allow flexible, more granular access to users’ data and improve app accessibility.</p>
      
      <h3><b>Migration guide</b></h3>
      <p>Please note that webhook-specific endpoints are still available under the <b><code>admin</code></b> scope. No changes were made to existing public or private apps.</p>
      <p>We’re also working on a separate solution that would allow apps with webhooks to switch from the <b><code>admin</code></b> scope to a new scope without asking users to re-install the app. We’ll share more details about it soon!</p>
      <p>If you still want to add or remove the scopes of an approved or published app, <a href="https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app#changing-the-scopes" target="blank">learn how changing the scopes will affect your app's existing users</a>.</p>
      <p>If you have any questions or comments, please let us know in the <a href="https://devcommunity.pipedrive.com/" target="blank">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">January 26, 2024</span>
    </div>
    <div class="change-area">
      <h3><b>What is changing?</b></h3>
      <p>We’ve introduced new read-only and full-access OAuth scopes for Webhooks, which allow apps to create, fetch and delete webhooks on users’ behalf.</p>
      
      <p><b>webhooks:read</b></p>
      <p>When the <b><code>webhooks:read</code></b> scope is selected, an app can access the endpoint below, allowing it to list webhooks associated with its user.</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Webhooks#getWebhooks" target="blank">GET /v1/webhooks</a></code></li>
      </ul>
      
      <p><b>webhooks:full</b></p>
      <p>When the <b><code>webhooks:full</code></b> scope is selected, an app can access the endpoints below, allowing it to list webhooks associated with its user, create and delete webhooks for them.</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Webhooks#getWebhooks" target="blank">GET /v1/webhooks</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Webhooks#addWebhook" target="blank">POST /v1/webhooks</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Webhooks#deleteWebhook" target="blank">DELETE /v1/webhooks/{id}</a></code></li>
      </ul>
      <p>Learn more about Pipedrive webhooks <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2" target="blank">here</a> and about scopes and permission <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations" target="blank">here</a>.</p>
      
      <h3><b>Why is it changing?</b></h3>
      <p>We’ve implemented this change to allow flexible, more granular access to users’ data and improve app accessibility.</p>
      
      <h3><b>Migration guide</b></h3>
      <p>Please note that webhook-specific endpoints are still available under the <b><code>admin</code></b> scope. No changes were made to existing public or private apps.</p>
      <p>We’re also working on a separate solution that would allow apps with webhooks to switch from the <b><code>admin</code></b> scope to a new scope without asking users to re-install the app. We’ll share more details about it soon!</p>
      <p>If you still want to add or remove the scopes of an approved or published app, <a href="https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app#changing-the-scopes" target="blank">learn how changing the scopes will affect your app's existing users</a>.</p>
      <p>If you have any questions or comments, please let us know in the <a href="https://devcommunity.pipedrive.com/" target="blank">Developers’ Community</a>.</p>
      
		</div>
</div>


Introducing new OAuth scopes for Webhooks

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 16, 2024</span>
    </div>
    <div class="change-area">
      <p>We’ve introduced new endpoints to allow you to integrate video-calling apps into Pipedrive through a <a href="https://pipedrive.readme.io/docs/video-calling-app-extension">video calling app extension</a>.
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Meetings#saveUserProviderLink" target="blank">POST /meetings/userProviderLinks</a></code> – to link a user to the installed video call integration, allowing them to create video call links for their activities.</li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Meetings#deleteUserProviderLink" target="blank">DELETE /meetings/userProviderLinks/{id}</a></code> – to unlink a user from the video call integration when uninstalling it.</li>
      </ul></p>
      
		<p>If you have any questions or comments, please let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

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

We are introducing endpoints for linking and unlinking a user to/from a video call integration.


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">January 16, 2024</span>
    </div>
    <div class="change-area">
      <p>We’ve introduced new endpoints to allow you to integrate video-calling apps into Pipedrive through a <a href="https://pipedrive.readme.io/docs/video-calling-app-extension">video calling app extension</a>.
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Meetings#saveUserProviderLink" target="blank">POST /meetings/userProviderLinks</a></code> – to link a user to the installed video call integration, allowing them to create video call links for their activities.</li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Meetings#deleteUserProviderLink" target="blank">DELETE /meetings/userProviderLinks/{id}</a></code> – to unlink a user from the video call integration when uninstalling it.</li>
      </ul></p>
      
		<p>If you have any questions or comments, please let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>

		</div>
</div>


New <code>/userProviderLinks</code> endpoints

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">March 18, 2024</span>
    </div>
    <div class="change-area">
      
      <p><b>What is changing?</b></p>
      
      <p>From <b>March 18, 2023</b>, we are starting to restrict editing of soft-deleted deals via <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PUT deals/{id}</a></code> endpoint. This means that it is not possible to edit any fields (except restoring the deal) once the <code>status</code> of the deal has changed to <code>deleted</code>. In order to be able to edit that soft deleted deal, you must first restore that deal.</p>
      
      <p><b>Why is it changing?</b></p>
      
      <p>We already have similar behavior for <code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#updatePerson">PUT persons/{id}</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#updateOrganization">PUT organizations/{id}</a></code>. Editing fields after the entity has been soft deleted will push the deadline for permanent deletion further which may cause confusion and additional issues for our customers.</p>
      
      <p>If you have any questions or comments, please let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>
      
      </div>
</div>
`}</HTMLBlock>

We are starting to restrict editing of soft deleted deals


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">March 18, 2024</span>
    </div>
    <div class="change-area">
      
      <p><b>What is changing?</b></p>
      
      <p>From <b>March 18, 2023</b>, we are starting to restrict editing of soft-deleted deals via <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal">PUT deals/{id}</a></code> endpoint. This means that it is not possible to edit any fields (except restoring the deal) once the <code>status</code> of the deal has changed to <code>deleted</code>. In order to be able to edit that soft deleted deal, you must first restore that deal.</p>
      
      <p><b>Why is it changing?</b></p>
      
      <p>We already have similar behavior for <code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#updatePerson">PUT persons/{id}</a></code> and <code><a href="https://developers.pipedrive.com/docs/api/v1/Organizations#updateOrganization">PUT organizations/{id}</a></code>. Editing fields after the entity has been soft deleted will push the deadline for permanent deletion further which may cause confusion and additional issues for our customers.</p>
      
      <p>If you have any questions or comments, please let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>
      
      </div>
</div>


Breaking change: update to the behavior of <code>PUT deals/{id}</code> endpoint for soft-deleted deals

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 18, 2023</span>
    </div>
    <div class="change-area">
      
      <p>We’ve introduced a <b>new body parameter</b> in the <code><a href="https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLog">POST /callLogs</a></code> endpoint allowing you to associate call logs with leads.</p>
      
      <p><b>What was added</b></p>
      
      <p>From <b>December 18, 2023</b>, you can add a new body parameter to the <code><a href="https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLog">POST /callLogs</a></code> endpoint:</p>
      <ul>
        <li><code>lead_id</code> - The ID of the lead the call log is associated with in UUID format (optional)</li>
      </ul>
      
      <p><b>Please note that a single call log can only be associated with either a deal or a lead, not both at the same time.</b></p>
      <p>If you have any questions or comments, please let us know in <a href="https://devcommunity.pipedrive.com/">the Developer’s Community</a>.</p>
      
      </div>
</div>
`}</HTMLBlock>

We are introducing a new optional parameter in POST /callLogs endpoint

New optional parameter in <code>POST /callLogs</code> endpoint


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">December 18, 2023</span>
    </div>
    <div class="change-area">
      
      <p>We’ve introduced a <b>new body parameter</b> in the <code><a href="https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLog">POST /callLogs</a></code> endpoint allowing you to associate call logs with leads.</p>
      
      <p><b>What was added</b></p>
      
      <p>From <b>December 18, 2023</b>, you can add a new body parameter to the <code><a href="https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLog">POST /callLogs</a></code> endpoint:</p>
      <ul>
        <li><code>lead_id</code> - The ID of the lead the call log is associated with in UUID format (optional)</li>
      </ul>
      
      <p><b>Please note that a single call log can only be associated with either a deal or a lead, not both at the same time.</b></p>
      <p>If you have any questions or comments, please 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 18, 2023</span>
    </div>
    <div class="change-area">
      <p><b>What is new?</b></p>
      <p>We’re launching <b>three</b> new API resources with a range of endpoints to help you modify the data around the Projects feature space, allowing integrations and automations to join in on providing solutions in the <b>project and task management</b> problem space. The endpoints are tied with the Projects add-on which has to be enabled for the functionality to be used.
</p>
      <p><b><a href="https://developers.pipedrive.com/docs/api/v1/Projects" target="blank">Projects API</a></b> allows to create and manage ongoing, completed or canceled projects attached to an organization, person or to deals. Each project has an owner and must be placed in a phase. Each project consists of standard data fields but can also contain a number of custom fields. The custom fields can be recognized by long hashes as keys.
      </p>
      <p><b><a href="https://developers.pipedrive.com/docs/api/v1/ProjectsTemplates" target="blank">ProjectsTemplates API</a></b> allows to have a reusable and dynamic structure to simplify creation of a project. Project templates can contain information about activities, tasks and groups that will be used when creating a project. Currently, only GET functionality is available.
 </p>
      <p><b><a href="https://developers.pipedrive.com/docs/api/v1/Tasks" target="blank">Tasks API</a></b> allows to create and manage actions that need to be completed inside a project. A task must be associated with a project. Tasks have an optional due date, can be assigned to a user and can have subtasks.
</p>
      <br>
      <p>All new endpoints support querying based on <a href="https://pipedrive.readme.io/docs/core-api-concepts-pagination#cursor-pagination" target="blank">cursor pagination</a>.
The endpoints are also included in two new OAuth scopes: Projects read and Projects full, see the full division of endpoints in scopes <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations" target="blank">here</a>.
</p>
      <br>
      <p><b>Timeline of the launch</b></p>
      <p>
        We’re releasing the public BETA today, October 18th, 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
<a href="https://devcommunity.pipedrive.com/" target="_self">the Developers’ Community</a>.</p>
      </div>
</div>
`}</HTMLBlock>

{“product”: [“API”], “features”: [“Projects, ProjectTemplates, Tasks”], “email_description”: “We’re happy to share the public BETA launch of Project API together with ProjectTemplates API and Tasks API.“}


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">October 18, 2023</span>
    </div>
    <div class="change-area">
      <p><b>What is new?</b></p>
      <p>We’re launching <b>three</b> new API resources with a range of endpoints to help you modify the data around the Projects feature space, allowing integrations and automations to join in on providing solutions in the <b>project and task management</b> problem space. The endpoints are tied with the Projects add-on which has to be enabled for the functionality to be used.
</p>
      <p><b><a href="https://developers.pipedrive.com/docs/api/v1/Projects" target="blank">Projects API</a></b> allows to create and manage ongoing, completed or canceled projects attached to an organization, person or to deals. Each project has an owner and must be placed in a phase. Each project consists of standard data fields but can also contain a number of custom fields. The custom fields can be recognized by long hashes as keys.
      </p>
      <p><b><a href="https://developers.pipedrive.com/docs/api/v1/ProjectsTemplates" target="blank">ProjectsTemplates API</a></b> allows to have a reusable and dynamic structure to simplify creation of a project. Project templates can contain information about activities, tasks and groups that will be used when creating a project. Currently, only GET functionality is available.
 </p>
      <p><b><a href="https://developers.pipedrive.com/docs/api/v1/Tasks" target="blank">Tasks API</a></b> allows to create and manage actions that need to be completed inside a project. A task must be associated with a project. Tasks have an optional due date, can be assigned to a user and can have subtasks.
</p>
      <br>
      <p>All new endpoints support querying based on <a href="https://pipedrive.readme.io/docs/core-api-concepts-pagination#cursor-pagination" target="blank">cursor pagination</a>.
The endpoints are also included in two new OAuth scopes: Projects read and Projects full, see the full division of endpoints in scopes <a href="https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations" target="blank">here</a>.
</p>
      <br>
      <p><b>Timeline of the launch</b></p>
      <p>
        We’re releasing the public BETA today, October 18th, 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
<a href="https://devcommunity.pipedrive.com/" target="_self">the Developers’ Community</a>.</p>
      </div>
</div>


Introducing Projects API in public BETA

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 7, 2023</span>
    </div>
    <div class="change-area">
      
      <blockquote class="callout callout_info" theme="📘"><p class="callout-heading empty"><span class="callout-icon">📘</span></p><p><strong>We've decided to retract the change to Deals API</strong>: </p><p>After careful consideration and valuable input from feedback from our API users, we have decided to retract the previously announced breaking change to the API.</p><p><strong>Why are we retracting the change?</strong></p><p>Upon reviewing the concerns raised, it became evident that the implementation of workarounds to get the exact time of deal closures would impose undue burdens on our technology partners and customers. Therefore, we have opted to maintain the current functionality, where the relevant fields will continue to return full datetime values as they presently do.</p><p><strong>Will this retraction affect those using the existing API?</strong></p><p>There will be no alterations to the current API behavior, and consequently, no adverse effects will arise for those utilizing the established client code.</p><p><strong>What about those who have already made adjustments towards the new API behavior?</strong></p><p>For those who have proactively updated their code in anticipation of the new API specifications, firstly, thank you for your proactive work. With this retraction, we advise reverting any modifications pertaining to the now-retracted change. The API will continue to function as it did prior to the announcement, negating the necessity for these adjustments.</p><p>We apologize for any inconvenience this announcement may have caused and are committed to ensuring that our API remains user-friendly. Your continued support, feedback and understanding are greatly appreciated.</p><p>We at Pipedrive are committed to ensuring that every customer and partner has a stable and trustworthy experience with all of our products and services. Therefore, we’ll continue with transparent communications regarding our API and developer platform.</p></blockquote>
      
      <p><b>What is changing?</b></p>
      <p>The data type for the <code>close_time</code>, <code>won_time</code>, <code>first_won_time</code>, and <code>lost_time</code> response fields will be changed from <code>datetime</code> to <code>date</code> for the following Deals API endpoints:</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals" target="blank">GET /deals</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline" target="blank">GET /deals/timeline</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeal" target="blank">GET /deals/{id}</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="blank">POST /deals</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#duplicateDeal" target="blank">POST /deals/{id}/duplicate</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="blank">PUT /deals/{id}</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#mergeDeals" target="blank">PUT /deals/{id}/merge</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonDeals" target="blank">GET /persons/{id}/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelineDeals" target="blank">GET /pipelines/{id}/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductDeals" target="blank">GET /products/{id}/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Recents#getRecents" target="blank">GET /recents</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Stages#getStageDeals" target="blank">GET /stages/{id}/deals</a></code></li>
      </ul>
     
      
      <p>Similarly, the <code>won_time</code> and <code>lost_time</code> response fields will be changed from <code>datetime</code> to <code>date</code> in the <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsCollection" target="blank">GET /deals/collection</a></code> endpoint.</p>
      
      <p>The update will be gradually rolled out between <b>December 6 and December 13, 2023</b>.</p>
      
      <p>If you have any questions or comments, let us know in <a href="https://devcommunity.pipedrive.com/" target="_self">the Developers' Community</a>.</p>
   
      
      </div>
</div> 
`}</HTMLBlock>

We are updating the data type for four deals-related response fields from datetime to date.


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 7, 2023</span>
    </div>
    <div class="change-area">
      
      <blockquote class="callout callout_info" theme="📘"><p class="callout-heading empty"><span class="callout-icon">📘</span></p><p><strong>We've decided to retract the change to Deals API</strong>: </p><p>After careful consideration and valuable input from feedback from our API users, we have decided to retract the previously announced breaking change to the API.</p><p><strong>Why are we retracting the change?</strong></p><p>Upon reviewing the concerns raised, it became evident that the implementation of workarounds to get the exact time of deal closures would impose undue burdens on our technology partners and customers. Therefore, we have opted to maintain the current functionality, where the relevant fields will continue to return full datetime values as they presently do.</p><p><strong>Will this retraction affect those using the existing API?</strong></p><p>There will be no alterations to the current API behavior, and consequently, no adverse effects will arise for those utilizing the established client code.</p><p><strong>What about those who have already made adjustments towards the new API behavior?</strong></p><p>For those who have proactively updated their code in anticipation of the new API specifications, firstly, thank you for your proactive work. With this retraction, we advise reverting any modifications pertaining to the now-retracted change. The API will continue to function as it did prior to the announcement, negating the necessity for these adjustments.</p><p>We apologize for any inconvenience this announcement may have caused and are committed to ensuring that our API remains user-friendly. Your continued support, feedback and understanding are greatly appreciated.</p><p>We at Pipedrive are committed to ensuring that every customer and partner has a stable and trustworthy experience with all of our products and services. Therefore, we’ll continue with transparent communications regarding our API and developer platform.</p></blockquote>
      
      <p><b>What is changing?</b></p>
      <p>The data type for the <code>close_time</code>, <code>won_time</code>, <code>first_won_time</code>, and <code>lost_time</code> response fields will be changed from <code>datetime</code> to <code>date</code> for the following Deals API endpoints:</p>
      <ul>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeals" target="blank">GET /deals</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline" target="blank">GET /deals/timeline</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDeal" target="blank">GET /deals/{id}</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#addDeal" target="blank">POST /deals</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#duplicateDeal" target="blank">POST /deals/{id}/duplicate</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal" target="blank">PUT /deals/{id}</a></code></li>
         <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#mergeDeals" target="blank">PUT /deals/{id}/merge</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Persons#getPersonDeals" target="blank">GET /persons/{id}/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelineDeals" target="blank">GET /pipelines/{id}/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Products#getProductDeals" target="blank">GET /products/{id}/deals</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Recents#getRecents" target="blank">GET /recents</a></code></li>
        <li><code><a href="https://developers.pipedrive.com/docs/api/v1/Stages#getStageDeals" target="blank">GET /stages/{id}/deals</a></code></li>
      </ul>
     
      
      <p>Similarly, the <code>won_time</code> and <code>lost_time</code> response fields will be changed from <code>datetime</code> to <code>date</code> in the <code><a href="https://developers.pipedrive.com/docs/api/v1/Deals#getDealsCollection" target="blank">GET /deals/collection</a></code> endpoint.</p>
      
      <p>The update will be gradually rolled out between <b>December 6 and December 13, 2023</b>.</p>
      
      <p>If you have any questions or comments, let us know in <a href="https://devcommunity.pipedrive.com/" target="_self">the Developers' Community</a>.</p>
   
      
      </div>
</div> 


Breaking change: data type update for 4 deals-related response fields

<HTMLBlock>{`
<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 5, 2023</span>
    </div>
    <div class="change-area">
      
      <p>We have implemented the following bug fixes in <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2#webhook-format" target="blank">webhooks v2</a> for better user management and consistency with webhooks v1:</p>
     
      <p>1. The <code>user_id</code> field in the payload now represents the ID of the user who triggered the webhook. Previously, the field represented the owner of the webhook.</p>
      
      <p>2. We have added the <code>webhook_owner_id</code> field inside the meta section of the payload. This field represents the ID of the user who created the webhook.</p>
      
      <p>Please refer to our <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2#webhook-format" target="blank">webhooks v2 guide</a> for more details. For any questions or comments, please share them in <a href="https://devcommunity.pipedrive.com/" target="blank">our Developers’ Community</a>.</p>
      
      
      </div>
</div>
`}</HTMLBlock>

We have implemented two bug fixes in the webhooks v2 payload for better user management.


<div class="chlog-box">
    <div class="from-area">
        <span class="from-label">Effective from:</span><br>
        <span class="from-date">September 5, 2023</span>
    </div>
    <div class="change-area">
      
      <p>We have implemented the following bug fixes in <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2#webhook-format" target="blank">webhooks v2</a> for better user management and consistency with webhooks v1:</p>
     
      <p>1. The <code>user_id</code> field in the payload now represents the ID of the user who triggered the webhook. Previously, the field represented the owner of the webhook.</p>
      
      <p>2. We have added the <code>webhook_owner_id</code> field inside the meta section of the payload. This field represents the ID of the user who created the webhook.</p>
      
      <p>Please refer to our <a href="https://pipedrive.readme.io/docs/guide-for-webhooks-v2#webhook-format" target="blank">webhooks v2 guide</a> for more details. For any questions or comments, please share them in <a href="https://devcommunity.pipedrive.com/" target="blank">our Developers’ Community</a>.</p>
      
      
      </div>
</div>


Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog