---
schema_version: "1"
id: 95b6ac8b1d6b579e43897e3332badd46eec51a6d2b7edf0f8240a7bfa65a9f7a
title: Ingestion API
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/data-cloud-int/guides/c360-a-ingestion-api.md
canonical_url: https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-ingestion-api.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: c69f22c545f8391d671b82ab4eb217efce97d3453fa2cb31b75eafe977cfd8e9
products:
  - Data 360 Integration Guide
  - Data 360 Developer Documentation
---
# Ingestion API

You can push data from an external system into Data 360 with Ingestion API. The Ingestion API Connector lets you connect with Ingestion API.

Ingestion API is a REST API and offers two interaction patterns: bulk and streaming. The streaming pattern accepts incremental updates to a dataset as those changes are captured, while the bulk pattern accepts CSV files in cases where data syncs occur periodically. The same data stream can accept data from the streaming and the bulk interaction.

The process of setting up and configuring Ingestion API includes tasks that must be completed by the admin, the data aware specialist, and the developer. Some tasks must be completed before the information and files are handed off to the next role. The roles involved in each stage could differ within your organization. Here's an overview of how to configure Ingestion API data flow in Data 360.

- Agree on the data to be ingested into Data 360 and successfully build a file to bring data into Data 360.
- Set up the Ingestion API connector and share the object endpoint details with developers.
- Create a connected app and align with your developer on the OAuth flow being used to connect to Ingestion API.
- Create the data streams and deploy them.
- Make calls to the object endpoints and start sending data into Data 360.
- Map the data to standard Salesforce objects or custom objects.