[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">October 25, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      <p>Monetary discounts can now be added to the products attached to a deal, in addition to percentage discounts. The tax amount associated with a deal-product can now be specified as inclusive, exclusive, or none.</p>\n      \n      <h3><b>What is changing?</b></h3>\n      \n      <p>We have added 3 new body parameters to the POST and PUT deal-products endpoints:</p>\n      <ul>\n        <li><code>discount</code>- the value of the discount</li>\n        <li><code>discount_type</code>- the type of the discount's value (percentage or amount)</li>\n        <li><code>tax_method</code>- the tax option to be applied to the products (inclusive, exclusive or none)</li>\n      </ul>\n      \n      \n      <p>Similarly, the 3 fields have been added to the responses of the deal-products endpoints:</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts\" target=\"blank\">GET /deals/{id}/products</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"blank\">POST /deals/{id}/products</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"blank\">PUT /deals/{id}/products/{product_attachment_id}</a></code></li>\n      </ul>\n      <br>\n      <p>The existing <code>discount_percentage</code> parameter has been deprecated and will be removed from the 3 endpoints on <b>October 25, 2023</b>.</p>\n     \n      <h3><b>Why is it changing?</b></h3>\n      <p>With the new <code>discount</code> and <code>discount_type</code> fields being added to support both percentage and monetary discounts for products, the existing <code>discount_percentage</code> field no longer serves its purpose.</p>\n      \n      <p>If you have any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\" target=\"_self\">the Developers' Community</a>.</p>\n   \n      \n      </div>\n \n</div>\n      "
}
[/block]

Two new fields in Deals API enable adding monetary discounts to the products attached to a deal, in addition to previous percentage discounts. The existing <code>discount_percentage</code> field has therefore been deprecated and will be removed.

Update to the logic of product discounts

[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 21, 2023</span>\n    </div>\n    <div class=\"change-area\">\n     \n      <p>On June 29, 2022, we announced the <a href=\"https://developers.pipedrive.com/changelog/post/changes-in-filter-conditions-for-filters-api\" target=\"blank\">breaking changes in filter conditions for Filters API</a>. \nThe end date of the warning period has passed without the change going live for existing users prior to the initial announcement date. We want to apologize for any confusion or inconvenience this has caused. \n</p>\n      \n      <p>The changes to filter conditions will be implemented for all users between <b>August 21 and September 3, 2023</b>. All the details from the original announcement remain:</p>\n      \n      \n      <h3><b>What is changing?</b></h3>\n      <p>We will be implementing a limit to the number of conditions a filter can have via the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Filters#addFilter\" target=\"_self\">POST /filters</a></code> and <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Filters#updateFilter\" target=\"_self\">PUT /filters/{id}</a></code> endpoints.\n        The new limit will be <b>16 conditions per filter</b>.</p>\n      \n      <p>If a filter is being added or updated to include more than 16 conditions, the request will fail and a <code>400</code> error response, similar to this one, will be returned:</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\">false</span>,\n  <span class=\"cm-property\">\"error\"</span>: <span class=\"cm-string\">\"Filter is allowed to have at most 16 conditions\"</span>,\n  <span class=\"cm-property\">\"error_info\"</span>: <span class=\"cm-string\">\"Please check developers.pipedrive.com for more information about Pipedrive API.\"</span>,\n  <span class=\"cm-property\">\"data\"</span>: <span class=\"cm-atom\">null</span>,\n  <span class=\"cm-property\">\"additional_data\"</span>: <span class=\"cm-atom\">null</span>\n}\n</div></code></pre></div></div>\n      \n      <p>In addition to the limit, we have now deprecated and will soon stop supporting the following filter conditions from the <code>conditions</code> body parameter of \n        the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Filters#addFilter\" target=\"_self\">POST /filters</a></code> and <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Filters#updateFilter\" target=\"_self\">PUT /filters/{id}</a></code> endpoint:</p>\n      <ul>\n        <li><code>LIKE '%$'</code> <i>(ends with)</i></li>\n        <li><code>NOT LIKE '%$%'</code> <i>(does not contain)</i></li>\n        <li><code>NOT LIKE '%$'</code> <i>(does not end with)</i></li>\n      </ul>\n      \n      <p>We advise you to review the filters you have \n        created and make sure that they adhere to the changes.</p>\n        \n        <p><b>All existing filters with more than 16 conditions and/or the unsupported conditions will remain usable, but cannot be edited until they meet the above-mentioned requirements.</b></p>\n      \n      \n\t\t\t<h3><b>Why is it changing?</b></h3>\n      <p>Complex filters can easily cause system overload. As we are constantly improving our systems, \n        these limits will help to continuously support the performance \n        of our API to apps and users.</p>\n      \n     <p>If you have any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\" target=\"_self\">the Developers' Community</a>.</p>\n    </div>\n  \n  \n</div>\n\n"
}
[/block]

On June 29, 2022, we announced the breaking changes in filter conditions for Filters API. The end date of the warning period has passed without the change going live for existing users prior to the announcement date. We want to apologize for any confusion or inconvenience this has caused. We are announcing a new live date for this change.

Update to the breaking changes in filter conditions for Filters 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\">September 15, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <h2><b>What is changing?</b></h2>\n      \n      <p>From <b>September 15, 2023</b>, encrypted access tokens associated with <a href=\"https://pipedrive.readme.io/docs/marketplace-oauth-api\" target=\"blank\">OAuth 2.0</a> will be two times longer for improved security. We recommend using, at minimum, varchar(560) for storing the longer tokens in your app’s database.</p>\n      \n      <p><b>If your app uses encrypted access tokens, please check your app’s authentication logic to allocate enough space for storing the tokens.</b></p>\n      \n      <p>We will support old decryption until we are sure that all tokens are refreshed and use the new encryption.</p>\n      \n      <p>If you have any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">our Developers' Community</a>.</p>\n      </div>\n</div>"
}
[/block]

The encrypted access tokens for OAuth 2.0 will be two times longer from September 15, 2023 for improved security.

Improved security for access tokens related to OAuth 2.0

[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 4, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <h2><b>What is changing?</b></h2>\n      <p>Related to the announcement of <a href=\"https://developers.pipedrive.com/changelog/post/introducing-item-specific-create-and-update-permissions\" target=\"blank\">Introducing item-specific create and update permissions</a>, \n        we will be modifying the edit permission for Products API to make the behavior consistent \n        with deals, leads, organizations and persons entities.</p>\n      \n      <p><b>1. Introducing the <code>can_edit_other_users_products</code> field</b></p>\n      <p>Users can be restricted from editing other users’ products to ensure data reliability and quality for your Pipedrive account. Please note that the products owned by the user themselves will always remain editable.</p>\n\n      <p>The <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#getUserPermissions\" target=\"blank\">GET /users/{id}/permissions</a></code> endpoint will include a new response field \n        <code>can_edit_other_users_products</code> to indicate whether the user is allowed to edit other users’ products. \n        We will roll the new permission field out to all companies on September 4.</p>\n      \n      <p>If the user does not have permission to edit other users’ products, \n        calling the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#updateProduct\" target=\"blank\">PUT /products/{id}</a></code> endpoint will result in a 403 error.</p>\n      \n      <p><b>2. Removing the existing <code>can_edit_products</code> field</b></p>\n      <p>The current permission field for editing products - the can_edit_products field - will be removed from the response of \n        the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#getUserPermissions\" target=\"blank\">GET /users/{id}/permissions</a></code> endpoint on September 4, 2023.</p>\n     \n      <p><b>Please check your API consumption logic and start using the new response field to check for the user’s products editing permission.</b></p>\n      <br>\n      <h2><b>Where can I find the permissions for a user?</b></h2>\n      <p>The <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#getUserPermissions\" target=\"blank\">GET /users/{id}/permissions</a></code> endpoint can be used to find a specific user’s permissions.</p>\n      \n     <p>If you have any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">our Developers' Community</a>.</p>\n      \n   \n      </div>\n</div>"
}
[/block]

We are introducing a new response field and removing the existing one related to the permission for editing other users' products for the <code>GET /users/{id}/permissions</code> endpoint.

Update to the edit permission for Products 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\">August 22, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <p><b>What is being removed?</b></p>\n      <p>The <code>sum_no_discount</code> response field will be removed from 3 deal-products endpoints on <b>August 22, 2023</b>:</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts\" target=\"blank\">GET /deals/{id}/products</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"blank\">POST /deals/{id}/products</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"blank\">PUT /deals/{id}/products/{product_attachment_id}</a></code></li>\n      </ul>\n      \n      <br>\n      <p><b>Why is it changing?</b></p>\n      \n      <p>The <code>sum_no_discount</code> response field is an obsolete legacy field, which we are removing to ensure that the 3 deal-products endpoints return only the most relevant fields.</p>\n      <p>If you have any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">our Developers' Community</a>.</p>\n      \n      </div>\n</div>"
}
[/block]

We are going to be removing an obsolete response field from 3 deal-products endpoints.

Removal of the <code>sum_no_discount</code> response field from 3 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\">June 22, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <h3><b>What is being added?</b></h3>\n      \n      <p>We are adding the delete permission as part of the <a href=\"https://support.pipedrive.com/en/article/permission-sets\" target=\"blank\">Permission sets feature</a> to the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#deleteLead\" target=\"blank\">DELETE /leads/{id}</a></code> endpoint.</p>\n      \n      <p>We will roll the permission out to all companies between June 26 and July 20, 2023.</p>\n      \n      <b><p>By default, nothing will be changed in the API behavior.</p></b>\n      \n      <p>Users can now be restricted from deleting existing leads, similarly to already existing delete permissions for activities, deals, organizations, persons, and products.</p>\n      \n      <p>If the user does not have the <code>can_delete_leads</code> permission, calling the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#deleteLead\" target=\"blank\">DELETE /leads/{id}</a></code> endpoint will result in a <code>403</code> error.</p>\n      \n      <br>\n      <b><h3>Where can I find the permissions for a user?</h3></b>\n    \n      <p>The <code>can_delete_leads</code> permission field will be added to the response of the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#getUserPermissions\" target=\"blank\">GET /users/{id}/permissions</a></code> endpoint, which can be used to find a specific user’s permissions.</p>\n      \n      <p>If you have any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">our Developers' Community</a>.</p>\n      \n   \n      </div>\n</div>"
}
[/block]

We are going to be adding the delete permission to the <code>DELETE /leads/{id}</code> endpoint, so users can be restricted from deleting leads.

Introducing the delete permission for Leads 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\">June 21, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      \n      <p>We are introducing 2 new types of permissions as part of the <a href=\"https://support.pipedrive.com/en/article/permission-sets\" target=\"blank\">Permission sets feature</a> in our web app and API:</p>\n      <ul>\n        <li>Permissions for adding items</li>\n        <li>Permissions for editing another user’s items</li>\n      </ul>\n      \n      <p>Users can now be restricted from creating new and/or editing existing other users’ entities (deals, leads, persons and organizations). This ensures data reliability and quality for your Pipedrive account.</p>\n      \n      <b><h2>What is being added?</h2></b>\n      \n      <p>We will roll the feature out to all companies between June 26 and July 20, 2023.</p>\n      <b><p>By default, nothing will be changed in the API behavior.</p></b>\n      \n      <p>When a user’s permission for creating entities (e.g., the <code>can_add_deals</code> permission for deals) is disabled, the user will not be able to add new deals, leads, persons and/or organizations via the API. Similarly, the user will not be able to edit other users’ entities when the editing permission is disabled. The deals, leads, persons and organizations that are owned by the user themselves will always remain editable.</p>\n      <br>\n      <b><p>1. Permissions for adding items</p></b>\n      \n      <b><p>Deals API</p></b>\n      <p>If the user does not have the <code>can_add_deals</code> permission, calling the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDeal\" target=\"blank\">POST /deals</a></code> and/or <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#duplicateDeal\" target=\"blank\">POST /deals/{id}/duplicate</a></code> endpoints will result in a <code>403</code> error.</p>\n      \n      <b><p>Leads API</p></b>\n      <p>If the user does not have the <code>can_add_leads</code> permission, calling the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#addLead\" target=\"blank\">POST /leads</a></code> endpoint will result in a <code>403</code> error.</p>\n      \n      <b><p>Organizations API</p></b>\n      <p>If the user does not have the <code>can_add_organizations</code> permission, calling the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization\" target=\"blank\">POST /organizations</a></code> endpoint will result in a <code>403</code> error.</p>\n      \n      <b><p>Persons API</p></b>\n      <p>If the user does not have the <code>can_add_people</code> permission, calling the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#addPerson\" target=\"blank\">POST /persons</a></code> endpoint will result in a <code>403</code> error.</p>\n      <br>\n      <b><p>2. Permissions for editing another user’s items</p></b>\n      \n      <b><p>Deals API</p></b>\n      <p>If the user does not have the <code>can_edit_other_users_deals</code> permission, calling the following endpoints will result in a <code>403</code> error:</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealParticipant\" target=\"blank\">POST /deals/{id}/participants</a></code></li>\n         <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\" target=\"blank\">POST /deals/{id}/products</a></code></li>\n         <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal\" target=\"blank\">PUT /deals/{id}</a></code></li>\n         <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\" target=\"blank\">PUT /deals/{id}/products/{product_id}</a></code></li>\n         <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#deleteDealParticipant\" target=\"blank\">DELETE /deals/{id}/participants/{deal_participant_id}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#deleteDealProduct\" target=\"blank\">DELETE /deals/{id}/products/{product_attachment_id}</a></code></li>\n      </ul>\n      \n      \n      <b><p>Leads API</p></b>\n      <p>If the user does not have the <code>can_edit_other_users_leads</code> permission, calling the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#updateLead\" target=\"blank\">PATCH /leads/{id}</a></code> endpoint will result in a <code>403</code> error.</p>\n      \n      <b><p>Organizations API</p></b>\n      <p>If the user does not have the <code>can_edit_other_users_organizations</code> permission, calling the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#updateOrganization\" target=\"blank\">PUT /organizations/{id}</a></code> endpoint will result in a <code>403</code> error.</p>\n      \n      <b><p>Persons API</p></b>\n      <p>If the user does not have the <code>can_edit_other_users_people</code> permission, calling the following endpoints will result in a <code>403</code> error:</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#addPersonPicture\" target=\"blank\">POST /persons/{id}/picture</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#updatePerson\" target=\"blank\">PUT /persons/{id}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#deletePersonPicture\" target=\"blank\">DELETE /persons/{id}/picture</a></code></li>\n      </ul>\n      \n      <br>\n      <b><p>Here’s an example <code>403</code> error response for both types of permissions:</p></b>\n      <div class=\"CodeTabs CodeTabs_initial theme-undefined\"><div class=\"CodeTabs-toolbar\"><button type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"JSON\"><div class=\"cm-s-neo\">{ \n  <span class=\"cm-property\">\"success\"</span>: <span class=\"cm-atom\">false</span>, \n  <span class=\"cm-property\">\"error\"</span>: <span class=\"cm-string\">\"You do not have permission to do this.\"</span>, \n  <span class=\"cm-property\">\"error_info\"</span>: <span class=\"cm-string\">\"Please check developers.pipedrive.com for more information about Pipedrive API.\"</span>, \n  <span class=\"cm-property\">\"data\"</span>: <span class=\"cm-atom\">null</span>, \n  <span class=\"cm-property\">\"additional_data\"</span>: <span class=\"cm-atom\">null</span> \n}\n\n</div></code></pre></div></div>\n      \n      \n      <br>\n      <b><h2>Where can I find the permissions for a user?</h2></b>\n    \n      <p>We will be adding all of the above mentioned permission fields to the response of the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Users#getUserPermissions\" target=\"blank\">GET /users/{id}/permissions</a></code> endpoint, which can be used to find a specific user’s permissions.</p>\n      \n      <p>If you have any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">our Developers' Community</a>.</p>\n      \n      \n      <code><a href=\"xx\" target=\"blank\"></a></code>\n      \n      \n\n      \n      \n      </div>\n</div>"
}
[/block]

We are introducing 2 new types of permissions as part of the Permission sets feature to be able to restrict or allow users from creating new and/or editing other users’ deals, leads, persons and organizations.

Introducing item-specific create and update permissions

[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 26, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <b><p>What is changing?</p></b>\n      <p>We are making an important security update to our SSL configuration, which will take effect on <b>June 26, 2023</b>. </p>\n      \n      <p>We will be disabling weak ciphers and allowing only the following ciphers:</p>\n      <p>TLS 1.2:</p>\n      <ul>\n        <li>TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256</li>\n        <li>TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 </li>\n        <li>TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 </li>\n        <li>TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256</li>\n        <li>TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256</li>\n        <li>TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384</li>\n      </ul>\n      \n      <p>TLS 1.3:</p>\n      <ul>\n        <li>TLS_AES_128_GCM_SHA256</li>\n        <li>TLS_AES_256_GCM_SHA384</li>\n        <li>TLS_CHACHA20_POLY1305_SHA256</li>\n      </ul>\n      \n      \n      \n     </br>\n      <b><p>Why is it changing?</p></b>\n      <p>The update to our SSL configuration is necessary to ensure the security of our systems and data. Please check and update your systems accordingly.</p>\n      <p>If you have any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">our Developers' Community</a>.</p>\n\t\t\t\n</div>\n</div>"
}
[/block]

We are making an important security update to our SSL configuration, where weak ciphers will be disabled.

Important security update for SSL configuration

[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, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <b><p>What is changing?</p></b>\n      <p>We have released a new major version candidate for <a href=\"https://github.com/pipedrive/client-php\" target=\"blank\">Pipedrive’s API client for PHP</a>. </p>\n      <p>The new and improved version for the client includes:\n      <ul>\n        <li>Leads API support</li>\n        <li>Fixes to deprecation notices</li>\n        <li>Automatic updates from the API Reference</li>\n      </ul></p>\n     \n      <p>You can refer to <a href=\"https://github.com/pipedrive/client-php/blob/5.0.0-beta.0/README.md\" target=\"blank\">the readme section</a> and <a href=\"https://github.com/pipedrive/client-php/blob/5.0.0-beta.0/MIGRATION-5.x.md\" target=\"blank\">the migration guide</a> for supportive material on migrating to the new major version.</p>\n      \n     </br>\n      <b><p>When is this being released?</p></b>\n      <p>The new version will be released as stable on <b>August 15, 2023</b>. In the meantime, the new version has been released as a version candidate.</p>\n      <p>Please let us know if you have any questions or feedback in <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">the Developer’s Community</a>.</p>\n\t\t\t\n</div>\n</div>"
}
[/block]

A new major version candidate for Pipedrive’s API client for PHP will be released as stable on August 15, 2023.

Major upgrade for the PHP client

[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 9, 2023</span>\n    </div>\n    <div class=\"change-area\">\n\t\t\t<p>To ensure a smooth and stable experience for your app’s users, we’ve enhanced the app updating process for publicly available apps in Developer Hub.</p>\n\t\t\t<p><img src=\"https://files.readme.io/dca6901-small-Developer_Hub_-_approved_app_-_merge_changes_-_three-dot_menu.png\"></img></p>    \n    \t<p>When you change/edit <a href=\"https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app#critical-and-non-critical-fields\" target=\"blank\">critical fields</a>, a private copy of your app will be created to ensure continuous stability for your app’s customers. These changes must then go through the approval process to ensure everything works correctly.</p>\n  \t\t<p>Get all the details in our documentation about <a href=\"https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app\" target=\"blank\">updating approved apps</a>.</p>\n      </div>\n</div>"
}
[/block]

To ensure a smooth and stable experience for your app's users, we've enhanced the process of updating your app in Developer Hub.

Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog