ApivomApivom
Get Demo

Salesforce Marketing Cloud Engagement API Connector

Salesforce Marketing Cloud Engagement REST APIs — transactional e-mail and SMS sends, Journey Builder events and interactions, Content Builder assets, data extension rows, contacts, MobilePush, async imports, audit events and Event Notification Service callbacks — registered in Apivom Atlas as 116 routes on your tenant subdomain.

What you can do

  • Transactional Messaging: e-mail and SMS send definitions, message sends and delivery records (22 messaging routes)
  • Journey Builder: event definitions, fire entry events, list/create/delete interactions, journey details (21 routes)
  • Content Builder: assets, files, salutations, categories and asset queries (14 routes); data extension row upserts, sync and async (12 hub routes)
  • Contacts, attribute groups and schema; MobilePush locations and messages; SMS keywords, opt-ins and MO queue
  • Platform: Event Notification Service callbacks and subscriptions, async import jobs with validation results, audit and security events
  • 116 routes (43 read-only) on {subdomain}.rest.marketingcloudapis.com, plus the SOAP endpoint and the v2 token/discovery/userinfo routes

Use cases

  • CRM events enter a journey — Fire a Journey Builder entry event when a deal is won or a contract renews so the customer joins the onboarding or renewal journey with the CRM attributes attached.
  • Transactional notices from your systems — Send order confirmations, appointment reminders or one-time codes through Transactional Messaging e-mail and SMS, and read the delivery record per recipient.
  • Data extensions kept current — Upsert contact, consent and segment rows into data extensions on a schedule — synchronously for small batches, asynchronously for bulk — so audiences match the CRM.

Marketing Cloud Engagement — the former ExactTarget — is Salesforce's cross-channel marketing platform for e-mail, SMS and push at volume, and its REST APIs cover everything an external system needs to feed it and send from it: Transactional Messaging for triggered e-mail and SMS with per-recipient delivery records, Journey Builder events that enter a contact into a journey and the interactions behind them, Content Builder assets, data extension rows written synchronously or asynchronously, contact and attribute-group management, MobilePush locations and messages, SMS keywords and opt-ins, async file imports with validation summaries, audit and security events, and the Event Notification Service that calls your endpoint back on sends, bounces and opens. Apivom Atlas catalogues 116 of these routes, 43 of them read-only, with the tenant subdomain applied per request so one connector serves REST, SOAP and auth hosts. No Apivom product workflow uses Marketing Cloud Engagement today — Apivom's own marketing automation runs on Apivom's platform — so the connector is available to tenants who run Marketing Cloud and want CRM events, consent or contact data flowing into it, scoped per customer.

Authentication

An installed package on your Marketing Cloud Engagement account (client id + secret) and your tenant subdomain. The caller gets a token at {subdomain}.auth.marketingcloudapis.com and sends it as Bearer; the subdomain sets the REST/SOAP base URL per request. Secret encrypted in your Iris tenant.

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 Marketing Cloud Engagement or Marketing Cloud Next?

Engagement — the subdomain-based platform at marketingcloudapis.com (REST, SOAP and auth hosts). Marketing Cloud Next, the newer edition built on the Salesforce core platform, has its own connector in this catalogue with a Connected App and My Domain instance URL.

Which business unit do the calls hit?

The one the installed package's token is scoped to. Marketing Cloud issues tokens per business unit (account_id); create one installed package per business unit you want to address, or request a token with the target MID in the token call.

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.