ApivomApivom
Get Demo

Salesforce Data 360 Connect API Connector

Salesforce Data 360 Connect REST APIs — the /ssot configuration surface: connections and connectors, data streams, data lake and data model objects and their mappings, data transforms, identity resolution, calculated insights, segments, activations and activation targets, data graphs, data spaces, data kits, search indexes, data clean rooms, machine-learning models and document processing — registered in Apivom Atlas as 196 routes.

What you can do

  • Sources: connections and connector types (21 routes), data streams, data lake objects, private network routes
  • Modelling: data model objects and mappings (14), data transforms (12), identity resolutions (6), calculated insights (6), data graphs and data spaces
  • Activation: segments (10), activations and activation targets (11), data action targets and data actions
  • AI and collaboration: machine-learning models (17), search indexes and document processing for retrieval, data clean rooms (13), data kits
  • Query and limits: SQL and SOQL-style query endpoints, metadata entities, universal id lookup and instance limits
  • 196 routes (89 read-only) under /services/data/v{version}/ssot on your My Domain org, documented in the AI integration guide (llms.txt)

Use cases

  • Configuration as code across orgs — Read data streams, mappings, transforms and identity rules from one instance and apply them to another so sandboxes and production stay aligned.
  • Segment and activation operations — List segments, trigger activations and watch activation targets from an operations console instead of clicking through Setup.
  • Setup audit and drift detection — Snapshot connections, data model objects and calculated insights on a schedule and alert on changes that nobody planned.

Where the Data 360 runtime APIs move records in and out, the Connect APIs build and operate the instance itself: every object you would otherwise configure in Data Cloud Setup is exposed as a REST resource under /services/data/v{version}/ssot. Connections and data streams describe where data comes from; data lake objects, data model objects, mappings and transforms describe how it is harmonised; identity resolution rules unify profiles; calculated insights, segments, activations and activation targets turn them into audiences delivered to marketing, advertising and service systems; data graphs, data spaces, data kits, search indexes, clean rooms and machine-learning models round out the platform. Apivom Atlas registers 196 of these routes, 89 read-only, on your My Domain org with a Connected App token. No Apivom product workflow uses the Data 360 Connect APIs today — Apivom does not provision or operate Data 360 instances for customers — so the connector is catalogued for teams that automate their Data 360 setup and want that automation visible and logged in an Apivom tenant.

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.

Connect APIs or Data 360 APIs — which do I need?

Use this connector to configure the instance (streams, mappings, identity resolution, segments, activations). Use the separate Data 360 APIs connector to ingest records, run queries and read unified profiles at runtime. Most integrations need both.

Does Apivom set up Data 360 for customers?

No. Apivom's own data platform is used by its products; Data 360 remains your Salesforce project. The routes are registered so your setup automation can run through an Apivom tenant where it is useful, scoped per customer.

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.