--- cuppy_hub: salesforce cuppy_path: reference/official/data360/data-cloud-dev/guide/dc-dev-overview.md cuppy_section: docs cuppy_doc: ZNYK-PQAV cuppy_doc_uuid: 314e73bb-5d75-4248-9a1f-de7b61de05db cuppy_permalink: https://cuppy.io/salesforce/d/ZNYK-PQAV cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/data-cloud-dev/guide/dc-dev-overview cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: 0b44f96a6668164ee7ebb79adaec6d581a790e12cd60d3df411a397c49f9d443 # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- > Mirror of (Salesforce, Data 360 Developer Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers. ## Data 360 Development Cycle Use APIs and SDKs to integrate data, query data, and manipulate calculated insights and profiles. For reference information about APIs, SDKs, and data model objects (DMOs), see [Data 360 Reference Guide](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_intro_cdpapis.htm). This diagram shows the API and object integration points within Data 360 and the Salesforce Platform. The diagram separates the components that relate to a Data 360 tenant from the components within the Salesforce Platform. ![Image 1: API and object integration points within Data 360](https://a.sfdcstatic.com/developer-website/sfdocs/data-cloud/media/data-cloud-dev/DataCloud_IntegrationPointsFlowChart.png) Here’s what the diagram covers in detail. 1. After the data is ingested from data sources, it’s represented as a set of data lake objects (DLOs). Using the Customer 360 data model, an administrator maps the DLO fields to a data model object (DMO). Next, an administrator unifies the data by using identity resolution rules, which results in a Unified DMO. 2. The Data 360 API is part of the Data 360 tenant, and the API calls access the tenant-specific endpoint in the tenant. The Data 360 API includes REST resources for running queries, accessing profiles, calculated insights, identity resolution rulesets, data source records, and metadata. 3. The Connect API is part of the Salesforce Platform. Like the Data 360 API, Connect API includes REST resources for running queries, accessing profiles, calculated insights, identity resolution rulesets, data source records, and metadata. Connect API also provides Apex classes through the `ConnectApi` namespace so that you can perform a subset of these operations. 4. Using data actions, calculated insights and engagement data can trigger automation in the Salesforce Platform using Platform Events, in Marketing Cloud, or in an external system using a webhook. **See Also** * [_Data Cloud Reference Guide_](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_intro_cdpapis.htm) * [_Data Cloud Connect REST API_](https://developer.salesforce.com/docs/data/connectapi/overview) * _Salesforce Help:_[Data Cloud Features](https://help.salesforce.com/s/articleView?id=customer360_a.htm&type=5) * [Custom App Development](https://developer.salesforce.com/docs/data/data-cloud-dev/guide/custom-app-dev.html) * [Integration with External Systems Using Data Actions](https://developer.salesforce.com/docs/data/data-cloud-dev/guide/custom-app-dev.html#integration-with-external-systems-using-data-actions) --- You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.