[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">March 12, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p><b>What is changing?</b></p>\n      <ol>\n        <li>We’re adding a new Labels field (<code>label_ids</code>), with the type <code>set</code> for the following <b>Persons</b> and <b>Organizations</b> API endpoints. The <code>Labels</code> field <b>can store up to 100 values per entity</b>.</li>\n              \n              <ul>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealParticipants\" target=\"blank\">GET /v1/deals/{id}/participants</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizations\" target=\"blank\">GET /v1/organizations</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganization\" target=\"blank\">GET /v1/organizations/{id}</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationPersons\" target=\"blank\">GET /v1/organizations/{id}/persons</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization\" target=\"blank\">POST /v1/organizations</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#updateOrganization\" target=\"blank\">PUT /v1/organizations/{id}</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#mergeOrganizations\" target=\"blank\">PUT /v1/organizations/{id}/merge</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#getPersons\" target=\"blank\">GET /v1/persons</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#getPerson\" target=\"blank\">GET /v1/persons/{id}</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#addPerson\" target=\"blank\">POST /v1/persons</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#updatePerson\" target=\"blank\">PUT /v1/persons/{id}</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#mergePersons\" target=\"blank\">PUT /v1/persons/{id}/merge</a></code></li>\n              </ul>\n\n        <li>The endpoints <code><a href=\"https://developers.pipedrive.com/docs/api/v1/PersonFields#getPersonFields\" target=\"blank\">GET /v1/personFields</a></code> and <code><a href=\"https://developers.pipedrive.com/docs/api/v1/OrganizationFields#getOrganizationFields\" target=\"blank\">GET /v1/organizationFields</a></code> will return the definition of these fields</li>\n\n        <li>The old <code>Label</code> field and the new <code>Labels</code> field are updated synchronously based on these rules:</li>\n              \n              <ul>\n                <li>When the <code>Labels</code> field is updated, the <code>Label</code> field value will be set to the first value of the <code>Labels</code> field.</li>\n                <li>When the <code>Label</code> field is updated, the <code>Labels</code> field value will be overwritten by the <code>Label</code> field value.</li>\n              </ul>\n      </ol>\n      \n      <p><b>Why is this changing?</b></p>\n      <p>We’re changing the behavior of the existing Label field to prevent data inconsistency between the old and new fields.</p>\n\n\n      <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>\n\n\t\t</div>\n</div>"
}
[/block]

We are introducing a new Labels field for the Contacts.

Introducing a new Labels field and modifying the behavior of the existing Label field

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">June 10, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p><b>What is changing?</b></p>\n      <p>The <b><code>duration</code></b> and <b><code>duration_unit</code></b> request body and response parameters will be removed from three deal-products endpoints on June 10th, 2024:</p>\n            <ul>\n              <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts\" target=\"blank\">GET /deals/{id}/products</a></code></li>\n              <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"blank\">POST /deals/{id}/products</a></code></li>\n              <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"blank\">PUT /deals/{id}/products/{product_attachment_id}</a></code></li>\n            </ul>\n\n      <p><b>What is changing?</b></p>\n      <p>We’re replacing product durations with a new recurring products feature to allow users to attach products with a recurring billing cycle to deals. Users will be able to see the revenue of recurring products based on the billing frequency, cycles and start dates in reporting and forecasting via the Insights feature. This change should better serve the needs of our customers who sell subscriptions, licenses and recurring products and services.</p>\n      <p>New fields are now available for customers who <b>meet both</b> of the terms below:</p>\n      <ul>\n      \t<li>Have a subscription to Advanced plans and above.</li>\n        <li>Have previously used durations in the POST and PUT endpoints to edit the billing frequency and billing cycles (for example, a monthly subscription active for 12 months).</li>\n      </ul>\n      \n      <p>Instead of using product durations in product attachments as a time quantity, users can now use a combination of the product attachment quantity and the product unit fields. For example, a service charged by the number of work hours.</p>\n      \n      <p><b>Migration guide</b></p>\n      \n      <p>On the API change’s effective date of June 10th, 2024, the product attachments’ <b><code>duration</code></b> and <b><code>duration_unit</code></b> fields will be removed from the API.</p>\n      <ul>\n      \t<li>The product attachment <b><code>duration</code></b> field value will be merged into the <b><code>quantity</code></b> field value where <code>quantity = quantity * duration</code>.</li>\n        <li>The <b><code>duration_unit</code></b> values will be lost.</li>\n      </ul>\n      \n      <p>To migrate duration data to the new product subscriptions feature, it’s now possible to move values to the new <b><code>billing frequency</code></b> and <b><code>billing cycles</code></b> product attachment fields through these endpoints:</p>\n       <ul>\n         <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"blank\">POST /deals/{id}/products</a></code></li>\n         <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"blank\">PUT /deals/{id}/products/{product_attachment_id}</a></code></li>\n      </ul>\n      \n      <p>The fields are available in beta testing for users subscribed to the <b>Advanced</b> plan and above with previously used durations. Customers who aren’t included in the beta testing group can contact Pipedrive’s support and ask to be included. These are the new fields request body parameters:</p>\n      \n      <ul>\n      \t<li><b><code>billing_frequency</code></b></li>\n        \t<ul>\n      \t\t\t<li>Type: <code><b>string</b></code></li>\n        \t\t<li>Description: <code>How often a customer is billed for access to a service or product.</code></li>\n                <li>Values: <code><b>one-time</b>, <b>annually</b>, <b>semi-annually</b>, <b>quarterly</b>, <b>monthly</b>, <b>weekly</b></code></li>\n                \t<ul>\n      \t\t\t\t\t<li>Default: <code><b>one-time</b></code></li>\n                \t</ul>\n      \t\t</ul>\n        <li><b><code>billing_frequency_cycles</code></b></li>\n        \t<ul>\n      \t\t\t<li>Type: <code><b>number</b></code></li>\n        \t\t<li>Description: <code>The number of times the billing frequency repeats for a product in a deal. It can be set to null if the number of cycles is infinite, in which case the deal value will be incremented with 1 year of cycles.</code></li>\n                <li>Values: <code><b>null</b></code> or higher than <code><b>1</b></code>. When billing frequency is set to <code><b>one-time</b></code>, this value must be set to <code><b>null</b></code>.</li>\n                \t<ul>\n      \t\t\t\t\t<li>Default: <code><b>null</b></code></li>\n                \t</ul>\n      \t\t</ul>\n      </ul>\n      \n      <p>Some things to consider when copying the <b><code>duration</code></b> values to the new fields:</p>\n      \n      <ul>\n      \t<li>The <b><code>duration</code></b> value should be set to <code><b>1</b></code> so that it’s no longer considered for the deal value.</li>\n        <li>The <b>deal value</b> will change if there are <b>amount discounts</b> in either the updated product attachment or additional discounts.</li>\n        <li>For <b>companies</b> in the <b>Essential plan</b>, we recommend merging the <b><code>duration</code></b> value with <b><code>quantity</code></b> and updating the product unit with the <b><code>duration_unit</code></b> value.</li>\n      </ul>\n\n\n      <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>\n\n\t\t</div>\n</div>\n"
}
[/block]

{"product": ["API"], "features": ["Products”,”Deals"], label:”Update”, “email_description”: “We are deprecating duration and duration_unit request body and response parameters from three deal-products endpoints” }

Breaking change: Product durations deprecation

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">February 02, 2024</span>\n    </div>\n    <div class=\"change-area\">\n<p><b>What is changing?</b></p>\n<p>We've introduced a new cursor-paginated endpoint to retrieve deal participants' changelog:\n</p>\n\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealParticipantsChangelog\" target=\"blank\">GET /deals/{id}/participantsChangelog</a></code></li>\n      </ul>\n<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 \n      <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>\n\n<p><b>Why is it changing?</b></p>\n<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>\n\n\n<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>\n\n\t\t</div>\n</div>"
}
[/block]

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

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

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">March 4, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <h3><b>What is changing?</b></h3>\n      <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>\n      <p>Starting from March 4th, this field will be removed from the webhooks API responses.</p>\n      \n      <h3><b>Why is it changing?</b></h3>\n      <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>\n\n      <p>Reach out to us through the <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">Developers’ Community</a> for any questions or comments.</p>\n\t</div>\n</div>"
}
[/block]

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

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">March 25, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We are changing how deals, leads and projects can be linked to activities.</p>\n<br/>\n<p><b>What is changing?</b></p>\n<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>\n<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:\n</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Activities#addActivity\" target=\"blank\">POST /v1/activities</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Activities#updateActivity\" target=\"blank\">PUT /v1/activities/{id}</a></code></li>\n      </ul>\n<p>It means that an activity can only be linked either to a deal, lead or a project. </p>\n<p>If passing several of the mentioned entities in the payload the following hierarchy for linking will be used:</p>\n      <ul>\n        <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>\n        <li>If <code>lead_id</code> is passed together with <code>project_id</code> the activity will be only linked to the lead</li>\n      </ul>\n\n<p><b>What is changing?</b></p>\n<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>\n\n\n<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>\n\n\t\t</div>\n</div>"
}
[/block]

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

Changes to activities connected entities

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">January 26, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <h3><b>What is changing?</b></h3>\n      <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>\n      \n      <p><b>webhooks:read</b></p>\n      <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>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Webhooks#getWebhooks\" target=\"blank\">GET /v1/webhooks</a></code></li>\n      </ul>\n      \n      <p><b>webhooks:full</b></p>\n      <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>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Webhooks#getWebhooks\" target=\"blank\">GET /v1/webhooks</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Webhooks#addWebhook\" target=\"blank\">POST /v1/webhooks</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Webhooks#deleteWebhook\" target=\"blank\">DELETE /v1/webhooks/{id}</a></code></li>\n      </ul>\n      <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>\n      \n      <h3><b>Why is it changing?</b></h3>\n      <p>We’ve implemented this change to allow flexible, more granular access to users’ data and improve app accessibility.</p>\n      \n      <h3><b>Migration guide</b></h3>\n      <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>\n      <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>\n      <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>\n      <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>\n      \n\t\t</div>\n</div>"
}
[/block]

Introducing new OAuth scopes for Webhooks

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">January 16, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <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>.\n      <ul>\n        <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>\n        <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>\n      </ul></p>\n      \n\t\t<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>\n\n\t\t</div>\n</div>"
}
[/block]

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

New <code>/userProviderLinks</code> endpoints

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">March 18, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <p><b>What is changing?</b></p>\n      \n      <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>\n      \n      <p><b>Why is it changing?</b></p>\n      \n      <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>\n      \n      <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>\n      \n      </div>\n</div>"
}
[/block]

We are starting to restrict editing of soft deleted deals

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

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">December 18, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <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>\n      \n      <p><b>What was added</b></p>\n      \n      <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>\n      <ul>\n        <li><code>lead_id</code> - The ID of the lead the call log is associated with in UUID format (optional)</li>\n      </ul>\n      \n      <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>\n      <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>\n      \n      </div>\n</div>"
}
[/block]

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

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

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">October 18, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      <p><b>What is new?</b></p>\n      <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.\n</p>\n      <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.\n      </p>\n      <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.\n </p>\n      <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.\n</p>\n      <br>\n      <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>.\nThe 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>.\n</p>\n      <br>\n      <p><b>Timeline of the launch</b></p>\n      <p>\n        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.\nKeep in mind that between the BETA and the full release of the API, the endpoints are subject to changes.\n      </p>\n      <p>We are eager to hear your feedback, questions or comments in\n<a href=\"https://devcommunity.pipedrive.com/\" target=\"_self\">the Developers’ Community</a>.</p>\n      </div>\n</div>"
}
[/block]

{“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.“}

Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog