[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 24, 2019</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=\"websocket-functionality-deprecation\"></div>\n        <div class=\"heading-text\"><div id=\"websocket-functionality-deprecation\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Websocket functionality deprecation </div>\n        <a aria-label=\"Skip link to Websocket functionality deprecation \" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#websocket-functionality-deprecation\"></a></h3>\n\n       <p>We are going to deprecate the websocket usage in client-nodejs for third-party developers <a href=\"https://github.com/pipedrive/client-nodejs/pull/94\">https://github.com/pipedrive/client-nodejs/pull/94</a>.</p>  \n      <p>The current library will stop working on September 24, 2019. In case of any dependency affected by this deprecation, please keep in mind this is <b>a breaking change</b>. It is very urgent for you to update your library and migrate to using webhooks.</p>\n     \n       <p class=\"published-on\"><i>Published on July 30, 2019</i></p>\n    </div>\n</div>"
}
[/block]

{"product": ["Developer Platform"], "features": ["SDK"]}

Websocket functionality 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\">August 15, 2019</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-how-future-activities-behave\"></div>\n        <div class=\"heading-text\"><div id=\"change-in-how-future-activities-behave\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Change in how future Activities behave</div>\n        <a aria-label=\"Skip link to Change in how future Activities behave\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#change-in-how-future-activities-behave\"></a></h3>\n   \n       \n      <p>\n        Endpoints directly affected: </p>\n      <ul>\n<li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Activities/put_activities_id\" target=\"_self\">PUT /activities/{id}</code></a></li><li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Activities/get_activities\" target=\"_self\">GET /activities</code></a></li></ul>\n            <br>\n      <p><b>What will change?</b></p>\n<p>Currently, if future activities (<code>due_date</code> and <code>due_time</code> in the future) have been marked as done, those activities’ <code>due_date</code> and <code>due_time</code> have been overwritten with the <code>marked_as_done_time</code>. This behaviour will be changed.\nStarting from August 15, the <code>due_date</code> and <code>due_time</code> will remain as they were initially set, different from the <code>marked_as_done_time</code>.</p>\n\n<p><b>Why?</b></p>\n<p>We are working on improving Pipedrive’s integrations with external calendars and this is a necessary change. Overall, this was an unexpected behaviour and we are bringing it into line with how calendars usually behave.</p>\n\n<p><b>Who is affected?</b></p>\n<p>Anyone creating statistics based on activities.<br>\nAnyone marking future activities as done.<br>\n  <br>\nIf there is functionality built on top of the previous behaviour, it will have to be altered.</p>\n      <p class=\"published-on\"><i>Published on July 15, 2019</i></p>\n    </div>\n</div>"
}
[/block]

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

Change in how future Activities behave

[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>July 5, 2019</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=\"breaking-change-in-put-activities-id-endpoint\"></div>\n        <div class=\"heading-text\"><div id=\"breaking-change-in-put-activities-id-endpoint\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Breaking change in <code>PUT /activities/{id}</code> endpoint</div>\n        <a aria-label=\"Skip link to Breaking change in PUT /activities/{id} endpoint \" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#breaking-change-in-put-activities-id-endpoint\"></a></h3>\n\n      \n       <p>There will be a breaking change for the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Activities/put_activities_id\">PUT /activities/{id}</a></code> endpoint.</p>\n      \n      <p>Starting July 5th, in order to reconcile with other item <code>PUT</code> endpoints of our API, the endpoint will start directing to the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Activities/delete_activities_id\">DELETE /activities/{id}</a></code> endpoint when performing a soft delete by changing <code>active_flag: 0</code>.</p>\n      \n     \n       <p class=\"published-on\"><i>Published on June 25, 2019</i></p>\n    </div>\n</div>"
}
[/block]

Breaking change in <code>PUT /activities/{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\">July 1, 2019</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=\"akamai-wap-implementation\"></div>\n        <div class=\"heading-text\"><div id=\"akamai-wap-implementation\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Akamai WAP implementation</div>\n        <a aria-label=\"Skip link to Akamai WAP implementation\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#akamai-wap-implementation\"></a></h3>\n\n       <p>In order to provide a more secure service to our customers, Pipedrive is in the process of implementing Akamai WAP (Web Application Protector). The implementation of this tool ensures that malicious requests will be blocked.  </p>\n      <p><b> Why are we telling you this?</b> </p> \n      <p>In the implementation phase we are eliminating all false positives from the system to ensure that legitimate requests will not be blocked. If you happen to notice that your request is blocked and receives <b>403 error</b>, please contact us and we can investigate why this occurred. </p>\n      \n     \n       <p class=\"published-on\"><i>Published on June 17, 2019</i></p>\n    </div>\n</div>"
}
[/block]

Akamai WAP implementation

[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 4, 2019</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-endpoint-in-filters-resource\"></div>\n        <div class=\"heading-text\"><div id=\"new-endpoint-in-filters-resource\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>New endpoint in Filters resource</div>\n        <a aria-label=\"Skip link to New endpoint in Filters resource\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#new-endpoint-in-filters-resource\"></a></h3>\n      \n        \n \n      <p>We have added a new <code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Filters/get_filters_helpers\">GET /filters/helpers</a></code> endpoint to the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Filters\">Filters</code> </a></code>resource.</p>\n        <p>The new endpoint allows you to see the all the possible operators and their meanings for creating <code>conditions</code> in order to either add or update a <code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Filters/post_filters\">Filter</code></a>. \n<a href=\"https://pipedrive.readme.io/docs/adding-a-filter\">Here is a tutorial</a> showing how to add a new Filter using the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Filters/get_filters_helpers\">GET /filters/helpers</a></code> endpoint.</p>\n  <p class=\"published-on\"><i>Published on June 4, 2019</i></p>\n    </div>\n</div>"
}
[/block]

New endpoint in Filters resource

[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 30, 2019</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-endpoint-in-deals-resource\"></div>\n        <div class=\"heading-text\"><div id=\"new-endpoint-in-deals-resource\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>New endpoint in Deals resource</div>\n        <a aria-label=\"Skip link to New endpoint in Deals resource\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#new-endpoint-in-deals-resource\"></a></h3>\n      \n       <p>We have added a new <code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Deals/get_deals_summary\">GET /deals/summary</a></code> endpoint to <code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Deals\">Deals</code> </a></code>resource.</p>\n        <p>\nThe new endpoint allows you to see the summary of all the Deals in one company. You can customize the response of the summary with the following parameters: <code>status</code>, <code>filter_id</code>, <code>user_id</code>, <code>stage_id</code>. Here is an example of one company's Deals summary without specifying any parameters:</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-property\">\"success\"</span>: <span class=\"cm-atom\">true</span>,\n  <span class=\"cm-property\">\"data\"</span>: {\n    <span class=\"cm-property\">\"values_total\"</span>: {\n      <span class=\"cm-property\">\"USD\"</span>: {\n        <span class=\"cm-property\">\"value\"</span>: <span class=\"cm-number\">201.99</span>,\n        <span class=\"cm-property\">\"count\"</span>: <span class=\"cm-number\">91</span>,\n        <span class=\"cm-property\">\"value_converted\"</span>: <span class=\"cm-number\">201.99</span>,\n        <span class=\"cm-property\">\"value_formatted\"</span>: <span class=\"cm-string\">\"201,99 $\"</span>,\n        <span class=\"cm-property\">\"value_converted_formatted\"</span>: <span class=\"cm-string\">\"201,99 $\"</span>\n      }\n    },\n    <span class=\"cm-property\">\"weighted_values_total\"</span>: {\n      <span class=\"cm-property\">\"USD\"</span>: {\n        <span class=\"cm-property\">\"value\"</span>: <span class=\"cm-number\">201.99</span>,\n        <span class=\"cm-property\">\"count\"</span>: <span class=\"cm-number\">91</span>,\n        <span class=\"cm-property\">\"value_formatted\"</span>: <span class=\"cm-string\">\"201,99 $\"</span>\n      }\n    },\n    <span class=\"cm-property\">\"total_count\"</span>: <span class=\"cm-number\">91</span>,\n    <span class=\"cm-property\">\"total_currency_converted_value\"</span>: <span class=\"cm-number\">201.99</span>,\n    <span class=\"cm-property\">\"total_weighted_currency_converted_value\"</span>: <span class=\"cm-number\">201.99</span>,\n    <span class=\"cm-property\">\"total_currency_converted_value_formatted\"</span>: <span class=\"cm-string\">\"201,99 $\"</span>,\n    <span class=\"cm-property\">\"total_weighted_currency_converted_value_formatted\"</span>: <span class=\"cm-string\">\"201,99 $\"</span>\n  }\n}\n</div></code></pre></div></div>\n\n        <p class=\"published-on\"><i>Published on May 30, 2019</i></p>\n    </div>\n</div>\n"
}
[/block]

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

New endpoint in Deals resource

[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 25, 2019<</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=\"daily-api-limit-for-postput-endpoints\"></div>\n        <div class=\"heading-text\"><div id=\"daily-api-limit-for-postput-endpoints\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Daily API limit for <code>POST</code>/<code>PUT</code> endpoints</div>\n        <a aria-label=\"Skip link to Daily API limit for POST/PUT endpoints\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#daily-api-limit-for-postput-endpoints\"></a></h3>\n       \n       <p>\nWe're introducing a daily API fair usage limit for <code>POST</code>/<code>PUT</code> endpoints. We consider fair usage to be <b>a maximum of 10 000 <code>POST</code>/<code>PUT</code> requests daily per user per 24 hours</b>. The daily limit will be reset at midnight in UTC.</p>\n\n<p>In the case of exceeding the 10 000 daily limit on multiple occasions, we may start blocking your <code>POST</code>/<code>PUT</code> requests towards our API.</p>\n<p>\n  The daily limit is introduced in addition to <a href=\"https://pipedrive.readme.io/docs/core-api-concepts-rate-limiting\">the rate limiting</a> and will apply to all <code>POST</code>/<code>PUT</code> endpoints provided by our <a href=\"https://developers.pipedrive.com/docs/api/v1/\">API</a>.</p>\n       <p><b> Example use-case</b></p>\n\n<p>Martin is a user of Pipedrive. He has </p>\n<ul>\n<li>installed two apps from the Pipedrive Marketplace</li>\n  <li>built two custom integrations using the Pipedrive API</li></ul>\n<p>Both apps and custom integrations are a subject to the same daily limit to make requests against the Pipedrive API on behalf of the user, Martin. </p>\n       <p>So for example, if one of those installed apps is making 350 <code>POST</code> requests per day and two of the integrations 100 <code>PUT</code> requests each per day, then there's <strong>10000 - 350 - 100 - 100 = 9450 </strong> <code>POST</code>/<code>PUT</code> requests left for those two apps and two integrations to use for the remaining time until the reset.</p>\n\n\n <p>The daily fair usage limit of 10 000 <code>POST</code>/<code>PUT</code> requests will be the same for all three plans (Silver, Gold, Platinum). </p> \n\n <p>Introducing the daily API limit allows us to protect the system from data overload, to have more equal and higher performance distribution in order to handle your requests quicker.\n</p>\n        <p class=\"published-on\"><i>Published on May 24, 2019</i></p>\n    </div>\n</div>"
}
[/block]

{"product": ["API"], "features": ["Rate limiting"]}

Daily API limit for <code>POST</code>/<code>PUT</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 30, 2019</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=\"additional-change-in-email-and-phone-number-quantity-limit\"></div>\n        <div class=\"heading-text\"><div id=\"additional-change-in-email-and-phone-number-quantity-limit\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Additional change in email and phone number quantity limit</div>\n        <a aria-label=\"Skip link to Additional change in email and phone number quantity limit\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#additional-change-in-email-and-phone-number-quantity-limit\"></a></h3>\n  \n       <p><b>What will change?</b>\n        <br>\nThe number of emails and phone numbers a user can add to a <b><code>person</code> object</b> will be limited to <b>50 records each</b>. A user can add a maximum of <b>50 emails</b> and a maximum of <b>50 phone numbers</b> per <code>person</code>.</p>\n\n <p>When a <code>person</code> object has reached 50 emails or 50 phone numbers, the UI will no longer show the <b>“+ add more” button for this <code>person</code></b>. If a 3rd party developer sends more than 50 emails or phone numbers, they will receive an API error. This API error should help to prevent data loss for the customer.</p>\n      </p>\n <p><b>Why?</b>\n   <br>\nThis change comes in addition to the change announced on <a href=\"https://pipedrive.readme.io/docs/changelog#new-limit-for-importing-emails-and-phone-numbers\">May 7th</a> as 3rd party developers can still unknowingly abuse the API - for example, adding thousands of emails and/or phone numbers into one <code>person</code>. This happens regularly a few times per month and it adds a lot of real-time processing demands to our servers, causing slow webapp performance for all the companies that share the same server.</p>\n\n        <p class=\"published-on\"><i>Published on May 17, 2019</i></p>\n    </div>\n</div>\n"
}
[/block]

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

[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 30, 2019</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=\"additional-change-in-email-and-phone-number-quantity-limit\"></div>\n        <div class=\"heading-text\"><div id=\"additional-change-in-email-and-phone-number-quantity-limit\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Additional change in email and phone number quantity limit</div>\n        <a aria-label=\"Skip link to Additional change in email and phone number quantity limit\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#additional-change-in-email-and-phone-number-quantity-limit\"></a></h3>\n  \n       <p><b>What will change?</b>\n        <br>\nThe number of emails and phone numbers a user can add to a <b><code>person</code> object</b> will be limited to <b>50 records each</b>. A user can add a maximum of <b>50 emails</b> and a maximum of <b>50 phone numbers</b> per <code>person</code>.</p>\n\n <p>When a <code>person</code> object has reached 50 emails or 50 phone numbers, the UI will no longer show the <b>“+ add more” button for this <code>person</code></b>. If a 3rd party developer sends more than 50 emails or phone numbers, they will receive an API error. This API error should help to prevent data loss for the customer.</p>\n      </p>\n <p><b>Why?</b>\n   <br>\nThis change comes in addition to the change announced on <a href=\"/changelog/post/new-limit-for-importing-emails-and-phone-numbers\">May 7th</a> as 3rd party developers can still unknowingly abuse the API - for example, adding thousands of emails and/or phone numbers into one <code>person</code>. This happens regularly a few times per month and it adds a lot of real-time processing demands to our servers, causing slow webapp performance for all the companies that share the same server.</p>\n\n        <p class=\"published-on\"><i>Published on May 17, 2019</i></p>\n    </div>\n</div>\n"
}
[/block]

Additional change in email and phone number quantity limit

[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>May 9, 2019</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=\"adding-a-deal-bug-fix\"></div>\n        <div class=\"heading-text\"><div id=\"adding-a-deal-bug-fix\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>Adding a deal bug fix</div>\n        <a aria-label=\"Skip link to Adding a deal bug fix\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#adding-a-deal-bug-fix\"></a></h3>\n       \n      \n      <p>We identified an issue with <code><a href=\"https://developers.pipedrive.com/docs/api/v1/#!/Deals/post_deals\">POST /deals</a></code> endpoint. It was possible to add <code>last_activity_date</code> and <code>next_activity_date</code>  fields when adding a deal.</p>\n\n<p>This has been fixed, because these are values which will automatically be calculated based on the activities linked to the deal.</p>\n      \n<p>Please let us know if you have any questions by replying to the forum thread <a href=\"https://devcommunity.pipedrive.com/t/update-deal-details-using-api-not-working/1065/\">here</a>.</p>\n\n        <p class=\"published-on\"><i>Published on May 17, 2019</i></p>\n    </div>\n</div>"
}
[/block]

Adding a Deal bug fix

[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 7, 2019</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-limit-for-importing-emails-and-phone-numbers\"></div>\n        <div class=\"heading-text\"><div id=\"new-limit-for-importing-emails-and-phone-numbers\" class=\"heading-anchor_backwardsCompatibility\">\n          </div>New limit for importing emails and phone numbers</div>\n        <a aria-label=\"Skip link to New limit for importing emails and phone numbers\" class=\"heading-anchor-icon fa fa-anchor\" \n           href=\"#new-limit-for-importing-emails-and-phone-numbers\"></a></h3>\n      \n    \n      <p><b>What will change?</b>\n        <br>\nThe number of emails and phone numbers a user can add to a <b>“person” type object</b> will be limited to <b>150 records each</b>. A user can add a maximum of <b>150 emails</b> and a maximum of <b>150 phone numbers</b> per person.</p>\n\n <p>When a person object has reached 150 emails, their UI will no longer show the <b>“+ add more” button</b>. If a 3rd party developer sends more than 150 emails, they will receive an API error. This API error should help to prevent data loss for the customer.</p>\n<br>\n <p><b>Why?</b>\n   <br>\n3rd party developers can unknowingly abuse the API - for example, adding thousands of emails and/or phone numbers into one person happens regularly a few times per month. They usually clean up after themselves, but this still adds a lot of real-time processing demands to our servers.</p>\n<br>\n <p><b>Who is affected?</b>\n   <br>\nThe most obvious will be companies who already have too many emails or phone numbers per person, as they will no longer be able to add any more emails or phone numbers to their “person” type objects.\n      </p>\n\n        <p class=\"published-on\"><i>Published on May 7, 2019</i></p>\n    </div>\n</div>"
}
[/block]

Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog