[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, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <p>On November 18, 2022, we announced a <a href=\"https://developers.pipedrive.com/changelog/post/breaking-change-in-codelabelcode-response-fields-data-type-for-deals\">breaking change in the <code>label</code> response field’s data type for Deals</a> with a 2-month warning period.</p>\n      <p>The initial end date of the grace period has passed without the change going live. We want to apologize for any confusion or inconvenience this may have caused. Our team has been working hard to ensure that the change is fully ready to be rolled out, and we strongly believe this will improve the capabilities of our platform in the long run.</p>\n      \n      <p>We are now excited to announce that from <b>March 29, 2023</b>, we will start the gradual rollout of this change.</p>\n      \n      <b><p>What is changing?</p></b>\n      \n      <p>All the technical details from the original announcement still apply:</p>\n      \n      <p>For deals, the data type of a label’s ID will be changed from <code>integer</code> to </code>string</code>:</p>\n      <ul>\n        <li>If the deal has a single label specified, it will be returned as a <code>string</code></li>\n        <li>If the deal has multiple labels specified, it will be returned as a comma-separated <code>string</code></li>\n      </ul>\n      \n      <p>The change affects the following deals-related 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#getDeal\">GET /deals/{id} </a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline\">GET /deals/timeline</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        <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#duplicateDeal\">POST /deals/{id}/duplicate</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      </ul>\n\n<p>Similarly, the data type of a label’s ID will be changed from <code>integer</code> to <code>string</code> in the response payload of the <code>deal</code> v1 webhook.</p>\n      \n      <p>For the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/DealFields#getDealFields\">GET /dealFields</a></code> and <code><a href=\"https://developers.pipedrive.com/docs/api/v1/DealFields#getDealField\">GET /dealFields/{id}</a></code> endpoints, the <code>field_type</code> associated with the <code>“key”: “label”</code> response object will be <code>set</code>, instead of the current <code>enum</code> type.</p>\n      \n      <p><b>Why is it changing?</b></p>\n      <p>We are changing the data type of a deal’s label response field from <code>integer</code> to <code>string</code> to support the functionality of having multiple labels in one deal, which will be introduced in our web app.</p>\n      \n      <p><b>Who will be affected?</b></p>\n      <p>Everyone using the specified endpoints to retrieve the labels of a deal.</p>\n      <p>If you have any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n     \n      </div>\n</div>"
}
[/block]

The previously announced breaking change in the data type of a deal’s <code>label</code> response field has been postponed. We apologize for any confusion or inconvenience this may have caused. We are now excited to announce a new start date for the gradual rollout of this change.

Update to the breaking change in <code>label</code> response field’s data type for 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\">March 3, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      <p>1. Leads API now supports querying for users that are allowed to access a lead via the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#getLeadUsers\" target=\"blank\">GET /leads/{id}/permittedUsers</a></code> endpoint.</p>\n      \n      <p>2. A new optional body parameter <code>duration_unit</code> can be used to specify the unit when editing a product’s duration. The following endpoints include the new parameter:</p>\n      <ul>\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      <p>3. We have removed the mistakenly documented pagination parameters <code>start</code> and <code>limit</code> from the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#getProductUsers\" target=\"blank\">GET /products/{id}/permittedUsers</a></code> endpoint.</p>\n      \n      <p>4. We have corrected the HTTP code for erroneous requests to be <code>404</code> for the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Leads#getLeads\" target=\"blank\">GET /leads</a></code> endpoint.</p>\n  \n  </div>\n</div>"
}
[/block]

The latest updates to our API Reference include a new <code>GET /leads/{id}/permittedUsers</code> endpoint, a new <code>duration_unit</code> parameter for POST and PUT deal-products, and a corrected error code and error messages for <code>GET /leads</code>.

February 2023 release notes

[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 1, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <b><p>What is changing?</p></b>\n      <p>From <b>May 1, 2023</b>, the <code>variations_enabled</code> field will be removed from the response of the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts\" target=\"blank\">GET /deals/{id}/products</a></code> endpoint.</p>\n      \n      <b><p>Why is it changing?</p></b>\n      <p>With the  <a href=\"https://support.pipedrive.com/en/article/can-i-have-one-product-in-different-price-variations\" target=\"blank\">Price variations feature</a> now enabled for all companies, the <code>variations_enabled</code> response field is always returned as <code>true</code>. Hence, it no longer serves its purpose.</p>\n      <p>If you have any feedback, please let us know in <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">the Developers’ Community</a>.</p>\n      \n      \n      </div>\n</div>"
}
[/block]

The <code>variations_enabled</code> field will be removed from the response of the <code>GET /deals/{id}/products</code> endpoint.

Removal of the <code>variations_enabled</code> response field from <code>GET /deals/{id}/products</code>

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">February 22, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We’re introducing webhooks version 2 (v2) to give you <b>more reliability and stability</b> and <b><code>lead</code> webhooks</b>!</p>      \n      <h3>What is new?</h3>\n\t\t\t<p>Built on a new technology platform, webhooks v2 is more reliable so there should be <b>no more duplicate or missing webhooks</b>. \n        In addition, you can now <b>create <code>lead</code> webhooks</b>.</p>\n      <p>Get all the details in our <a href=\"https://pipedrive.readme.io/docs/webhooks-v2-migration-guide\" target=\"blank\">v1 to v2 migration guide</a> \n        and our <a href=\"https://pipedrive.readme.io/docs/guide-for-webhooks-v2\" target=\"blank\">guide for webhooks v2</a>.</p>\n      <h3>How to create v2 webhooks</h3>\n\t\t\t<p>At the moment, webhooks v2 can only be created via the API. Find out how to create them in our <a href=\"https://pipedrive.readme.io/docs/guide-for-webhooks-v2#how-to-create-webhooks-v2-via-api\" target=\"blank\">guide</a>.</p>\n      <h3>5 things to know about webhooks v2</h3>\n\t\t\t<ol type=\"1\">\n        <li>Webhooks v2 is still in BETA, so it may be subject to change</li>\n  \t\t\t<li>Webhooks v2 and v1 will continue to run in parallel for the time being. You will be notified of any changes via our <a href=\"https://developers.pipedrive.com/changelog\" target=\"blank\">Changelog</a>, so make sure you subscribe to it.</li>\n  \t\t\t<li>Please review the <a href=\"https://pipedrive.readme.io/docs/webhooks-v2-migration-guide\" target=\"blank\">v1 to v2 migration guide</a> closely as there are significant differences in webhooks v2’s payload</li>\n  \t\t\t<li>Webhooks v2 covers all event objects except <code>pipeline</code>, <code>stage</code> and <code>activityType</code> events. For those, please use v1.</li>\n  \t\t\t<li>Should a field no longer be available in the payload of a v2 webhook, please query it from our API</li>\n  \t\t</ol>\n\t\t\t<p>Learn about webhooks v2 <a href=\"https://pipedrive.readme.io/docs/guide-for-webhooks-v2\" target=\"blank\">here</a> and how to migrate your webhooks from v1 to v2 <a href=\"https://pipedrive.readme.io/docs/webhooks-v2-migration-guide\" target=\"blank\">here</a>. \n      If you have any feedback or run into any issues, please do let us know in our <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">Developers’ Community</a>!</p>\n  </div>\n</div>"
}
[/block]

{"product": [“API”, "Webhooks"], "features": ["Activities", "Deals", "Leads", "Notes", "Organizations", "Persons", "Products", "Users"], "email_description": "Built on a new technology platform, webhooks v2 is more reliable, which means there should be <b>no more duplicate or missing webhooks</b>. In addition, you can now <b>create <code>lead</code> webhooks</b>." }

Introducing webhooks v2

[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 20, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      <figure>\n  \t\t<img src=\"https://files.readme.io/834b94f-Developer_sandbox_account_overview.png\" alt=\"Developer Hub\">\n  \t\t<figcaption>The all-new Developer Hub</figcaption>\n\t\t\t</figure>\n      <p>Building apps is now easier with our brand-new <a href=\"https://pipedrive.readme.io/docs/developer-hub\" target=\"blank\">Developer Hub</a>! \n        Formerly known as Marketplace Manager, Developer Hub is where you can create and manage apps for the Pipedrive Marketplace.</p>\n      <p>From today, Developer Hub will be available in all developer sandbox accounts.</p>\n      <br>\n      <h3>What can I build in Developer Hub?</h3>\n      <p>Within <a href=\"https://pipedrive.readme.io/docs/developer-hub\" target=\"blank\">Developer Hub</a>, you can build public and private apps depending on your use case and service. \n        Public apps are for providing a public offering of your integration to any Pipedrive user, while private apps are for selected Pipedrive users/companies. \n        If you’re unsure what to build, we’ve got some inspiration for you <a href=\"https://developers.pipedrive.com/usecases\" target=\"blank\">here</a>.</p>\n      <b>What happens to the apps I had in Marketplace Manager?</b>\n\t\t\t<p>Don’t worry, all your apps will be moved to Developer Hub! \n        In your Developer Hub dashboard, you’ll find your public and private apps in the corresponding sections. \n        Unlisted apps will be moved to the Private apps section.</p>\n      <figure>\n  \t\t<img src=\"https://files.readme.io/9579524-Developer_Hub_dashboard_-_apps_list.png\" alt=\"Public and private apps in Developer Hub\">\n  \t\t<figcaption>Public and private apps in Developer Hub</figcaption>\n\t\t\t</figure>\n      <br>\n      <h3>Where can I find Developer Hub?</h3>\n      <p> Developer Hub is available in all developer sandbox accounts. \n        <a href=\"https://developers.pipedrive.com/\" target=\"blank\">Sign up for your sandbox account now</a> if you don’t already have one!</p>\n      <p>If you have a developer sandbox account, <a href=\"https://app.pipedrive.com/auth/login\" target=\"blank\">sign in</a> and go to <em>Settings > (company name) Developer Hub</em>.</p>\n       <figure>\n  \t\t<img src=\"https://files.readme.io/a4b7881-How_to_find_Developer_Hub.png\" alt=\"How to find Developer Hub\">\n\t\t\t</figure>\n      <p>Need Developer Hub in your main account? Let us know at <a href=\"mailto:marketplace.devs@pipedrive.com\">marketplace.devs@pipedrive.com</a>.</p>\n      <br>\n      <h3>What’s new in Developer Hub?</h3>\n      <b>Improved developer experience – no more long scrolling</b>\n      <p>Do more with Developer Hub! \n        Featuring an updated app registration form with different tabs, you can now easily access relevant sections as you build your app. \n        That’s right, no more long scrolling!</p>\n      <p>Moreover, you’ll get Helper content along the way to give you quick access to our developer tutorials and documentation when needed.</p>\n      <br>\n      <b>App extensions made easier</b>\n      <p>Implement and manage your app extensions more easily in the App extensions tab! \n        Add any app extensions you want by clicking on the respective buttons. \n        Head to the “My added extensions” section below to manage your added app extensions and add actions where applicable. \n        It’s all within one tab for easy management!</p>\n      <br>\n      <b>One-click preview for your Marketplace app listing</b>\n\t\t\t<p>Previewing your Marketplace app listing only takes one click on the green “Preview” button! \n        Found in the bottom left of the General info, Setup and installation, Support and Legal info tabs, you can now preview your app listing within Developer Hub to see how it’ll look in our Marketplace. \n        No more exiting your app registration form to preview!</p>\n      <br>\n      <b>Install and test your app right away</b>\n\t\t\t<p>Installing and testing your app can be done once you’ve inserted your callback URL and chosen your access scopes! \n        You’ll find a green “Install & test” button in the bottom left of the OAuth & access scopes tab and an “Install & test” prompt for all your draft apps in your Developer Hub dashboard. \n        Ensuring your app works as intended sure is key for public apps!</p>\n      <br>\n      <h3>Start building your app in Developer Hub</h3>\n      <p>To help you get started, see our guides on <a href=\"https://pipedrive.readme.io/docs/developer-hub\" target=\"blank\">Developer Hub</a>, \n        <a href=\"https://pipedrive.readme.io/docs/marketplace-registering-the-app\" target=\"blank\">how to register a public app</a>, \n        <a href=\"https://pipedrive.readme.io/docs/marketplace-registering-a-private-app\" target=\"blank\">how to register a private app</a> and \n        <a href=\"https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app\" target=\"blank\">how to update your app</a>.</p>\n\t\t\t<p><a href=\"https://app.pipedrive.com/auth/login\" target=\"blank\">Log in to your developer sandbox account</a> to check it out, \n        or <a href=\"https://developers.pipedrive.com/\" target=\"blank\">sign up to get your sandbox account</a> if you need one. \n        We can’t wait to see what you build for the Pipedrive Marketplace!</p>\n    </div>\n</div>"
}
[/block]

Building apps is now easier with our <b>brand-new Developer Hub</b>! Formerly known as Marketplace Manager, Developer Hub is where you can create and manage apps for the Pipedrive Marketplace.

App building just got easier with Developer Hub

[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 8, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      <p><b>What has been fixed?</b></p>\n      \n      <p>It has come to our attention that up until now, supplying a new <code>pipeline_id</code> when updating a deal via the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal\">PUT /deals/{id}</a></code> endpoint did not correctly update the <code>stage_id</code> associated with the deal’s pipeline.</p>\n      \n      <p>Hence, on <b>February 8, 2023</b>, we implemented a fix to the behavior in our system. Updating the <code>pipeline_id</code> of a deal via the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal\">PUT /deals/{id}</a></code> endpoint now automatically updates the associated <code>stage_id</code> value to the first stage of the specified pipeline.</p>\n      \n      <p>As a reminder, the behavior of <code>pipeline_id</code> and <code>stage_id</code> for the <code>PUT</code> endpoint is as follows:</p>\n      <ul>\n        <li><code>pipeline_id</code> - the ID of the pipeline this deal will be added to. By default, the deal will be added to the first stage of the specified pipeline.</li>\n        <li><code>stage_id</code> - the ID of the stage this deal will be added to. Please note that a pipeline will be assigned automatically based on the <code>stage_id</code>. If omitted, the deal will be placed in the first stage of the default pipeline.</li>\n      </ul>\n      \n      <p><b>What does it mean for me?</b></p>\n      \n      <p>The bug has been fixed in our system and no further action is required to continue using the <code>pipeline_id</code> and/or <code>stage_id</code> body parameters for updating deals.</p>\n      \n      <p>Should you notice an inconsistency between <code>pipeline_id</code> and <code>stage_id</code> values for existing deals that have been updated with the <code>PUT</code> endpoint, we suggest contacting our <a href=\"https://support.pipedrive.com/en/contact-us?ref=www\">support</a>.</p>\n      \n      <p>In the case of any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n      \n       </div>\n</div>"
}
[/block]

We have implemented a bug fix to the underlying behavior of the pipeline_id and stage_id parameters for the PUT /deals/{id} endpoint.

Bug fix in the behavior of <code>pipeline_id</code> and <code>stage_id</code> for <code>PUT /deals/{id}</code>

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">April 3, 2023</span>\n    </div>\n    <div class=\"change-area\">\n\n      <p><b>What is changing?</b></p>\n      <p><b>1. Products API</b></p>\n      \n      <p>From <b>April 3, 2023</b>, the data type for the <code>active_flag</code> and <code>selectable</code> body parameters will be changed to boolean (with true and false values), instead of the current integer type. This applies to the following endpoints:</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#addProduct\">POST /products</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#updateProduct\">PUT /products/{id}</a></code></li>\n      </ul>\n      \n      <p><b>2. Deals API</b></p>\n      <p>Similarly, from <b>April 3, 2023</b>, the data type for the <code>enabled_flag</code> body parameter will be changed to boolean (with true and false values), instead of the current integer type. This applies to the the following endpoints:</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDealProduct\">POST /deals/{id}/products</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDealProduct\">PUT /deals/{id}/products/{product_attachment_id}</a></code></li>\n      </ul>\n      \n       <p><b>Why is it changing?</b></p>\n\n      <p>Due to a legacy implementation on our side, the <code>active_flag</code>, <code>selectable</code>, and <code>enabled_flag</code> body parameters have so far accepted both boolean and integer data types. From April 3, 2023, the parameters will accept only boolean values to be consistent with other boolean fields in our API.</p>\n<p>In case of any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n      \n  </div>\n</div>"
}
[/block]

The data type for selectable, active_flag, and enabled_flag body parameters will be changed from integer to boolean for POST/PUT products and deal-products endpoints.

Breaking change: data type update for 3 products-related parameters

[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 31, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <p>1. We added the <code>deal_id</code> field to the response example of the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealFollowers\">GET /deals/{id}/followers</a></code> endpoint to reflect reality.</p>\n      \n      <p>2. The <code>location_lat</code> and <code>location_long</code> fields were removed from 4 response examples as these fields are not returned in the responses in reality. This applies to the following endpoints:</p>\n  \t\t<ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Activities#getActivities\">GET /activities</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Activities#getActivity\">GET /activities/{id}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Activities#addActivity\">POST /activities</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Activities#updateActivity\">PUT /activities/{id}</a></code></li>\n      </ul>\n  \n      <p>3. We removed the mistakenly documented required label from the <code>name</code> and <code>manager_id</code> body parameters of the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/LegacyTeams#updateTeam\">PUT /legacyTeams/{id}</a></code> endpoint.</p>\n  \n  </div>\n</div>"
}
[/block]

The latest updates to our API Reference include adding the deal_id field to the example response of the GET /deals/{id}/followers endpoint, and removing unnecessary required labels from PUT /legacyTeams/{id}.

January 2023 release notes

[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 23, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We are introducing <a href=\"https://support.pipedrive.com/en/article/pipeline-visibility\">pipeline visibility</a> inside the <a href=\"https://support.pipedrive.com/en/article/visibility-groups\">visibility groups feature</a> in our web app and API so users can restrict and control access to specific pipelines and the deals inside them.</p>\n      </br>\n      <p><b>What is changing?</b></p>\n      \n      <p>When visibility restrictions are applied for a pipeline, the responses of the Pipelines API, Deals API, and Stages API endpoints will behave as following:</p>\n      </br>\n      <p><b>1. Pipelines API</b></p>\n      <p>The GET endpoints of the Pipelines API will not return information for pipelines that are not visible to the user making the request. This applies to the following endpoints:</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelines\">GET /pipelines</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipeline\">GET /pipelines/{id}</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelineConversionStatistics\">GET /pipelines/{id}/conversion_statistics</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/Pipelines#getPipelineMovementStatistics\">GET /pipelines/{id}/movement_statistics</a></code></li>\n      </ul>\n   </br>\n      \n      <p>The GET endpoints for retrieving the info of a specific pipeline will return <code>HTTP 404</code> if the pipeline is not visible.</p>\n      <p>Deleting a pipeline that is the last visible pipeline for any visibility group will not be possible and a <code>HTTP 400</code> error response will be returned. This applies to the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Pipelines#deletePipeline\">DELETE /pipelines/{id}</a></code> endpoint.</p>\n     \n      </br>\n      <p><b>2. Deals API</b></p>\n      <p>The GET endpoints of the Deals API will not return deal information that is not visible to the user making the request. This applies to 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#searchDeals\">GET /deals/search</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealsSummary\">GET /deals/summary</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline\">GET /deals/timeline</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#getDealActivities\">GET /deals/{id}/activities</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealFiles\">GET /deals/{id}/files</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealUpdates\">GET /deals/{id}/flow</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealFollowers\">GET /deals/{id}/followers</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealMailMessages\">GET /deals/{id}/mailMessages</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealParticipants\">GET /deals/{id}/participants</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealPersons\">GET /deals/{id}/persons</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealProducts\">GET /deals/{id}/products</a></code></li>\n      </ul>\n </br>\n      \n      <p>The endpoints for retrieving and updating the information of a specific deal will return <code>HTTP 403</code> if the deal is not visible.</p>\n      \n      <p>The <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDeal\">POST /deals</a></code> endpoint will return <code>HTTP 400</code> in these cases:</p>\n      <ul>\n        <li>When creating a deal with the <code>pipeline_id</code> or <code>stage_id</code> parameters for a pipeline/stage that is not visible to the user</li>\n        <li>When creating a deal with the <code>pipeline_id</code> or <code>stage_id</code> and <code>user_id</code> parameters for a pipeline/stage that is not visible to the assigned user</li>\n      </ul>\n      <p>If a deal is being created without <code>pipeline_id</code> or <code>stage_id</code> assigned, the deal will be automatically assigned to the first pipeline visible to the user.</p>\n      \n      <p>The <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal\">PUT /deals/{id}</a></code> endpoint will return <code>HTTP 403</code> when supplying a <code>stage_id</code> of a stage that is not visible to the user making the request and/or a <code>user_id</code> who does not have visibility for the pipeline/stage.</p>\n      \n  </br>\n      <p><b>3. Stages API</b></p>\n      \n      <p>The <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Stages#getStages\">GET /stages</a></code> endpoint will not return information about stages which are not visible to the user making the request.</p>\n      <p>The <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Stages#getStage\">GET /stages/{id}</a></code> and <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Stages#getStageDeals\">GET /stages/{id}/deals</a></code> endpoints will return <code>HTTP 404</code> if the specified stage is not visible.</p>\n      \n</br>\n      <p>In case of any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n      \n      \n      </div>\n</div>"
}
[/block]

We are introducing pipeline visibility inside the visibility groups feature in our web app and API so users can restrict and control access to specific pipelines and the deals inside them.

Introducing pipeline visibility

[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 15, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <p><b>What is changing?</b></p>\n      \n      <p>From <b>March 15, 2023</b>, we will be adding <code>limit</code> and <code>start</code> query parameters to the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Stages#getStages\">GET /stages</a></code> endpoint to support pagination:</p>\n      <ul>\n        <li><code>limit</code> - The limit of entries to be returned</li>\n        <li><code>start</code> - The position that represents the first result for the page</li>\n      </ul>\n      \n      <p>If the <code>limit</code> value is not provided, 100 stage items will be returned.</p>\n      <p>Please refer to our Developer Documentation for more information on <a href=\"https://pipedrive.readme.io/docs/core-api-concepts-pagination\">pagination</a>.</p>\n      \n      <p><b>Why is it changing?</b></p>\n      <p>We are introducing pagination support for this endpoint to ensure that responses with a big amount of data are easier to handle.</p>\n      \n\t\t\t<p><b>Who will be affected?</b></p>\n      <p>Everyone using the specified endpoint to retrieve stages.</p>\n\t\t\t<p>If you have any questions or comments, let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n      \n      </div>\n</div>"
}
[/block]

We are introducing pagination for the GET /stages endpoint.

Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog