- Ingestion: create, read, update, close or abort bulk ingest jobs and upload CSV batches; manage and test Event API runner profiles for streaming (9 routes)
- Query: run SQL against the lakehouse with the Query API v1 and the paginated v2 (next batch id)
- Profile: read unified profiles and child objects by record id or search key, with calculated insights per record (8 routes)
- Data Graphs and insights: fetch a data graph record and its metadata, list calculated insight metadata and values
- 30 routes (21 read-only) on api.salesforce.com, documented in the AI integration guide (llms.txt)
Salesforce Data 360 API Connector
Salesforce Data 360 (formerly Data Cloud) runtime APIs — Ingestion API bulk jobs and streaming Event API profiles, SQL Query API v1/v2 with batched results, Profile API lookups on data model objects, calculated insights, Data Graph reads, metadata and the universal id lookup — registered in Apivom Atlas as 30 routes on api.salesforce.com.
What you can do
Use cases
- Unified profile beside the CRM record — Look up the Data 360 unified individual and its calculated insights when an account or contact is opened, without building a second profile store.
- External events into Data 360 — Stream behavioural or transactional events from your own systems through the Event API so they land on the right profile.
- SQL extracts for reporting — Run Query API statements over harmonised data model objects and page through the result batches into your warehouse.
Data 360 is the Salesforce customer data platform — the lakehouse where CRM, marketing, commerce and external data are harmonised into data model objects, unified into profiles and enriched with calculated insights and data graphs. Its runtime APIs are the ones an external system touches day to day: the Ingestion API to push records in, either as bulk CSV jobs or streaming events against a runner profile; the Query API to run SQL over the harmonised tables; the Profile API to read a unified customer with its related objects and insights; and the Data Graph and metadata endpoints that describe what is there. Apivom Atlas registers 30 of these routes, 21 read-only, on api.salesforce.com, with a Connected App token exchanged for the Data 360 scope. No Apivom product workflow uses Data 360 today — Apivom's analytics and data products run on Apivom's own data plane — so the connector is catalogued for customers whose unified profiles live in Data 360 and who want an Apivom product scoped against them.
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.
What is the difference from Data 360 Connect APIs?
This connector is the runtime surface — ingest, query, profile, data graph. The Data 360 Connect APIs (separate connector, 196 routes) configure the instance: data streams, data model object mappings, identity resolution, segments, activations and the rest of the setup objects.
Does any Apivom product read from Data 360?
No. Apivom's data products run on Apivom's own data plane. Data 360 is registered so a customer whose profiles live there can scope an Apivom lookup or export against it; nothing of the kind 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.