ApivomApivom
Get Demo

Marketing Cloud Account Engagement (Pardot) API

Marketing Cloud Account Engagement (Pardot) API v5 — prospects, prospect accounts, lists and memberships, campaigns, forms and form handlers, landing pages, emails and templates, dynamic content, visitors and activities, lifecycle stages, bulk exports, imports and actions — registered in Apivom Atlas as 173 routes on pi.pardot.com.

What you can do

  • Prospects and accounts: create, read, update, delete and upsert prospects, prospect accounts, custom fields, tags and tagged objects
  • Lists and campaigns: lists and list memberships, campaigns, list emails, engagement studio programs, lifecycle stages and histories
  • Assets: forms and form fields, form handlers, landing pages, layout and email templates, dynamic content and variations, custom redirects, files, folders, tracker domains
  • Activity: visitors, visits, page views, visitor activities and external activities for engagement scoring
  • Bulk: exports and imports with batches, bulk actions, and the account endpoint for the business unit
  • 173 routes (78 read-only) on pi.pardot.com with the Pardot-Business-Unit-Id header, documented in the AI integration guide (llms.txt)

Use cases

  • Prospect and engagement data in the CRM — Read prospects, their list memberships and recent activities so sales sees marketing engagement next to the account without opening Pardot.
  • Form submissions into an ERP or ticketing flow — Follow form handler and prospect updates and hand qualified submissions to downstream systems the moment they land.
  • Bulk export for analytics — Run export jobs on visitor activities and prospects into your data platform for attribution and funnel reporting.

Account Engagement — still Pardot to most of its users — is Salesforce's B2B marketing automation product, and its v5 API is the full object model behind it: prospects and the accounts they roll up to, the lists and campaigns they belong to, the forms, landing pages, emails and dynamic content they interact with, the visitor and activity records that drive scoring, and the bulk export and import jobs that move data in volume. Apivom Atlas registers 173 of those routes, 78 read-only, on pi.pardot.com; Salesforce SSO issues the token through a Connected App and every call names the business unit in the Pardot-Business-Unit-Id header. No Apivom product workflow uses Account Engagement today — no Apivom product reads or writes Pardot — so the connector is catalogued for customers running Pardot who want Apivom products scoped against their prospect data.

Authentication

A Connected App on your Salesforce org (consumer key + secret) and your My Domain instance URL. The caller runs the OAuth 2.0 flow and sends the access token as Bearer; the instance URL becomes the per-request base URL. Apivom Atlas forwards, logs and stores nothing.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Is this the same as Salesforce Marketing Cloud?

No. Account Engagement (Pardot) is the B2B marketing automation product on pi.pardot.com; Marketing Cloud Engagement is the separate B2C platform on marketingcloudapis.com with its own connector in this catalogue.

Does any Apivom product sync with Pardot today?

No. Apivom's own marketing automation runs on Apivom's platform and has no Pardot connection. This connector exists so a Pardot customer can scope a sync or export with us; none runs today.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.