[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 25, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We are changing how deals, leads and projects can be linked to activities.</p>\n<br/>\n<p><b>What is changing?</b></p>\n<p>At the moment when creating or updating an activity via Public API it is possible to link it with a deal, lead and a project at the same time. </p>\n<p>After the changes are applied, it will only be possible to link an activity to one of the mentioned entities at once. The change affects the following 2 endpoints:\n</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Activities#addActivity\" target=\"blank\">POST /v1/activities</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Activities#updateActivity\" target=\"blank\">PUT /v1/activities/{id}</a></code></li>\n      </ul>\n<p>It means that an activity can only be linked either to a deal, lead or a project. </p>\n<p>If passing several of the mentioned entities in the payload the following hierarchy for linking will be used:</p>\n      <ul>\n        <li>If <code>deal_id</code> is passed together with <code>lead_id</code> or <code>project_id</code> the activity will be only linked to the deal</li>\n        <li>If <code>lead_id</code> is passed together with <code>project_id</code> the activity will be only linked to the lead</li>\n      </ul>\n\n<p><b>What is changing?</b></p>\n<p>Activities have always been intended to work like this but this limitation has never been implemented in our public API. This brings confusion for our users because Pipedrive UI has been built considering this limitation.</p>\n\n\n<p>If you have any questions or comments, please let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n\n\t\t</div>\n</div>"
}
[/block]

We are changing how deals, leads and projects can be linked to activities

Changes to activities connected entities

[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 26, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <h3><b>What is changing?</b></h3>\n      <p>We’ve introduced new read-only and full-access OAuth scopes for Webhooks, which allow apps to create, fetch and delete webhooks on users’ behalf.</p>\n      \n      <p><b>webhooks:read</b></p>\n      <p>When the <b><code>webhooks:read</code></b> scope is selected, an app can access the endpoint below, allowing it to list webhooks associated with its user.</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Webhooks#getWebhooks\" target=\"blank\">GET /v1/webhooks</a></code></li>\n      </ul>\n      \n      <p><b>webhooks:full</b></p>\n      <p>When the <b><code>webhooks:full</code></b> scope is selected, an app can access the endpoints below, allowing it to list webhooks associated with its user, create and delete webhooks for them.</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Webhooks#getWebhooks\" target=\"blank\">GET /v1/webhooks</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Webhooks#addWebhook\" target=\"blank\">POST /v1/webhooks</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Webhooks#deleteWebhook\" target=\"blank\">DELETE /v1/webhooks/{id}</a></code></li>\n      </ul>\n      <p>Learn more about Pipedrive webhooks <a href=\"https://pipedrive.readme.io/docs/guide-for-webhooks-v2\" target=\"blank\">here</a> and about scopes and permission <a href=\"https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations\" target=\"blank\">here</a>.</p>\n      \n      <h3><b>Why is it changing?</b></h3>\n      <p>We’ve implemented this change to allow flexible, more granular access to users’ data and improve app accessibility.</p>\n      \n      <h3><b>Migration guide</b></h3>\n      <p>Please note that webhook-specific endpoints are still available under the <b><code>admin</code></b> scope. No changes were made to existing public or private apps.</p>\n      <p>We’re also working on a separate solution that would allow apps with webhooks to switch from the <b><code>admin</code></b> scope to a new scope without asking users to re-install the app. We’ll share more details about it soon!</p>\n      <p>If you still want to add or remove the scopes of an approved or published app, <a href=\"https://pipedrive.readme.io/docs/marketplace-updating-the-existing-app#changing-the-scopes\" target=\"blank\">learn how changing the scopes will affect your app's existing users</a>.</p>\n      <p>If you have any questions or comments, please let us know in the <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">Developers’ Community</a>.</p>\n      \n\t\t</div>\n</div>"
}
[/block]

Introducing new OAuth scopes for Webhooks

[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 16, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      <p>We’ve introduced new endpoints to allow you to integrate video-calling apps into Pipedrive through a <a href=\"https://pipedrive.readme.io/docs/video-calling-app-extension\">video calling app extension</a>.\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Meetings#saveUserProviderLink\" target=\"blank\">POST /meetings/userProviderLinks</a></code> – to link a user to the installed video call integration, allowing them to create video call links for their activities.</li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Meetings#deleteUserProviderLink\" target=\"blank\">DELETE /meetings/userProviderLinks/{id}</a></code> – to unlink a user from the video call integration when uninstalling it.</li>\n      </ul></p>\n      \n\t\t<p>If you have any questions or comments, please let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n\n\t\t</div>\n</div>"
}
[/block]

We are introducing endpoints for linking and unlinking a user to/from a video call integration.

New <code>/userProviderLinks</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\">March 18, 2024</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <p><b>What is changing?</b></p>\n      \n      <p>From <b>March 18, 2023</b>, we are starting to restrict editing of soft-deleted deals via <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#updateDeal\">PUT deals/{id}</a></code> endpoint. This means that it is not possible to edit any fields (except restoring the deal) once the <code>status</code> of the deal has changed to <code>deleted</code>. In order to be able to edit that soft deleted deal, you must first restore that deal.</p>\n      \n      <p><b>Why is it changing?</b></p>\n      \n      <p>We already have similar behavior for <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#updatePerson\">PUT persons/{id}</a></code> and <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Organizations#updateOrganization\">PUT organizations/{id}</a></code>. Editing fields after the entity has been soft deleted will push the deadline for permanent deletion further which may cause confusion and additional issues for our customers.</p>\n      \n      <p>If you have any questions or comments, please let us know in <a href=\"https://devcommunity.pipedrive.com/\">the Developer’s Community</a>.</p>\n      \n      </div>\n</div>"
}
[/block]

We are starting to restrict editing of soft deleted deals

Breaking change: update to the behavior of <code>PUT deals/{id}</code> endpoint for soft-deleted 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\">December 18, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <p>We’ve introduced a <b>new body parameter</b> in the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLog\">POST /callLogs</a></code> endpoint allowing you to associate call logs with leads.</p>\n      \n      <p><b>What was added</b></p>\n      \n      <p>From <b>December 18, 2023</b>, you can add a new body parameter to the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/CallLogs#addCallLog\">POST /callLogs</a></code> endpoint:</p>\n      <ul>\n        <li><code>lead_id</code> - The ID of the lead the call log is associated with in UUID format (optional)</li>\n      </ul>\n      \n      <p><b>Please note that a single call log can only be associated with either a deal or a lead, not both at the same time.</b></p>\n      <p>If you have any questions or comments, please 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 a new optional parameter in POST /callLogs endpoint

New optional parameter in <code>POST /callLogs</code> endpoint

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">October 18, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      <p><b>What is new?</b></p>\n      <p>We’re launching <b>three</b> new API resources with a range of endpoints to help you modify the data around the Projects feature space, allowing integrations and automations to join in on providing solutions in the <b>project and task management</b> problem space. The endpoints are tied with the Projects add-on which has to be enabled for the functionality to be used.\n</p>\n      <p><b><a href=\"https://developers.pipedrive.com/docs/api/v1/Projects\" target=\"blank\">Projects API</a></b> allows to create and manage ongoing, completed or canceled projects attached to an organization, person or to deals. Each project has an owner and must be placed in a phase. Each project consists of standard data fields but can also contain a number of custom fields. The custom fields can be recognized by long hashes as keys.\n      </p>\n      <p><b><a href=\"https://developers.pipedrive.com/docs/api/v1/ProjectsTemplates\" target=\"blank\">ProjectsTemplates API</a></b> allows to have a reusable and dynamic structure to simplify creation of a project. Project templates can contain information about activities, tasks and groups that will be used when creating a project. Currently, only GET functionality is available.\n </p>\n      <p><b><a href=\"https://developers.pipedrive.com/docs/api/v1/Tasks\" target=\"blank\">Tasks API</a></b> allows to create and manage actions that need to be completed inside a project. A task must be associated with a project. Tasks have an optional due date, can be assigned to a user and can have subtasks.\n</p>\n      <br>\n      <p>All new endpoints support querying based on <a href=\"https://pipedrive.readme.io/docs/core-api-concepts-pagination#cursor-pagination\" target=\"blank\">cursor pagination</a>.\nThe endpoints are also included in two new OAuth scopes: Projects read and Projects full, see the full division of endpoints in scopes <a href=\"https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations\" target=\"blank\">here</a>.\n</p>\n      <br>\n      <p><b>Timeline of the launch</b></p>\n      <p>\n        We’re releasing the public BETA today, October 18th, and the API will be available for usage and testing on all accounts. We’ll notify you here in the changelog once the full version of the API is released, so remember to subscribe.\nKeep in mind that between the BETA and the full release of the API, the endpoints are subject to changes.\n      </p>\n      <p>We are eager to hear your feedback, questions or comments in\n<a href=\"https://devcommunity.pipedrive.com/\" target=\"_self\">the Developers’ Community</a>.</p>\n      </div>\n</div>"
}
[/block]

{“product”: [“API”], “features”: [“Projects, ProjectTemplates, Tasks”], “email_description”: “We’re happy to share the public BETA launch of Project API together with ProjectTemplates API and Tasks API.“}

Introducing Projects API in public BETA

[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 7, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <blockquote class=\"callout callout_info\" theme=\"📘\"><p class=\"callout-heading empty\"><span class=\"callout-icon\">📘</span></p><p><strong>We've decided to retract the change to Deals API</strong>: </p><p>After careful consideration and valuable input from feedback from our API users, we have decided to retract the previously announced breaking change to the API.</p><p><strong>Why are we retracting the change?</strong></p><p>Upon reviewing the concerns raised, it became evident that the implementation of workarounds to get the exact time of deal closures would impose undue burdens on our technology partners and customers. Therefore, we have opted to maintain the current functionality, where the relevant fields will continue to return full datetime values as they presently do.</p><p><strong>Will this retraction affect those using the existing API?</strong></p><p>There will be no alterations to the current API behavior, and consequently, no adverse effects will arise for those utilizing the established client code.</p><p><strong>What about those who have already made adjustments towards the new API behavior?</strong></p><p>For those who have proactively updated their code in anticipation of the new API specifications, firstly, thank you for your proactive work. With this retraction, we advise reverting any modifications pertaining to the now-retracted change. The API will continue to function as it did prior to the announcement, negating the necessity for these adjustments.</p><p>We apologize for any inconvenience this announcement may have caused and are committed to ensuring that our API remains user-friendly. Your continued support, feedback and understanding are greatly appreciated.</p><p>We at Pipedrive are committed to ensuring that every customer and partner has a stable and trustworthy experience with all of our products and services. Therefore, we’ll continue with transparent communications regarding our API and developer platform.</p></blockquote>\n      \n      <p><b>What is changing?</b></p>\n      <p>The data type for the <code>close_time</code>, <code>won_time</code>, <code>first_won_time</code>, and <code>lost_time</code> response fields will be changed from <code>datetime</code> to <code>date</code> for the following Deals API endpoints:</p>\n      <ul>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDeals\" target=\"blank\">GET /deals</a></code></li>\n         <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealsTimeline\" target=\"blank\">GET /deals/timeline</a></code></li>\n         <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDeal\" target=\"blank\">GET /deals/{id}</a></code></li>\n         <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#addDeal\" target=\"blank\">POST /deals</a></code></li>\n         <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#duplicateDeal\" target=\"blank\">POST /deals/{id}/duplicate</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#mergeDeals\" target=\"blank\">PUT /deals/{id}/merge</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Persons#getPersonDeals\" target=\"blank\">GET /persons/{id}/deals</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Pipelines#getPipelineDeals\" target=\"blank\">GET /pipelines/{id}/deals</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Products#getProductDeals\" target=\"blank\">GET /products/{id}/deals</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Recents#getRecents\" target=\"blank\">GET /recents</a></code></li>\n        <li><code><a href=\"https://developers.pipedrive.com/docs/api/v1/Stages#getStageDeals\" target=\"blank\">GET /stages/{id}/deals</a></code></li>\n      </ul>\n     \n      \n      <p>Similarly, the <code>won_time</code> and <code>lost_time</code> response fields will be changed from <code>datetime</code> to <code>date</code> in the <code><a href=\"https://developers.pipedrive.com/docs/api/v1/Deals#getDealsCollection\" target=\"blank\">GET /deals/collection</a></code> endpoint.</p>\n      \n      <p>The update will be gradually rolled out between <b>December 6 and December 13, 2023</b>.</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</div> "
}
[/block]

We are updating the data type for four deals-related response fields from datetime to date.

Breaking change: data type update for 4 deals-related response fields

[block:html]
{
  "html": "<div class=\"chlog-box\">\n    <div class=\"from-area\">\n        <span class=\"from-label\">Effective from:</span><br>\n        <span class=\"from-date\">September 5, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <p>We have implemented the following bug fixes in <a href=\"https://pipedrive.readme.io/docs/guide-for-webhooks-v2#webhook-format\" target=\"blank\">webhooks v2</a> for better user management and consistency with webhooks v1:</p>\n     \n      <p>1. The <code>user_id</code> field in the payload now represents the ID of the user who triggered the webhook. Previously, the field represented the owner of the webhook.</p>\n      \n      <p>2. We have added the <code>webhook_owner_id</code> field inside the meta section of the payload. This field represents the ID of the user who created the webhook.</p>\n      \n      <p>Please refer to our <a href=\"https://pipedrive.readme.io/docs/guide-for-webhooks-v2#webhook-format\" target=\"blank\">webhooks v2 guide</a> for more details. For any questions or comments, please share them in <a href=\"https://devcommunity.pipedrive.com/\" target=\"blank\">our Developers’ Community</a>.</p>\n      \n      \n      </div>\n</div>"
}
[/block]

We have implemented two bug fixes in the webhooks v2 payload for better user management.

Bug fixes in webhooks v2 payload

[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\">November 15, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      \n      <p>UPDATE: In order to support the use cases where a deal has a larger amount of notes, we are updating the announced new notes per deal limit to 100.\n      \n      <p>We are introducing a new limit to the size of notes and the allowed number of notes per deal as a proactive measure aimed at safeguarding our system from potential misuse and excessive load.</p>\n      \n      <h3><b>What is changing?</b></h3>\n      <p><b>1. Limit on note size</b></p>\n      \n      <p>From <b>November 15, 2023</b>, notes will have <b>a maximum size limit of 100 kB</b>. Adding new notes and/or updating existing ones over the 100 kB limit will fail with a <code>400</code> error code for these endpoints:</p>\n      <ul>\n        <li><code></code><a href=\"https://developers.pipedrive.com/docs/api/v1/Notes#addNote\" target=\"blank\">POST /notes</a></li>\n        <li><code></code><a href=\"https://developers.pipedrive.com/docs/api/v1/Notes#updateNote\" target=\"blank\">PUT /notes/{id}</a></li>\n      </ul>\n      \n      <p><b>Please note that all existing notes exceeding the 100 kB limit will remain usable, but cannot be edited, unless they meet the size requirement.</b></p>\n      \n      <p>Here's an example of the <code>400</code> error response:</p>\n      <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\" role=\"tablist\"><button aria-selected=\"true\" class=\"CodeTabs_active\" role=\"tab\" type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\" role=\"tabpanel\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\" tabindex=\"0\"><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\">\"Note content size cannot be more than 100 kB.\"</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      <br>\n      \n      <p><b>2. Limit on notes per deal</b></p>\n      <p>Similarly, from <b>November 15, 2023</b>, the <b>maximum number of notes per deal will be 100</b>. If the limit is exceeded for a specific deal, attempting to add new and/or update existing notes to be associated with the deal via the following endpoints will fail:</p>\n       <ul>\n        <li><code></code><a href=\"https://developers.pipedrive.com/docs/api/v1/Notes#addNote\" target=\"blank\">POST /notes</a></li>\n        <li><code></code><a href=\"https://developers.pipedrive.com/docs/api/v1/Notes#updateNote\" target=\"blank\">PUT /notes/{id}</a></li>\n      </ul>\n      \n      <p>Here's an example of the <code>400</code> error response:</p>\n      <div class=\"CodeTabs CodeTabs_initial theme-light\"><div class=\"CodeTabs-toolbar\" role=\"tablist\"><button aria-selected=\"true\" class=\"CodeTabs_active\" role=\"tab\" type=\"button\">JSON</button></div><div class=\"CodeTabs-inner\" role=\"tabpanel\"><pre><button aria-label=\"Copy Code\" class=\"rdmd-code-copy fa\"></button><code class=\"rdmd-code lang-json theme-light\" data-lang=\"json\" name=\"\" tabindex=\"0\"><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\">\"The limit of 50 notes per deal has been reached.\"</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      <h3><b>Why is it changing?</b></h3>\n      <p>We are introducing the two new note-related limits in an effort to ensure the optimal performance and security of our system. We believe the 100 kB limit is generous enough to cover various use cases for notes while also protecting our system from potential misuse.</p>\n      \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    </div>\n</div>  "
}
[/block]

We are introducing two new limits to Notes API: the maximum note size of 100 kB and the maximum number of notes per deal as 50. The goal of the limits is to safeguard our system from potential misuse and excessive load.

Breaking change: new note size and notes per deal limits

[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 14, 2023</span>\n    </div>\n    <div class=\"change-area\">\n      <p>Based on your feedback, we’ve made one of the most requested app features possible: iframes!</p>\n      <p>With our <a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions\" target=\"blank\">custom user interface (UI) extensions</a>, \n        you can render an embedded iframe with any contextual web content directly inside different Pipedrive views.</p>\n      <img src=\"https://files.readme.io/4614557-Custom_floating_window_in_Pipedrives_user_interface.png\">\n      <h3>Why should you implement custom UI extensions for your app?</h3>\n      <p>With custom UI extensions, you can now display your content natively in Pipedrive’s UI. This enables you to extend your app’s functionality in a multitude of ways, such as:\n\t\t\t<ul>\n\t\t  <li>Calling – outgoing and incoming calls, call notifications, in-call activities, call outcomes and follow-up actions</li>\n\t\t  <li>Messaging – messaging conversations and notifications</li>\n\t\t\t<li>The sky is the limit for any use case that helps customers win more deals! Display incoming support cases, showing a stream of contextual events from email marketing, lead generation \n        and other customer engagement tools, e.g., campaign click rates, webform/survey submissions, website visits, etc.</li>\n      </ul>\n      </p>\n  \t\t<p>Start building with the four custom UI extensions we offer:\n\t\t\t<ul>\n      <li><a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions-floating-window\" target=\"blank\">Custom floating window</a></li>\n\t\t\t<li><a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions-panels\" target=\"blank\">Custom panels</a></li>\n\t\t\t<li><a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions-modals\" target=\"blank\">Custom modals</a></li>\n\t\t\t<li><a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions-app-settings\" target=\"blank\">Custom UI for app settings</a></li>\n\t\t\t</ul>\n  \t\t</p><br>\n<h3>Custom floating window</h3>\n<p><img src=\"https://files.readme.io/7685eb9-Custom_floating_window.png\"></p>\n<p>A <a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions-floating-window\" target=\"blank\">custom floating window</a> is an iframe embedded inside a <b>resizable and draggable window</b> that <b>persists while a user navigates</b> around Pipedrive.</p>\n<p>Users can drag the floating window around Pipedrive’s interface, while apps can resize it and make it visible where appropriate, e.g., when a user receives an incoming call/message.</p>\n<p>In addition, apps with a custom floating window have a <a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions-floating-window#visibility-in-pipedrives-ui\" target=\"blank\">default entry point in the apps dock</a> located in a popover visible from the puzzle icon in the top bar.</p>\n<h3>Custom panels</h3>\n<img src=\"https://files.readme.io/5180f4a-Custom_panel.png\">\n<p>A <a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions-panels\" target=\"blank\">custom panel</a> is an iframe embedded inside a <b>sidebar panel in the detail view</b> of deals, people, and organizations. Its height can be customized.</p>\n<h3>Custom modals</h3>\n<img src=\"https://files.readme.io/f5ab078-Custom_modal.png\">\n<p>A <a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions-modals\" target=\"blank\">custom modal</a> is an iframe embedded in a <b>modal</b> window that <b>opens when triggered</b> by the user from various menus and links inside Pipedrive. A custom modal’s height and width are adjustable, as a modal can have a larger area.</p>\n<p>Custom modals have multiple entry points, including list and detail views and via the SDK.</p>\n<h3>Custom UI for app settings</h3>\n<p>Custom UI for app settings is an iframe embedded in a surface that gives users easy access to user settings for your app.</p>\n<br>\n<h3>Get inspired with our sample apps</h3>\n<p><b>Custom UI extensions x contract management sample app</b><br>\nLearn <a href=\"https://developers.pipedrive.com/tutorials/docusign-contract-management-custom-ui-integration?step=1\" target=\"blank\">how to integrate a contract management service into Pipedrive using custom UI extensions</a>. Although this tutorial centers on document/contract management, it can be extended to various use cases like proposals and CPQ (Configure, Price, Quote) integrations.</p>\n<p><b>Custom floating window x calling integrations</b><br>\nUsing the custom floating window, learn <a href=\"https://developers.pipedrive.com/tutorials/custom-floating-window-ui-caller-integrations\" target=\"blank\">how to integrate a calling service into Pipedrive</a>. While this extension is suitable for use cases that involve calling, telephony and messaging, it’s also an open canvas for any use case that fits.</p>\n<br>\n<h3>Start building custom UI extensions for your app</h3>\n<p>Check out our <a href=\"https://pipedrive.readme.io/docs/custom-ui-extensions\" target=\"blank\">custom UI extensions guide</a> and <a href=\"https://app.pipedrive.com/auth/login\" target=\"blank\">log in to your developer sandbox account</a> to start building. We’re excited to see how you use these extensions in your app!</p>\n<p>NB: If you need a sandbox, you can sign up for one <a href=\"https://developers.pipedrive.com/\" target=\"blank\">here</a>.</p>\n</div>\n</div>"
}
[/block]

Extend your app's functionality with our custom UI app extensions. Load any contextual web content within an embedded iframe directly inside different Pipedrive views.

Contents

Changelog

Announced changes

Subscribe to our Changelog

Subscribe to our Changelog

Subscribe to our
Changelog