In Data 360 (Formerly Data Cloud), the Ingestion API expects payloads to follow the structure defined in the object schema and not standard field API names. A common issue arises when payloads are sent using field API names, leading to ingestion failures or records with blank values.
To avoid this, you should download and use the schema definition, send attributes in the field names as defined in the schema. This ensures that the payload structure is accurate and aligns with the API's expectations.
Steps to follow:
Follow these steps to correctly format and send your payload using the Ingestion API.
1. Go to Data 360 Setup:
- Navigate to the Data 360 Setup in your Salesforce environment.
2. Search for Ingestion API:
- Use the search bar to find "Ingestion API."
3. Select Your Connector Name:
- From the list, select the name of your connector.
4. Locate the Integration Guide:
- Scroll to the bottom of the page where you will find the "Integration Guide."
5. Download Schema:
- Click on "Download Schema" to retrieve the full list of objects and field names expected by the Ingestion API.
6. Use the Downloaded Schema:
- Use the names as shown in the schema to send the payload.
Example from downloaded file:
components:
schemas:
personName:
type: object
properties:
identificationID:
type: number
createdDate:
type: string
format: date-time
Note:
If the payload is sent using field API names instead of the schema-defined field names, the system won't recognize the fields or their values. As a result, you'll observe a single row in the data stream with all columns blank. Since the payload lacks valid fields, the ingestion process treats each call as an upsert to the same record, ultimately leading to one record populated with only blank values.
005102709

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.