---
cuppy_hub: salesforce
cuppy_path: reference/official/data360/data-cloud-dev/guide/dc-deploy_data_kit_components.md
cuppy_section: docs
cuppy_doc: 91JF-KXPT
cuppy_doc_uuid: 3ff741ab-48bd-48d6-8fa7-97454b3d3792
cuppy_permalink: https://cuppy.io/salesforce/d/91JF-KXPT
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-deploy_data_kit_components
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: 127294981ac851f550972561402cfbe3f27f352ad11b8b252f4eb6aec8a0842b
# cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks.
---

> Mirror of <https://developer.salesforce.com/docs/data/data-cloud-dev/guide/dc-deploy_data_kit_components.html> (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.

## Deploy Data Kit Components by Using Deploy Data Kit Components Flow

Deploy all standard data kit components sequentially to a target org using the [Deploy Data Kit Components](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_actions_custom_deploy_datakit.htm) flow. You provide the input for the flow: data kit name, data space name, and the component payload list and send the POST request to trigger the flow. Before moving to the next component, the flow waits for the deployment status of the previous component. The response body contains the `Flow_InterviewGuid`.

This flow is available by using the REST API version 61.0 and later.

| User Permission Set Needed |  |
| --- | --- |
| To deploy data kit components: | Permission set: Data Cloud Architect |

The basic workflow to deploy standard data kit components includes these steps.

1.   [Install your package with a data kit](https://help.salesforce.com/s/articleView?id=data.c360_a_create_install_package.htm&type=5) and its components in a target org.
2.   Trigger the flow by using the REST API.

This is the syntax required for the request payload. The payload can be in either JSON or XML format.

POST

Authorization: Bearer _token_

| Name | Type | Description |
| --- | --- | --- |
| dataKitComponentsInput | sfdatakit__DeployComponentInput | Required. A collection of data kit components to deploy. The collection list contains the payload details about the components. |
| dataKitNameInput | Text | Required. The data kit name that contains the components. |
| dataKitDataSpaceInput | Text | Optional. The name of the data space to deploy the data kit. If a data space isn’t defined, the system deploys the components in the default data space. |

The example shows sample input payloads for different data kit components:

**Data Stream Bundle**

**Connector Framework**

**Ingest API**

**Streaming App**

**Calculated Insights**

**Data Lake Object**

**Data Graph**

**Data Transform**

**DataStream B2C Commerce**

**Identity Resolution**

**Segment**

To find out which Data 360 components are packageable, see [Data 360 Extensibility Readiness Matrix](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_isv_readiness_data.htm). **Deployment Example**

This example request triggers the deploy data kit components flow to deploy the data stream bundle, data lake objects, and data transform components from the ** `MyTestDatakit`** data kit.

`curl https://{MyDomainName}.my.salesforce.com/services/data/v{version}/actions/custom/flow/sfdatakit__DeployDataKitComponents`

**Data Kit Request Body**

**Data Kit Response Body**

*   _REST API Developer Guide_: [Deploy Data Kit Components by Using Deploy Data Kit Components Flow](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_actions_custom_deploy_datakit.htm)
*   _Salesforce Help_: [Data Services Billable Usage Types for Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_data_usage_types.htm&type=5)


---
<!-- cuppy -->
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.
<!-- /cuppy -->