[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 5, 2021</span>\n    </div>\n    <div class=\"change-area\">\n      <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n        <div class=\"heading-anchor anchor waypoint\" id=\"change-in-the-availability-of-webhooks-for-apps\"></div>\n        <div class=\"heading-text\"><div id=\"change-in-the-availability-of-webhooks-for-apps\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Change in the availability of webhooks for apps</div>\n        <a aria-label=\"Skip link to Change in the availability of webhooks for apps\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#change-in-the-availability-of-webhooks-for-apps\"></a></h3>\n      \n    \n      <p><b>What is changing?</b></p>\n      <p>Apps that are creating, fetching, and deleting webhooks as a part of their functionality will start to only be able to see and delete webhooks that the app itself has created.  This means that starting from the change date, an app can see and delete only  webhooks that have the type set as <code>type='application'</code>. </p>\n        \n       <p> This is done to protect and maintain a separation of admin privileges to manage users' webhooks and applications' webhooks.</p>\n      \n      <p><b>Who is affected?</b></p>\n      <p> Every app that has functionality that relies on receiving any other type of webhooks besides  <code>'application'</code>, e.g. <code>'general'</code>.</p>\n          <br>\n      <p class=\"published-on\"><i>Published on April 5, 2021</i></p>\n  </div>\n</div>"
}
[/block]

Change in the availability of webhooks for apps

[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\">September 30, 2021</span>\n    </div>\n    <div class=\"change-area\">\n       <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n        <div class=\"heading-anchor anchor waypoint\" id=\"update-to-the-removal-of-the-search-api-endpoints\"></div>\n        <div class=\"heading-text\"><div id=\"update-to-the-removal-of-the-search-api-endpoints\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Update to the removal of the <code>/*/find</code>, <code>/searchResults</code>, and <code>/searchResults/field</code> endpoints</div>\n        <a aria-label=\"Skip link to Update to the removal of the /*/find, /searchResults, and /searchResults/field endpoints\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#update-to-the-removal-of-the-search-api-endpoints\"></a></h3>\n      \n         \n      <p>\n      In April last year we <a href=\"https://pipedrive.readme.io/docs/changelog#removal-of-the-/find-/searchresults-and-/searchresults/field-endpoints-replaced-by-6-new-endpoints\" target=\"_self\">announced</a> the deprecation and removal of the following 6 endpoints:</p>\n<ul>\n <li> <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealsByName\">GET /deals/find</a></code> - Searches all deals by their title</li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#getPersonByName\">GET /persons/find</a></code> - Searches all persons by their name</li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationByName\">GET /organizations/find</a></code> - Searches all organizations by their name</li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#getProductsByName\">GET /products/find</a></code> - Returns data about the products that were found.</li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/SearchResults#search\">GET /searchResults</a></code> - Searches all items or 1 item by all fields</li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/SearchResults#searchByField\">GET /searchResults/field</a></code> - searches 1 item type by 1 field</li>\n  </ul>\n<br>\n      <p>Based on the amount of requests we’re still receiving against the deprecated endpoints listed above, the original removal date at March 31, 2021 will be postponed to <b>September 30, 2021</b>.</p>\n\n<p>We strongly advise you to migrate your services and avoid the use of these 6 deprecated API endpoints.</p>\n\n\n\n<p>Continue reading  <a href=\"https://developers.pipedrive.com/changelog/post/removal-of-the-find-searchresults-and-searchresultsfield-endpoints-replaced-by-6-new-endpoints\" target=\"_self\">the original announcement</a> to learn more about the new Search API endpoints we suggest you to migrate to.</p>\n\n      <p><b>Who is affected?</b></p>\n\n<p>Anyone depending on the previously listed 6 deprecated endpoints in any way is affected. In case you are using the previously listed 6 deprecated API endpoints in your code or 3rd party app/integration, please remove any dependency on these endpoints as soon as possible, or by September 30, 2021 the latest. For additional help, check out <a href=\"https://pipedrive.readme.io/docs/new-search-api-migration-guide\">the new search API migration guide</a>.</p>     \n       <br>\n      <p class=\"published-on\"><i>Published on March 31, 2021</i></p>\n  </div>\n</div>"
}
[/block]

{"product": ["API"], "features": ["Deals", "Persons", "Organizations", "Products", "SearchResults"]}

[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\">September 30, 2021</span>\n    </div>\n    <div class=\"change-area\">\n       <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n        <div class=\"heading-anchor anchor waypoint\" id=\"update-to-the-removal-of-the-search-api-endpoints\"></div>\n        <div class=\"heading-text\"><div id=\"update-to-the-removal-of-the-search-api-endpoints\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Update to the removal of the <code>/*/find</code>, <code>/searchResults</code>, and <code>/searchResults/field</code> endpoints</div>\n        <a aria-label=\"Skip link to Update to the removal of the /*/find, /searchResults, and /searchResults/field endpoints\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#update-to-the-removal-of-the-search-api-endpoints\"></a></h3>\n      \n         \n      <p>\n      In April last year we <a href=\"/changelog/post/removal-of-the-/find-/searchresults-and-/searchresults/field-endpoints-replaced-by-6-new-endpoints\" target=\"_self\">announced</a> the deprecation and removal of the following 6 endpoints:</p>\n<ul>\n <li> <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealsByName\">GET /deals/find</a></code> - Searches all deals by their title</li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#getPersonByName\">GET /persons/find</a></code> - Searches all persons by their name</li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationByName\">GET /organizations/find</a></code> - Searches all organizations by their name</li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#getProductsByName\">GET /products/find</a></code> - Returns data about the products that were found.</li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/SearchResults#search\">GET /searchResults</a></code> - Searches all items or 1 item by all fields</li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/SearchResults#searchByField\">GET /searchResults/field</a></code> - searches 1 item type by 1 field</li>\n  </ul>\n<br>\n      <p>Based on the amount of requests we’re still receiving against the deprecated endpoints listed above, the original removal date at March 31, 2021 will be postponed to <b>September 30, 2021</b>.</p>\n\n<p>We strongly advise you to migrate your services and avoid the use of these 6 deprecated API endpoints.</p>\n\n\n\n<p>Continue reading  <a href=\"https://developers.pipedrive.com/changelog/post/removal-of-the-find-searchresults-and-searchresultsfield-endpoints-replaced-by-6-new-endpoints\" target=\"_self\">the original announcement</a> to learn more about the new Search API endpoints we suggest you to migrate to.</p>\n\n      <p><b>Who is affected?</b></p>\n\n<p>Anyone depending on the previously listed 6 deprecated endpoints in any way is affected. In case you are using the previously listed 6 deprecated API endpoints in your code or 3rd party app/integration, please remove any dependency on these endpoints as soon as possible, or by September 30, 2021 the latest. For additional help, check out <a href=\"https://pipedrive.readme.io/docs/new-search-api-migration-guide\">the new search API migration guide</a>.</p>     \n       <br>\n      <p class=\"published-on\"><i>Published on March 31, 2021</i></p>\n  </div>\n</div>"
}
[/block]

Update to the removal of the <code>/*/find</code>, <code>/searchResults</code>, and <code>/searchResults/field</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\">April 23, 2021</span>\n    </div>\n    <div class=\"change-area\">\n      <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n        <div class=\"heading-anchor anchor waypoint\" id=\"replacing-the-note-field-in-leads-api-with-fields-in-notes-api\"></div>\n        <div class=\"heading-text\"><div id=\"replacing-the-note-field-in-leads-api-with-fields-in-notes-api\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Replacing the <code>note</code> field in Leads API with fields in Notes API</div>\n        <a aria-label=\"Skip link to Replacing the note field in Leads API with fields in Notes API\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#replacing-the-note-field-in-leads-api-with-fields-in-notes-api\"></a></h3>\n      \n        \n      <p><b>  What is going to change?</b></p>\n      <p> We will remove the <code>note</code> field from the following Leads API endpoints:</p>\n<ul>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#getLeads\">GET /leads</a></code></li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#getLead\">GET /leads/{id}</a></code></li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#addLead\">POST /leads</a></code></li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#updateLead\">PATCH /leads/{id}</a></code></li>\n</ul>\n<p> And add <code>lead_id</code> and <code>pinned_to_lead_flag</code> fields to <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Notes#getNotes\">GET /notes</a></code> endpoint.</p>\n      <p> <b>Why is it going to change?</b></p>\n<p> Until recently, we only supported having a single note for a Lead. Now we are adding support for multiple Notes. In doing so, it requires to stop using the <code>note</code> property on a Lead (which is in 1:1 relation) and start using the Note entity. The Note entity can be then linked to a Lead and thus it will be in a 1:N Lead to Note relation.</p>\n      \n     <p>Until the grace time is over, we will create a Note object every time someone calls <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#addLead\">POST /leads</a></code> with a note parameter. We will return and update the FIRST Note linked to a Lead on a <code>GET</code> and <code>PATCH</code> call. Therefore when using our API before the grace time is over, the only change will be that in the background a Note object will be created.</p>\n\n      <p> The <code>note</code> field will be removed on April 23, 2021. The support for multiple Notes is effective immediately.\n</p>\n      \n       <br>\n      <p class=\"published-on\"><i>Published on March 23, 2021</i></p>\n  </div>\n</div>"
}
[/block]

{"product": ["API"], "features": ["Notes", "Leads"]}

Replacing the <code>note</code> field in Leads API with fields in Notes API

[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, 2021</span>\n    </div>\n    <div class=\"change-area\">\n      <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n      <div class=\"heading-anchor anchor waypoint\" id=\"11-deals-endpoints-to-return-two-new-fields\"></div>\n        <div class=\"heading-text\"><div id=\"11-deals-endpoints-to-return-two-new-fields\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>11 Deals endpoints to return two new fields</div>\n        <a aria-label=\"Skip link to 11 Deals endpoints to return two new fields\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#11-deals-endpoints-to-return-two-new-fields\"></a></h3>\n      \n      \n   \n      <p>  We have added two new fields to the responses of the following endpoints:</p>\n    <ul>\n      <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDeals\">GET /deals</a></code></li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDeal\">POST /deals</a></code></li>\n      <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDeal\">GET /deals/{id}</a></code></li>\n       <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal\">PUT /deals/{id}</a></code></li>\n      <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#mergeDeals\">PUT /deals/{id}/merge</a></code></li>\n      <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#duplicateDeal\">POST /deals/{id}/duplicate</a></code></li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#getOrganizationDeals\">GET /organizations/{id}/deals</a></code></li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#getPersonDeals\">GET /persons/{id}/deals</a></code></li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelineDeals\">GET /pipelines/{id}/deals</a></code></li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#getProductDeals\">GET /products/{id}/deals</a></code></li>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Stages#getStageDeals\">GET /stages/{id}/deals</a></code></li>\n\n      </ul>\n\n<p>The possible value of the two new fields <code>group_id</code> and <code>group_name</code> can both be <code>null</code> or</p>\n      <ul><li>an integer representing the group for <code>group_id</code></li>\n        <li>a string representing the group for <code>group_name</code></li></ul>\n\n      <p>These two fields are <code>read_only</code> and cannot be updated via Deals endpoints.</p>\n\n      \n              <br>\n      <p class=\"published-on\"><i>Published on March 18, 2021</i></p>\n  </div>\n</div>"
}
[/block]

{"product": ["API"], "features": ["Deals"]}

11 Deals endpoints to return two new fields

[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 29, 2021</span>\n    </div>\n    <div class=\"change-area\">\n      <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n       <div class=\"heading-anchor anchor waypoint\" id=\"change-in-value-types-for-radio-and-checkbox-group-blocks-in-embedded-app-actions\"></div>\n        <div class=\"heading-text\"><div id=\"change-in-value-types-for-radio-and-checkbox-group-blocks-in-embedded-app-actions\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Change in <code>value</code>  types for Radio and Checkbox Group Blocks in Embedded app actions</div>\n        <a aria-label=\"Skip link to Change in value  types for Radio and Checkbox Group Blocks in Embedded app actions\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#change-in-value-types-for-radio-and-checkbox-group-blocks-in-embedded-app-actions\"></a></h3>\n      \n         \n      <p>The <a href=\"https://pipedrive.readme.io/docs/embedded-actions-component-library#radio-group\" target=\"_self\">Radio Group Block</a> and <a href=\"https://pipedrive.readme.io/docs/embedded-actions-component-library#checkbox-group\" target=\"_self\">Checkbox Group Block</a> of <a href=\"https://pipedrive.readme.io/docs/app-extensions-embedded-actions\" target=\"_self\">Embedded app actions</a> will continue to support <b>only</b> <code>string</code> type for the <code>value</code> option in both Block level and <code>items</code> level. </p><div class=\"magic-block-parameters\">\n\t<div class=\"rdmd-table\"><div class=\"rdmd-table-inner\"><table><thead><tr><th style=\"text-align:left\">Block</th><th style=\"text-align:left\">Previously available types for value</th><th style=\"text-align:left\">Available type starting from March 29, 2021</th></tr></thead><tbody><tr><td style=\"text-align:left\">Radio Group Block</td><td style=\"text-align:left\">string or number</td><td style=\"text-align:left\">string</td></tr><tr><td style=\"text-align:left\">Checkbox Group Block</td><td style=\"text-align:left\">array of string, boolean or number</td><td style=\"text-align:left\">array of string</td></tr></tbody></table></div></div>\n        <br>\n      <p class=\"published-on\"><i>Published on March 10, 2021</i></p>\n  </div>\n</div>"
}
[/block]

{"product": ["App extensions"], "features": ["App actions"]}

Change in <code>value</code> types for Radio and Checkbox Group Blocks in Embedded app actions

[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 8, 2021</span>\n    </div>\n    <div class=\"change-area\">\n        <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n      <div class=\"heading-anchor anchor waypoint\" id=\"restoration-of-the-subscriptions-api\"></div>\n        <div class=\"heading-text\"><div id=\"restoration-of-the-subscriptions-api\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Restoration of the Subscription API</div>\n        <a aria-label=\"Skip link to Restoration of the Subscription API\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#restoration-of-the-subscriptions-api\"></a></h3>\n      \n         \n      <p>Regarding <a href=\"https://pipedrive.readme.io/docs/changelog#removal-of-the-subscriptions-api\" target=\"_self\">the recent Subscription API update</a>, after further user testing, our product team has found an alternative way to meet the needs of our customers around tracking and predicting the sales revenue. Thus, the Recurring Revenue and Payment Schedules functionalities along with <b>the Subscriptions API endpoints will not be removed</b> and will remain as the foundation of Pipedrive's revenue forecasting and tracking.</p> \n      <p>A related change to Subscriptions API <a href=\"https://pipedrive.readme.io/docs/changelog#new-field-in-deals-object\" target=\"_self\">announced on February 11, 2021</a> will not be reverted and will continue providing additional linking possibilities between Deals and Recurring Revenue feature.\n</p>\n      \n        <br>\n      <p class=\"published-on\"><i>Published on March 8, 2021</i></p>\n  </div>\n</div>"
}
[/block]

{"product": ["API"], "features": ["Subscriptions"]}

[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 8, 2021</span>\n    </div>\n    <div class=\"change-area\">\n        <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n      <div class=\"heading-anchor anchor waypoint\" id=\"restoration-of-the-subscriptions-api\"></div>\n        <div class=\"heading-text\"><div id=\"restoration-of-the-subscriptions-api\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Restoration of the Subscription API</div>\n        <a aria-label=\"Skip link to Restoration of the Subscription API\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#restoration-of-the-subscriptions-api\"></a></h3>\n      \n         \n      <p>Regarding <a href=\"/changelog/post/removal-of-the-subscriptions-api\" target=\"_self\">the recent Subscription API update</a>, after further user testing, our product team has found an alternative way to meet the needs of our customers around tracking and predicting the sales revenue. Thus, the Recurring Revenue and Payment Schedules functionalities along with <b>the Subscriptions API endpoints will not be removed</b> and will remain as the foundation of Pipedrive's revenue forecasting and tracking.</p> \n      <p>A related change to Subscriptions API <a href=\"/changelog/post/new-field-in-deals-object\" target=\"_self\">announced on February 11, 2021</a> will not be reverted and will continue providing additional linking possibilities between Deals and Recurring Revenue feature.\n</p>\n      \n        <br>\n      <p class=\"published-on\"><i>Published on March 8, 2021</i></p>\n  </div>\n</div>"
}
[/block]

Restoration of the Subscription API

[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 1, 2021</span>\n    </div>\n    <div class=\"change-area\">\n        <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n      <div class=\"heading-anchor anchor waypoint\" id=\"new-parameter-in-put-mailbox-mailthreads-id-endpoint\"></div>\n        <div class=\"heading-text\"><div id=\"new-parameter-in-put-mailbox-mailthreads-id-endpoint\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>New parameter in <code>PUT /mailbox/mailThreads/{id}</code> endpoint</div>\n        <a aria-label=\"Skip link to New parameter in PUT /mailbox/mailThreads/{id} endpoint\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#new-parameter-in-put-mailbox-mailthreads-id-endpoint\"></a></h3>\n      \n         \n      <p>We have added a new parameter <code>lead_id</code> to the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Mailbox#updateMailThreadDetails\" target=\"_self\">PUT /mailbox/mailThreads/{id}</a></code> endpoint. This parameter allows an email to be associated together with an existing lead.\n</p><p>\nPossible values for the parameter are the lead’s unique ID which references the lead, e.g. <code>dc775b7e-db49-444c-8a53-7ee785af1091</code> or <code>null</code>.</p>\n\n      <br>\n      <p class=\"published-on\"><i>Published on March 1, 2021</i></p>\n  </div>\n</div>"
}
[/block]

{"product": ["API"], "features": ["Mailbox"]}

New parameter in <code>PUT /mailbox/mailThreads/{id}</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\">February 18, 2021</span>\n    </div>\n    <div class=\"change-area\">\n       <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n      <div class=\"heading-anchor anchor waypoint\" id=\"new-parameter-in-post-callLogs-endpoint\"></div>\n        <div class=\"heading-text\"><div id=\"new-parameter-in-post-callLogs-endpoint\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>New parameter in <code>POST /callLogs</code> endpoint</div>\n        <a aria-label=\"Skip link to New parameter in POST /callLogs endpoint\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#new-parameter-in-post-callLogs-endpoint\"></a></h3>\n      \n      \n       \n      <p>We have added a new parameter <code>note</code> to the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLog\" target=\"_self\">POST /callLogs</a></code> endpoint.\n        The <code>note</code> parameter allows you to add notes to call logs.</p>\n      <br>\n      <p class=\"published-on\"><i>Published on February 18, 2021</i></p>\n  </div>\n</div>"
}
[/block]

{"product": ["API"], "features": ["CallLogs"]}

New 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\">March 16, 2021</span>\n    </div>\n    <div class=\"change-area\">\n        <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n      <div class=\"heading-anchor anchor waypoint\" id=\"removal-of-a-static-field-from-users-api-response\"></div>\n        <div class=\"heading-text\"><div id=\"removal-of-a-static-field-from-users-api-response\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Removal of a static field from Users API response</div>\n        <a aria-label=\"Skip link to Removal of a static field from Users API response\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#removal-of-a-static-field-from-users-api-response\"></a></h3>\n    \n      <p><b>What is going to change?</b></p>\n      <p>We will remove the field <code>activated</code> from the responses of the following Users API endpoints:\n</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1Users#getUsers\">GET /users</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#addUser\">POST /users</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#findUsersByName\">GET /users/find</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#getCurrentUser\">GET /users/me</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#getUser\">GET /users/{id}</a></code></li>\n       <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#updateUser\">PUT /users/{id}</a></code></li>\n      </ul>\n      \n       <p><b>Why is it going to change?</b></p>\n      <p>We are removing the <code>activated</code> field from these endpoints because the value of the field is static - it is always set to <code>true</code>.</p>\n      <br>\n      <p class=\"published-on\"><i>Published on February 16, 2021</i></p>\n  </div>\n</div>\n      "
}
[/block]

{"product": ["API"], "features": ["Users"]}

Removal of a static field from Users API response

[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 15, 2021</span>\n    </div>\n    <div class=\"change-area\">\n      <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n      <div class=\"heading-anchor anchor waypoint\" id=\"introducing-new-app-extensions-embedded-app-actions\"></div>\n        <div class=\"heading-text\"><div id=\"introducing-new-app-extensions-embedded-app-actions\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Introducing new app extensions - Embedded app actions</div>\n        <a aria-label=\"Skip link to Introducing new app extensions - Embedded app actions\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#introducing-new-app-extensions-embedded-app-actions\"></a></h3>\n     \n      <p>Embedded app actions are a new type of app extensions that allow apps to provide a way for users to complete actions right inside Pipedrive without them being redirected. These types of app extensions enable users to, for example, add contacts to email campaigns, send SMS messages, change the status of a document, create tasks in project management tools, etc., without leaving Pipedrive.</p>\n<p>\nEmbedded actions work by opening a modal window that can be customized with different <b>Blocks and Action buttons</b>. It can handle various types of user interactions, allowing to apply business and validation rules.\n</p>\n      \n      <p>To start developing Embedded app actions, see our guides on the overview of <a href=\"https://pipedrive.readme.io/docs/app-extensions-embedded-actions\" target=\"_self\">Embedded app actions</a>, <a href=\"https://pipedrive.readme.io/docs/embedded-actions-component-library\" target=\"_self\">Component library</a>, and <a href=\"https://pipedrive.readme.io/docs/embedded-actions-user-interaction-handling\" target=\"_self\">User interaction handling</a>.</p>\n      <br>\n      <p class=\"published-on\"><i>Published on February 15, 2021</i></p>\n  </div>\n</div>"
}
[/block]

Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog