[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 11, 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-field-in-deals-object\"></div>\n        <div class=\"heading-text\"><div id=\"new-field-in-deals-object\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>New field in Deals object</div>\n        <a aria-label=\"Skip link to New field in Deals object\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#new-field-in-deals-object\"></a></h3>\n      \n         \n      <p><b>What is going to change?</b></p>\n      \n      <p>A new field <code>renewal_type</code> will be added to the Deals object. This change affects all Deals endpoints which return the Deal object(s) in the response.</p>\n\n<p>The possible values for the <code>renewal_type</code> field are <code>one_time</code>, <code>renewal</code>, and <code>new_business</code>.</p>\n      <ul>\n        <li><code>one_time</code> - Deal is a one-time transaction, no repetition of business transactions is expected.</li>\n        <li><code>renewal</code> - the Deal is a new relationship with a new client. Such Deals will have renewals to prolong terms of agreement with customers. This Deal is a base/parent Deal for a group of Deals which will be the future renewals.\n</li>\n        <li><code>new_business</code> - the Deal is connected to the new business type of a Deal via a Deal group and is used by account management or customer success teams to keep track of upcoming prolongation of business relationships.\n</li>\n      </ul>\n      <p>For example, to renew the Deal only once, add the following:</p>\n      <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\"><button type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\"><pre><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\"><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><div class=\"cm-s-neo\">{\n   <span class=\"cm-meta\">...</span>\n   <span class=\"cm-string\">\"renewal_type\"</span>: <span class=\"cm-string\">\"one_time\"</span>,\n   <span class=\"cm-meta\">...</span>\n}\n</div></code></pre></div></div>\n      \n      <p><b>Why is it going to change?</b></p>\n      <p>This change is linked to our <a href=\"https://pipedrive.readme.io/docs/changelog#removal-of-the-subscriptions-api\" target=\"_self\"> previous announcement</a> about substituting the Recurring Revenue and Payment Schedule features with an up-and-coming feature called Renewal management. In order to make it work, we need to add a new Deals field <code>renewal_type</code>.</p>\n      <br>\n      <p class=\"published-on\"><i>Published on February 11, 2021</i></p>\n</div>\n</div>"
}
[/block]

{"product": ["API"], "features": ["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\">February 11, 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-field-in-deals-object\"></div>\n        <div class=\"heading-text\"><div id=\"new-field-in-deals-object\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>New field in Deals object</div>\n        <a aria-label=\"Skip link to New field in Deals object\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#new-field-in-deals-object\"></a></h3>\n      \n         \n      <p><b>What is going to change?</b></p>\n      \n      <p>A new field <code>renewal_type</code> will be added to the Deals object. This change affects all Deals endpoints which return the Deal object(s) in the response.</p>\n\n<p>The possible values for the <code>renewal_type</code> field are <code>one_time</code>, <code>renewal</code>, and <code>new_business</code>.</p>\n      <ul>\n        <li><code>one_time</code> - Deal is a one-time transaction, no repetition of business transactions is expected.</li>\n        <li><code>renewal</code> - the Deal is a new relationship with a new client. Such Deals will have renewals to prolong terms of agreement with customers. This Deal is a base/parent Deal for a group of Deals which will be the future renewals.\n</li>\n        <li><code>new_business</code> - the Deal is connected to the new business type of a Deal via a Deal group and is used by account management or customer success teams to keep track of upcoming prolongation of business relationships.\n</li>\n      </ul>\n      <p>For example, to renew the Deal only once, add the following:</p>\n      <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\"><button type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\"><pre><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\"><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><div class=\"cm-s-neo\">{\n   <span class=\"cm-meta\">...</span>\n   <span class=\"cm-string\">\"renewal_type\"</span>: <span class=\"cm-string\">\"one_time\"</span>,\n   <span class=\"cm-meta\">...</span>\n}\n</div></code></pre></div></div>\n      \n      <p><b>Why is it going to change?</b></p>\n      <p>This change is linked to our <a href=\"/changelog/post/removal-of-the-subscriptions-api\" target=\"_self\"> previous announcement</a> about substituting the Recurring Revenue and Payment Schedule features with an up-and-coming feature called Renewal management. In order to make it work, we need to add a new Deals field <code>renewal_type</code>.</p>\n      <br>\n      <p class=\"published-on\"><i>Published on February 11, 2021</i></p>\n</div>\n</div>"
}
[/block]

New field in Deals object

[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 12, 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-the-subscriptions-api\"></div>\n        <div class=\"heading-text\"><div id=\"removal-of-the-subscriptions-api\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Removal of the Subscriptions API</div>\n        <a aria-label=\"Skip link to Removal of the Subscriptions API\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#removal-of-the-subscriptions-api\"></a></h3>\n      \n        \n    <p><strong>UPDATE</strong>: After further testing, our team has found an alternative method and will NO LONGER be removing these endpoints. For detailed information see the full announcement <a href=\"https://pipedrive.readme.io/docs/changelog#restoration-of-the-subscriptions-api\" target=\"_self\">here</a>.</p>\n\n\n      <p>We have now deprecated and will soon be removing the following nine Subscriptions API endpoints:</p>\n\n<p><ul>\n          <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#getSubscription\">GET /subscriptions/{id}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#findSubscriptionByDeal\">GET /subscriptions/find/{dealId}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#getSubscriptionPayments\">GET /subscriptions/{id}/payments</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#addRecurringSubscription\">POST /subscriptions/recurring</a></code></li>\n       <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#addSubscriptionInstallment\">POST /subscriptions/installment</a></code></li>\n       <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#updateRecurringSubscription\">PUT /subscriptions/recurring/{id}</a></code></li>\n       <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#updateSubscriptionInstallment\">PUT /subscriptions/installment/{id}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#cancelRecurringSubscription\">PUT /subscriptions/recurring/{id}/cancel}</a></code></li>\n      <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#deleteSubscription\">DELETE /subscriptions/{id}</a></code></li>\n      </ul></p>\n<p>We strongly advise you to avoid the use of these 9 deprecated API endpoints.</p>\n\n   <p><b>What's going to change?</b></p>\n  <p>The <a href=\"https://www.pipedrive.com/en/features/recurring-revenue\" target=\"_self\">Recurring Revenue</a> and Payment Schedule features will be substituted with a new renewal deals functionality and therefore the previously mentioned features will no longer be available as a standalone functionality.</p>\n  \n  <p><b>Why?</b></p>\n  <p>We wish to deliver the best possible sales oriented approach. Having that in mind, we need to move the functionalities of the Recurring Revenue and the Payment Schedules closer to Deals and Pipeline processes to truly support sales success of Pipedrive users.\n</p>\n   <br>\n      <p class=\"published-on\"><i>Published on February 4, 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\">April 12, 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-the-subscriptions-api\"></div>\n        <div class=\"heading-text\"><div id=\"removal-of-the-subscriptions-api\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Removal of the Subscriptions API</div>\n        <a aria-label=\"Skip link to Removal of the Subscriptions API\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#removal-of-the-subscriptions-api\"></a></h3>\n      \n        \n    <p><strong>UPDATE</strong>: After further testing, our team has found an alternative method and will NO LONGER be removing these endpoints. For detailed information see the full announcement <a href=\"/changelog/post/restoration-of-the-subscriptions-api\" target=\"_self\">here</a>.</p>\n\n\n      <p>We have now deprecated and will soon be removing the following nine Subscriptions API endpoints:</p>\n\n<p><ul>\n          <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#getSubscription\">GET /subscriptions/{id}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#findSubscriptionByDeal\">GET /subscriptions/find/{dealId}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#getSubscriptionPayments\">GET /subscriptions/{id}/payments</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#addRecurringSubscription\">POST /subscriptions/recurring</a></code></li>\n       <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#addSubscriptionInstallment\">POST /subscriptions/installment</a></code></li>\n       <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#updateRecurringSubscription\">PUT /subscriptions/recurring/{id}</a></code></li>\n       <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#updateSubscriptionInstallment\">PUT /subscriptions/installment/{id}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#cancelRecurringSubscription\">PUT /subscriptions/recurring/{id}/cancel}</a></code></li>\n      <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Subscriptions#deleteSubscription\">DELETE /subscriptions/{id}</a></code></li>\n      </ul></p>\n<p>We strongly advise you to avoid the use of these 9 deprecated API endpoints.</p>\n\n   <p><b>What's going to change?</b></p>\n  <p>The <a href=\"https://www.pipedrive.com/en/features/recurring-revenue\" target=\"_self\">Recurring Revenue</a> and Payment Schedule features will be substituted with a new renewal deals functionality and therefore the previously mentioned features will no longer be available as a standalone functionality.</p>\n  \n  <p><b>Why?</b></p>\n  <p>We wish to deliver the best possible sales oriented approach. Having that in mind, we need to move the functionalities of the Recurring Revenue and the Payment Schedules closer to Deals and Pipeline processes to truly support sales success of Pipedrive users.\n</p>\n   <br>\n      <p class=\"published-on\"><i>Published on February 4, 2021</i></p>\n</div>\n</div>"
}
[/block]

Removal of the Subscriptions 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=\"change-in-behavior-of-4-bulk-delete-endpoints\"></div>\n        <div class=\"heading-text\"><div id=\"change-in-behavior-of-4-bulk-delete-endpoints\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Change in behavior of 4 bulk DELETE endpoints</div>\n        <a aria-label=\"Skip link to Change in behavior of 4 bulk DELETE endpoints\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#change-in-behavior-of-4-bulk-delete-endpoints\"></a></h3>\n      \n      \n         \n      <p><b>What will change?</b></p>\n      <p>Four Pipedrive API bulk <code>DELETE</code> endpoints will be limited to deleting up to 1000 items per request.\n</p>\n       <p>The requests made against the following four bulk <code>DELETE</code> endpoints will be serviced slower than before. The processing speed will be based on the number of items being deleted and the worst case scenario being at most <b>20 seconds for a request with 1000 items</b>.</p>\n       <p>The change affects the following four API endpoints:</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Activities#deleteActivities\">DELETE /activities</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#deleteDeals\">DELETE /deals</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#deleteOrganizations\">DELETE /organizations</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#deletePersons\">DELETE /persons</a></code></li>\n      </ul>\n      <br>\n      <p><b>Why?</b></p>\n       <p>We are making technical improvements in the backend to increase the reliability of features reacting to changes made to entities. Examples of those features include Workflow Automation and Webhooks. In the current state, in rare cases when performing large bulk deletes, a reaction could be lost.</p>\n       <p>The bulk deletes will be done asynchronously in the background by going through items 1 by 1. This will make it possible for all related features to react to changes in a reliable way.</p>\n      <p><b>Who is affected?</b></p>\n       <p>Anyone depending on the behavior of those previously listed four endpoints in any way is affected. In case you are using the four endpoints in your code or 3rd party app/integration, please make sure that you complete the following two steps as soon as possible (or by March 1, 2021 the latest):\n</p>\n      <ul>\n        <li> send the maximum of 1000 items at once</li>\n        <li> your code can handle the requests taking longer to finish\n</li>\n      </ul>\n\n      <br>\n      <p class=\"published-on\"><i>Published on January 29, 2021</i></p>\n</div>\n</div>"
}
[/block]

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

Change in behavior of 4 bulk DELETE 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\">January 27, 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=\"companydomain-to-replace-api-proxy-in-API-requests\"></div>\n        <div class=\"heading-text\"><div id=\"companydomain-to-replace-api-proxy-in-API-requests\" class=\"heading-anchor_backwardsCompatibility\">\n          </div><code>companydomain</code> to replace <code>api-proxy</code> in API requests</div>\n        <a aria-label=\"Skip link to companydomain to replace api-proxy in API requests\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#companydomain-to-replace-api-proxy-in-API-requests\"></a></h3>\n      \n         \n      <p><b>What?\n</b></p>\n      \n      <p> From now on, we’re <b>suggesting</b> you to use <code>https://companydomain.pipedrive.com/api/v1/</code> API domains for making requests to Pipedrive API. Read more about Pipedrive API URL naming convention <a href=\"https://pipedrive.readme.io/docs/core-api-concepts-requests#url-naming\" target=\"_self\">here</a>.</p>\n\n      <p><b>Why?</b></p>\n<p>This suggestion comes in addition to the change announced on <a href=\"https://pipedrive.readme.io/docs/changelog#new-parameter-in-oauth-/oauth/token/-responses\" target=\"_self\">Feb 21 last year</a> when we introduced a new parameter <code>api_domain</code> in OAuth 2.0 <code>/oauth/token</code> responses for our external developers to receive up-to-date <code>company_domain</code> and <code>api_domain</code> every time one makes the initial request to get the tokens or when one refreshes a token. Also, using the <code>companydomain</code> prefix should make your requests to our API faster.</p>\n<p class=\"published-on\"><i>Published on January 27, 2021</i></p>\n</div>\n</div>"
}
[/block]

[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 27, 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=\"companydomain-to-replace-api-proxy-in-API-requests\"></div>\n        <div class=\"heading-text\"><div id=\"companydomain-to-replace-api-proxy-in-API-requests\" class=\"heading-anchor_backwardsCompatibility\">\n          </div><code>companydomain</code> to replace <code>api-proxy</code> in API requests</div>\n        <a aria-label=\"Skip link to companydomain to replace api-proxy in API requests\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#companydomain-to-replace-api-proxy-in-API-requests\"></a></h3>\n      \n         \n      <p><b>What?\n</b></p>\n      \n      <p> From now on, we’re <b>suggesting</b> you to use <code>https://companydomain.pipedrive.com/api/v1/</code> API domains for making requests to Pipedrive API. Read more about Pipedrive API URL naming convention <a href=\"https://pipedrive.readme.io/docs/core-api-concepts-requests#url-naming\" target=\"_self\">here</a>.</p>\n\n      <p><b>Why?</b></p>\n<p>This suggestion comes in addition to the change announced on <a href=\"/changelog/post/new-parameter-in-oauth-/oauth/token/-responses\" target=\"_self\">Feb 21 last year</a> when we introduced a new parameter <code>api_domain</code> in OAuth 2.0 <code>/oauth/token</code> responses for our external developers to receive up-to-date <code>company_domain</code> and <code>api_domain</code> every time one makes the initial request to get the tokens or when one refreshes a token. Also, using the <code>companydomain</code> prefix should make your requests to our API faster.</p>\n<p class=\"published-on\"><i>Published on January 27, 2021</i></p>\n</div>\n</div>"
}
[/block]

<code>companydomain</code> to replace <code>api-proxy</code> in API requests

[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 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=\"new-parameters-in-app-actions-urls\"></div>\n        <div class=\"heading-text\"><div id=\"new-parameters-in-app-actions-urls\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>New parameters in App actions' URLs </div>\n        <a aria-label=\"Skip link to New parameters in App actions' URLs \" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#new-parameters-in-app-actions-urls\"></a></h3>\n      \n        \n      <p>App actions triggered from the Activity list view will now have additional parameters <code>activity_type</code>, <code>activity_start_date</code> and <code> activity_end_date</code> added to the URL of the action to describe a <b>filter</b> that has been applied to the selected activities. These parameters will be included in the <code>filter</code> parameter.</p>\n<p>The <code>activity_type</code> parameter will always be included in the URL for actions from the Activity list view,  <code>activity_start_date</code> and <code> activity_end_date</code> will be added only when they are selected by the user.</p>\n      <p>\n\n      For more information, see <a href=\"https://pipedrive.readme.io/docs/app-extensions-actions\">App actions' guide</a>.\n      </p>\n      \n          <p class=\"published-on\"><i>Published on January 15, 2021</i></p>\n    </div>\n</div>"
}
[/block]

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

New parameters in App actions' URLs

[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 12, 2021</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <h3 class=\"heading heading-3 header-scroll\" align=\"\">\n      <div class=\"heading-anchor anchor waypoint\" id=\"updates-to-goals-api\"></div>\n        <div class=\"heading-text\"><div id=\"updates-to-goals-api\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Updates to Goals API  </div>\n        <a aria-label=\"Skip link to Updates to Goals API \" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#updates-to-goals-api\"></a></h3>\n      \n         \n       <p>\n      We’re introducing three updates to our <a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Goals\">Goals API</a>:\n      </p>\n      <p>\n        1. There’s a new goal type -  <code>revenue_forecast</code>. This type of goal allows users to track their revenue forecast.</p>\n      <p>2. Goals don’t need to have an end date. You can set up infinite, open-ended goals by setting <code>end</code> to <code>null</code>.</p>\n        <p>3. <code>report_ids</code> array is now a part of the response of the Goals API. This array includes IDs of reports used in <a href=\"https://support.pipedrive.com/hc/en-us/articles/360001930658-Insights-feature\">the Insights feature</a> to highlight the goal’s progress over time. Every goal should have at least one report attached to it.</p>\n       <p class=\"published-on\"><i>Published on January 12, 2021</i></p>\n</div>\n</div>"
}
[/block]

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

Updates to Goals API

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\"><b>Effective from:</b></span><br>\n        <span class=\"from-date\"><b>January 7, 2021</b></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=\"phone-calls-integration-oauth-scope\"></div>\n        <div class=\"heading-text\"><div id=\"phone-calls-integration-oauth-scope\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Phone calls integration OAuth scope</div>\n        <a aria-label=\"Skip link to Phone calls integration OAuth scope \" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#phone-calls-integration-oauth-scope\"></a></h3>\n      \n     \n      <p><code><a href=\"https://developers.pipedrive.com/docs/api/v1/CallLogs\" target=\"_self\">CallLogs</a></code> endpoints have now been added to a new scope <b>Phone calls integration</b> which is available for OAuth apps. The scope will allow apps to enable advanced call integration features like logging call duration and other metadata and play call recordings inside Pipedrive.</p>\n\n<p>You can find the following endpoints of the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/CallLogs\" target=\"_self\">CallLogs</a></code> resource under this scope:</p>\n<p><ul>\n          <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLog\">POST /callLogs</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/CallLogs#deleteCallLog\">DELETE /callLogs/{id}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLogAudioFile\">POST /callLogs/{id}/recordings</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/CallLogs#getUserCallLogs\">GET /callLogs</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/CallLogs#getCallLog\">GET /callLogs/{id}</a></code></li>\n      </ul></p>\n<p>You can read more about the scopes and permission explanations <a href=\"https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations\">here</a>.</p> \n     <p>If you wish to update the scopes of an already approved or published app, be sure to <a href=\"https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app#changing-the-scopes\">learn how changing the scopes will affect your app's existing users</a>.</p>\n    \n       <p class=\"published-on\"><i>Published on January 7, 2021</i></p>\n    </div>\n</div>"
}
[/block]

{"product": ["Authorization"], "features": ["Scopes"]}

Phone calls integration OAuth scope

[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 6, 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=\"get-/itemsearch-now-supports-returning-leads\"></div>\n        <div class=\"heading-text\"><div id=\"get-/itemsearch-now-supports-returning-leads\" class=\"heading-anchor_backwardsCompatibility\">\n          </div><code>GET/itemSearch</code> now supports returning Leads</div>\n        <a aria-label=\"Skip link to GET/itemSearch now supports returning Leads\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#get-/itemsearch-now-supports-returning-leads\"></a></h3>\n      \n      \n        \n      <p><b>What will change?</b></p>\n       \n<p><code><a href=\"https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem\">GET /itemSearch</a></code> now supports returning <b>Leads</b> in <code>related_items</code> for Organizations and Persons that are linked to it. When the <code>search_for_related_items</code>for <code><a href=\"https://developers.pipedrive.com/docs/api/v1/ItemSearch#searchItem\">GET /itemSearch</a></code> is set to <code>true</code>, the response will include up to 100 newest related <b>Leads</b> in addition to up to a 100 <b>Deals</b> for each found Person and Organization.\n   \n</p>\n\n  <p class=\"published-on\"><i>Published on January 6, 2021</i></p>\n    </div>\n</div>\n      "
}
[/block]

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

<code>GET/itemSearch</code> now supports returning Leads

[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 4, 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=\"breaking change in get /files endpoint\"></div>\n        <div class=\"heading-text\"><div id=\"breaking change in get /files endpoint\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Breaking change in <code>GET /files</code> endpoint</div>\n        <a aria-label=\"Skip link to Breaking change in GET /fiels endpoint\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#breaking change in get /files endpoint\"></a></h3>\n      \n        \n      <p><b>What will change?</b></p>\n       \n<p>We are going to change the definition of the sort parameter of <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Files#getFiles\">GET /files</a></code> endpoint. We’re going to allow sorting by 2 columns only (<code>id</code>, <code>update_time</code>) and restrict sorting by more than 1 column at the same time (e.g. <code>field_name_1</code> ASC, <code>field_name_2</code> DESC won’t work anymore).</p>\n      <p><b>Why?</b></p>\n<p>We are optimising our sorting operations together with moving to a new service for files management.</p>\n      <p><b>Who is affected?</b></p>\n      <p>Anyone doing queries to <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Files#getFiles\">GET /files</a></code> using sorting by <code>file_type</code>.</p>\n\n  <p class=\"published-on\"><i>Published on December 17, 2020</i></p>\n    </div>\n</div>"
}
[/block]

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

Breaking change in <code>GET /files</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\">December 11, 2020</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=\"bug fix in date and datetime fields\"></div>\n        <div class=\"heading-text\"><div id=\"bug fix in date and datetime fields\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Bug fix in <code>date</code> and <code>datetime</code> fields</div>\n        <a aria-label=\"Skip link to Bug fix in date and datetime fields\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#bug fix in date and datetime fields\"></a></h3>\n\n      <p>There was an issue with <code>date</code> and <code>datetime</code> fields, which affected Deals, Persons, Organizations, Products and Activities resources. When filtering by <code>date</code> and/or <code>datetime</code> with the operators <code><</code>, <code>></code>, <code><=</code>, <code>>=</code> it might have returned rows with an empty date (<code>0000-00-00</code>) and/or empty datetime (<code>0000-00-00 00:00:00</code>). We made the server response more strict, which means that now when filtering the same way the rows with empty date will always be excluded.</p>\n        <p>The issue has now been fixed.</p>\n<p>Please let us know if you have any questions by replying to the forum thread <a href=\"https://devcommunity.pipedrive.com/t/bug-fix-in-date-and-datetime-fields/3517\">here</a>.</p>\n\n  <p class=\"published-on\"><i>Published on December 11, 2020</i></p>\n    </div>\n</div>"
}
[/block]

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

Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog