[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 3, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We are introducing six new fields. With the addition of the subscription deal products, new fields were added to better reflect a deal’s value</p>\n      \n\t\t\t<br/>\n      \n\t\t\t<h2>What is being added?</h2>\n\n\t\t\t\n      <p>The new fields are: <br />\n        <ul>\n          <li>\n            <code>mrr</code> - Monthly Recurring Revenue. Recurring revenue of the deal subscriptions per month\n          </li>\n          <li>\n            <code>arr</code> - Annual Recurring Revenue. Recurring revenue of the deal subscriptions per year\n          </li>\n          <li>\n            <code>acv</code> - Annual Contract Value. Sum of recurring revenue and one-time fees in a single year for a deal\n          </li>\n          <li>\n            <code>mrr_currency</code> - Currency of the <code>mrr</code> field\n          </li>\n          <li>\n            <code>arr_currency</code> - Currency of the <code>arr</code> field\n          </li>\n          <li>\n            <code>acv_currency</code> - Currency of the <code>acv</code> field\n          </li>\n        </ul>\n\n\t      <p>They were also added to the responses of the following endpoints:</p>\n      <ul>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDeals\" target=\"_blank\">GET /v1/deals</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDeal\" target=\"_blank\">GET /v1/deals/{id}</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline\" target=\"_blank\">GET /v1/deals/timeline</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDeal\" target=\"_blank\">POST /v1/deals</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#duplicateDeal\" target=\"_blank\">POST /v1/deals/duplicate</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal\" target=\"_blank\">PUT /v1/deals/{id}</li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal\" target=\"_blank\">PUT /v1/deals/{id}/merge</a></li>\n      </ul>\n\t\t\t</p>      \n\n     \t<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>\n\n\t\t</div>\n</div>"
}
[/block]

We are adding new deal value fields in the Deals Endpoints

New deal values fields for customers in Advanced Plan or above

[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\">May 20, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We are introducing 4 new fields for Leads and Deals</p>\n      \n\t\t\t<h2>What is being added?</h2>\n\n\t\t\t\n      <p>The following fields are being added to Leads and Deals:<br />\n        <ul>\n          <li>\n            <code>origin</code> - a system-generated value indicating how the entity was created (e.g. Import, API, Manually created). User cannot change this value\n          </li>\n          <li>\n            <code>origin_id</code> - a system-generated value which specifies the <code>origin</code> further. User can supply a value in POST payload. In other cases the value is autofilled when applicable (e.g. in case <code>origin</code> is <code>Import</code>, the <code>origin_id</code> is the unique batch id). User cannot change this value\n          </li>\n          <li>\n            <code>channel</code> - single option editable value to further specify entity source based on marketing channel. In certain cases this field is autofilled, but it doesn’t restrict users to manipulate it afterwards\n          </li>\n          <li>\n            <code>channel_id</code> - text field for users to further specify the <code>channel</code> by themselves. In certain cases this field is autofilled, but it doesn’t restrict users to manipulate it afterwards\n          </li>\n        </ul>\n\n\t      <p>All four new fields are included in respective <code>GET</code>, <code>POST</code> and <code>PUT</code> responses. <code>channel</code> and <code>channel_id</code> can be included in respective <code>POST</code> and <code>PUT</code> payloads. User can get list of currently supported values for <code>origin</code> and <code>channel</code> fields from <a href=\"https://developers.pipedrive.com/docs/api/v1/DealFields#getDealFields\" target=\"_blank\">DealFields endpoint</a></p>\n        <p>You can read more about these new fields and how to use them  in our <a href=\"https://support.pipedrive.com/en/article/lead-source-deals\">Knowledge Base article</a></p>\n        \n\t\t\t</p>      \n\n     \t<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>\n\n\t\t</div>\n</div>"
}
[/block]

We are adding 4 new fields for Deals and Leads to represent entity source

Introducing 4 new fields for Leads and 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\">May 14, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>Products and Deal Products have new fields designed for managing and streamlining the sale of products that are billed recurrently.\nThese fields are only available starting from the Advanced plan.</p>\n      \n\t\t\t<br/>\n      \n\t\t\t<h2>What is being added?</h2>\n\n\t\t\t<h3>Products</h3>\n\t\t\t<p>The new fields are:</p>  \n      <ul>\n        <li><i>billing_frequency</i> - How often a customer is billed for access to a service or product</li>\n        <li><i>billing_frequency_cycles</i> - The number of times the billing frequency repeats for a product in a deal\n</li>\n      </ul>\n      \n      <p>These fields were added as body parameters to the following endpoints:</p>\n      <ul>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#addProduct\" target=\"_blank\">POST /v1/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#updateProduct\" target=\"_blank\">PUT /v1/products/{id}</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v2/Products#addProduct\" target=\"_blank\">POST /v2/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v2/Products#updateProduct\" target=\"_blank\">PUT /v2/products/{id}</a></li>\n      </ul>\n      \n      <p>They were also added to the responses of the following endpoints:</p>\n      <ul>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#getProducts\" target=\"_blank\">GET /v1/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#getProduct\" target=\"_blank\">GET /v1/products/{id}</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#addProduct\" target=\"_blank\">POST /v1/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#updateProduct\" target=\"_blank\">PUT /v1/products/{id}</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#getProducts\" target=\"_blank\">GET /v2/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#getProduct\" target=\"_blank\">GET /v2/products/{id}</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#addProduct\" target=\"_blank\">POST /v2/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#updateProduct\" target=\"_blank\">PATCH /v2/products/{id}</a></li>\n      </ul>\n      \n      \n      <h3>Deal Products</h3>\n\t\t\t<p>The new fields are:</p>  \n      <ul>\n        <li><i>billing_frequency</i> - How often a customer is billed for access to a service or product</li>\n        <li><i>billing_frequency_cycles</i> - The number of times the billing frequency repeats for a product in a deal\n</li>\n        <li><i>billing_start_date</i> - When the product will start to be billed\n</li>\n      </ul>\n      \n      <p>These fields were added as body parameters to the following endpoints:</p>\n      <ul>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"_blank\">POST /v1/deals/{id}/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"_blank\">PUT /v1/deals/{id}/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts\" target=\"_blank\">GET /v2/deals/{id}/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"_blank\">POST /v2/deals/{id}/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"_blank\">PATCH  /v2/deals/{id}/products</a></li>\n      </ul>\n      \n      <p>They were also added to the responses of the following endpoints:</p>\n      <ul>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts\" target=\"_blank\">GET /v1/deals/{id}/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"_blank\">POST /v1/deals/{id}/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"_blank\">PUT /v1/deals/{id}/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts\" target=\"_blank\">GET /v2/deals/{id}/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"_blank\">POST /v2/deals/{id}/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"_blank\">PATCH  /v2/deals/{id}/products</a></li>\n        <li><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealsProducts\" target=\"_blank\">GET /v2/deals/products</a></li>\n        \n      </ul>\n\n      <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>\n\n\t\t</div>\n</div>"
}
[/block]

{"product": ["API"], "features": ["Products", ], "email_description": "New subscription fields in Products and Deal Products endpoints" }

New subscription fields in Products and Deal Products 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\">May 09, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We’re launching app onboarding/feature guide as well as app home page functionalities to further support app activation and engagement!\n</p>\n<br/>\n<h2>What is being added?</h2>\n\n<h3>1. App onboarding guide</h3>\n      \n<p>This feature enables app creators to add an onboarding guide that empowers users to familiarize themselves with a newly installed \n  app through an overview of its features or step-by-step instructions. This can help reduce the learning curve, maximize value extraction and foster adoption.\n      </p>  \n\n<p>You can now create the guide directly in the <A href=\"https://app.pipedrive.com/developer-hub\"><b>Developer Hub</b></a> and break it it into individual segments using content blocks. \n  To make the guide more engaging, you can add a link to a tutorial video or add a link to an onboarding article.\n      </p>  \n      \n<p><img alt=\"\" loading=\"lazy\" src=\"https://files.readme.io/9883b7e-Navigation.png\" title=\"\" align=\"center\" class=\"\" caption=\"\" height=\"auto\" width=\"auto\"></p>\n\n<p>Users will be prompted to view the guide upon installing the app and returning to Pipedrive. They can access the guide at any time from the\n  <b>Apps dock</b> (“My apps” panel) or from the app home page under <b>Settings → Tools and apps → Marketplace apps</b>.\n      </p>\n      \n<p><img alt=\"\" loading=\"lazy\" src=\"https://files.readme.io/bbd85d8-example_modal.png\" title=\"\" align=\"center\" class=\"\" caption=\"\" height=\"auto\" width=\"auto\"></p>\n\n<p>\n  Read more about it in the <a href=\"https://pipedrive.readme.io/docs/marketplace-registering-the-app#onboarding-for-users\">documentation</a>.\n</p>\n\n      <br/>\n\n<h3>2. App home page</h3>\n<p>\n      This page serves as a central hub where users who have installed your app can find everything related to it, from general information to permissions, \n  an onboarding/feature guide, support information, <a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions-app-settings\">app settings</a>, \n  <a href=\"https://pipedrive.readme.io/docs/app-sharing-adding-apps-to-multiple-users\">>app sharing management</a> and the option to uninstall it. \n  It’s accessible from the <b>Tools & Apps > Marketplace Apps</b> or the <b>Apps dock</b> (“My apps” panel) in the top menu bar.\n  <a href=\"https://pipedrive.readme.io/docs/app-home-page\">Learn more about it</a>.\n</p>\n\n<p><img alt=\"\" loading=\"lazy\" src=\"https://files.readme.io/a3c27c7-image.png\" align=\"center\" class=\"\" width=\"100%\" caption=\"\" height=\"auto\" title=\"\"></p>\n\n <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>\n      \n\t\t</div>\n</div>"
}
[/block]

"We are launching app onboarding guide and app home page features to help with app activation and engagement."

Introducing app onboarding guide and app home page

[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\">April 08, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We’re introducing app-sharing functionality for apps. When enabled, it allows an admin user to add the app to other users within the same Pipedrive company. \n        Adding apps to users will significantly increase the number of app installations per company, possibly increasing your app's new users and reducing churn probability of your customers.</p>\n<br/>\n<p><b>What is being added?</b></p>\n<p>The app-sharing feature can be enabled for most apps if they meet some essential criteria. \n  It allows admin users to initiate the sharing process by selecting a group of users within their company upon app installation. \n  Once shared, team members will receive notifications through multiple channels and will need to authorize the app to start using it.\n  Read more about it in the <a href=\"https://pipedrive.readme.io/docs/app-sharing-adding-apps-to-multiple-users\">documentation</a>.\n</p>\n\n    \n\n\n<p><b>Why was it added?</b></p>\n<p>\n      In many companies, due to the lack of a centralized system for sharing information, admins often rely on communication channels like Slack or email to push an app or integration forward, which may result in lower adoption rates and data silos. Allowing admins to add apps to multiple users in one go saves time while encouraging app adoption.\n      </p>\n<p>\nFor users, seamless access to information about added apps from a trustworthy source, along with entry points that redirect them to the authorization page, reduces barriers to installation and boosts confidence in authorizing the app, resulting in a significantly streamlined process.\n</p>\n<p>\nApp creators benefit from increased app visibility, higher utilization of the app within a customer company, and ultimately, better business results.\n</p>\n      </p>\n\n\t\t</div>\n</div>"
}
[/block]


<br>

We are announcing a new developer platform feature that allows you to enable app sharing for your app.

App sharing: Adding apps to multiple users

[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 14, 2024</span>\n    </div>\n    <div class=\"change-area\">\n<p><b>What is being added?</b></p>\n<p>We've introduced new endpoints to retrieve updates about field values of different entities:\n</p>\n\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealChangelog\" target=\"blank\">GET /deals/{id}/changelog</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#getPersonChangelog\" target=\"blank\">GET /persons/{id}/changelog</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationChangelog\" target=\"blank\">GET /organizations/{id}/changelog</a></code></li>\n      </ul>\n\n\n<p><b>Why is it changing?</b></p>\n<p>We are providing new endpoints specifically to fetch changes in deal, person and organization field values. They are similar to the existing \n  <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealUpdates\" target=\"blank\">/flow</a></code> endpoints but are more performant due to returning only one type of change and using cursor pagination.      \n      </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]


<br>

We are introducing several new <code>/changelog</code> endpoints with improved performance compared to existing /flow endpoints.

New <code>/changelog</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\">May 20, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p><b>What is changing?</b></p>\n      \n      <p>From May 20, 2024, fields <code>deal_id</code> and <code>org_id</code> must be either an integer or a string representing an integer. </p>\n      <p>The change affects the following endpoints:</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      \n      <p><b>Why is this changing?</b></p>\n      <p>We’re making this change to ensure the reliable processing of requests in Activities API and avoid interruptions in later stages.</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]

Fields deal_id and org_id must be either an integer or a string representing an integer.

Breaking change: updated validation rules for <code>POST/PUT /activities/{id}</code>

[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 29, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>Between the 29th of February and 4th of March, we rolled out the possibility of deleting users permanently from a company account upon deactivation. Deleted users’ personal information, including their name, email, phone number and profile picture, will be deleted and replaced with  “(deleted user)”, whereas their non-personal data will remain visible. </p>\n<br/>\n<p><b>What is changing?</b></p>\n<p>To indicate this new user’s status, we’ll include a new response boolean field <code>is_deleted: true | false</code> to the following endpoints in <code>Users API</code>:\n</p>\n      <ul>\n        <li><code>GET</code> endpoints \n          <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#getUsers\" target=\"blank\">/v1/users</a></code>,\n          <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#findUsersByName\" target=\"blank\">/v1/users/find</a></code>,\n          <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#getCurrentUser\" target=\"blank\">/v1/users/me</a></code>,\n          <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#getUser\" target=\"blank\">/v1/users/{id}</a></code>\n          </li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#addUser\" target=\"blank\">POST /v1/users</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#updateUser\" target=\"blank\">PUT /v1/users/{id}</a></code></li>\n      </ul>\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'll add a new field to <code>Users API.</code>

New field added to <code>Users API</code>

[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      \n      <p><code>Label</code> field can store up to 100 values per entity.</p>\n      <p>The change affects the following deals-related endpoints:</p>\n              \n              <ul>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDeal\" target=\"blank\">POST /deals</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#duplicateDeal\" target=\"blank\">POST /deals/{id}/duplicate</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal\" target=\"blank\">PUT /deals/{id}</a></code></li>\n                <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#mergeDeals\" target=\"blank\">PUT /deals/{id}/merge</a></code></li>\n              </ul>\n      \n      <p><b>Why is this changing?</b></p>\n      <p>We are changing the behavior of the <code>Label</code> field to improve API performance and ensure logic consistency across entities.</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 limiting the number of values the Label field can store per Deal

Limiting the number of values the Label field can store per Deal

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

Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog