Download Pardot Email API

Actions that users can use to create custom flows.March 9, 2023 Pardot Package v4.89 We changed the label for the legacy Pardot app that appears in the App Launcher to Pardot Classic (Deprecated). We changed the labels for default fields and default permission sets to match our new Account Engagement brand. We also fixed a performance issue when updating Lead, Contact, and Account records under certain conditions.December 12, 2022 Pardot Package v4.88 We fixed a performance issue when updating account records under certain conditions.July 19, 2022 Pardot Package v4.87 We changed the label for the legacy Pardot app that appears in the App Launcher to Pardot Classic. We also updated select classes to API version 53.0.February 9, 2022 Pardot Package v4.85 We upgraded the API version of several classes in the package to ~v53.0 to ensure that no class is using an outdated version.January 13, 2022Pardot Package v4.84We fixed an issue where the contents of different folders with the same name were merged into a single folder.December 16, 2021Pardot Package v4.82We updated the send limit logic to allow Salesforce Engage users the ability to select recipients up to their actual daily sending limit. September 8, 2021Pardot Package v4.81We updated the install link for the Engage Alerts Desktop app in the Engage Sales Tools page. August 18, 2021Pardot Package v4.80We fixed an issue where Engage wouldn’t show an error to indicate when an Image does not have a proper contentDownload Url. We fixed an issue where the Engage image editor would freeze if too many records when orgs had a large number of ContentVersion records. May 19, 2021Pardot Package v4.79We fixed an issue where Engage campaigns didn’t recognize merge fields for custom email preference center pages. February 11, 2021Pardot Package v4.78We fixed an issue with the Engage desktop app so that

Bug fixes and enhancements.January 5, 2017Name 14.7.0, Number 3.10Includes minor bug fixes.December 21, 2016Name 14.5.0, Number 3.8Includes minor bug fixes and enhancements.December 14, 2016Name 14.4.0, Number 3.7Includes minor bug fixes.November 30, 2016Name 14.3.2, Number 3.6.2Includes minor bug fixes and allows Salesforce Engage users to view the names and emails of recipients on the Preview tab when sending Engage Campaigns.November 18, 2016Name 14.2.1, Number 3.5.1Includes minor bug fixes and the Engagement History lightning component, an updated way to view Pardot and Salesforce Engage activities within Salesforce. If Lightning Experience is enabled in your Salesforce org, we recommend replacing the Pardot Activities VisualForce page with the Engagement History component on lead and contact record detail page.November 9, 2016Name 14.0.1, Number 3.3.1Resolves an issue with special characters causing HTML entities to display in Engage Email subject lines.November 1, 2016Name 14.0.0, Number 3.3Includes a new Visualforce page called PardotCompatibleWithClickjack. Customers who have clickjack protection for Visualforce pages with headers disabled enabled in their org can create a new Pardot tab using the PardotCompatibleWithClickjack Visualforce page, or disable the setting. See Adding the Pardot Compatible With Clickjack Visualforce Page for more information.October 28, 2016Name 13.8.1, Number 3.1.1Resolves an issue in the previous version (Name 13.8.0, Number 3.1) in Engage Campaigns that was causing additional CSS to be added to email copy.October 26, 2016Name 13.8.0, Number 3.1Includes security updates that require users that need to access or use Pardot data in Salesforce to have the Pardot Permission Set assigned. Enterprise edition Salesforce customers can opt to manually assign the permissions. Users whose permissions are manually assigned will need to assign the PardotResourceBaseByUserExtension class and the following pages: Pardot, SendPardotEmailContact, SendPardotEmailLead, SendToPardot.These updates eliminate the small number of Salesforce API calls that were being counted for things like viewing a lead or contact with a Pardot Activities

Pardot APIs let you extend your marketing automation efforts with integrations. Postman is an API platform that makes it easy to build, test, and experiment with API calls. You can use Pardot and Postman together to easily test and explore all that v5 of the Pardot API has to offer.On the Postman platform, a Postman Collection is a group of requests that are saved and organized in folders. Our collection includes calls for the 15 objects in v5 of the Pardot API.This blog post focuses on the Pardot public collection, so if you’re not already using Postman with the Salesforce API, check out the blog post, Explore the Salesforce APIs with a Postman Collection, to learn more. If you’ve never used an API client and you’re feeling overwhelmed, check out the Postman API Client Trailhead module to get some hands-on experience and gain confidence.Just a quick note before you get started: this collection is provided as-is. It’s not officially supported by Salesforce or covered by SLAs.Getting started with PostmanBefore you get started, you need a Salesforce username and password, a Pardot Business Unit ID, and the Consumer ID and Consumer Secret for a connected app with the Access Pardot Services scope. For more help, see the Getting Started with Pardot APIs guide in the Pardot developer docs.Next, install Postman and import the Pardot collection by following the instructions in our Github project.Finally, you are ready to set up authorization; the collection’s authorization uses variables with OAuth 2.0.On the collection folder’s tab, click Variables and add your information to the Current Value column. Note: grant_type, sf_username, and sf_password are only required if you choose to use the the username/password OAuth2.0 flow. After you’ve set up your variables, click the Authorization tab, scroll to the bottom, and click Get New Access Token. Follow the prompts to authorize.We’ve added robust documentation to the collection to make sure that you can find what you need. So, anytime you get stuck, just open the Documentation pane to get unstuck. Making a request to the Pardot APIAfter you’ve authorized, start experimenting with making requests to the Pardot API. For this example, let’s query the Campaigns object.Open the Campaign folder, then click Query. Configure the parameters for your query and click Send. If the request is successful, you’ll see a response on the bottom half of the page. ConclusionNow that you’ve seen the basics, get out there

To include forms and landing pages, optimized the flow structure, and fixed a few bugs.April 30, 2024 Pardot Package v4.96 We fixed a bug where some Leads/Contacts associated with Campaigns that have fractional cost values would receive an “An error has occurred” warning on the Engagement History Lightning Component. This addresses a Known Issue.April 30, 2024 Pardot Package v4.95 We fixed a bug where a timeout would lead to “We’re having trouble connecting” on the Engagement History Lightning Component for some Leads/Contacts. We fixed a bug where permissions for some of the provided VisualForce pages would have to be manually added to users even after the user had the Pardot permission set. The Pardot permission set now includes the missing permissions.February 20, 2024 Pardot Package v4.94 Improved form handlers by adding in a form field dependency, so now the form fields are copied automatically when you copy the form handler. Added status and error reasons to the confirmation screen to provide insight into copy failures.January 23, 2024 Pardot Package v4.93 We fixed an issue in the Bulk Asset Copy flow where the folder list is empty when a business unit has more than 2000 files.October 31, 2023 Pardot Package v4.92 We updated the Pardot package to include new invocable actions and a new flow that moves marketing content from sandbox to production environments. We also fixed the issue where the Sales Emails and Alerts app didn't show up in Lightning Experience, and fixed the unreliable Engage Campaign "Send Engage Email" button on list views for Sales Engagement customers.July 6, 2023 Pardot Package v4.90 We added API V5 for Flow that users can use to copy flows. We added a default Account Engagement Bulk Asset Copy Flow that users can use as a template to copy flows. We also added invocable

Custom objects, VisualForce pages, tabs, permission set, and custom permissions.March 16, 2015Name 4.3, Number 1.28.1.Corrects an issue with the “Send to Pardot” button for prospects with a ‘+’ character in their email address.November 18, 2013Name 4.3, Number 1.28Added the following Visualforce lead and contact fields: Pardot Activities Mobile, Pardot List Membership Mobile and Pardot Social Data Mobile for mobile integration with the Salesforce1 app.September 13, 2013Name 4.2, Number 1.27Added fields that capture Pardot visitor/prospect conversion data (conversion date, conversion object type, and conversion object name)December 17, 2012Name 4.0, Number 1.25.Added ability to send tracked Pardot emails from the Salesforce lead or contact record.August 21, 2012Name: 3.9, Number: 1.23.Corrects an issue with the activities iframe for prospects with ‘+’ characters in their email addresses.November 8, 2011Name: 3.7, Number: 1.21.Resolves issue where clicking the “Send to Pardot” button after updating an email address in Salesforce was creating a new record in Pardot.July 22, 2011Email changes in Salesforce now sync down to Pardot.May 9, 2011Name: 3.4, Number: 1.17.Includes an updated version of LeadDeck.March 14, 2011Includes the Pardot Lists VisualForce element, which enables list management in the CRM.January 7, 2011Name: 3.2, Number: 1.15.Includes trigger to stop syncing deleted leads and contacts.October 30, 2009Name: 2.7, Number: 1.8.Activities section was changed from an S-Control to a VisualForce Element.May 5, 2009Name: 2.5, Number: 1.7.Includes fields for Google Analytics parameters.April 17, 2009 Name: 2.4, Number: 1.6.November 30, 2007Initial releaseNeed more? Start a conversation with other Pardot users in the Trailblazer Community.