Stream Records to Data 360 Connect API

Data 360 Connect API supports streaming ingestion of contact records. Stream data to keep a source system in sync with Marketing Cloud Next in near real-time.

To stream data from an external source, create an ingestion API schema and connector, deploy a data stream, and then create an external client app.

• Create an ingestion API schema file
• Create an ingestion API connector
• Create and deploy a data stream
• Create an external client app

Configure your app to package the streaming data in a way that matches the schema for the ingestion API. A streaming ingestion request can contain multiple records. The maximum payload size is 200 KB.

Each record that you add corresponds to an object in the data array. Include all fields from the schema in the request payload, including optional fields. If there’s no data for a field, pass an empty string or null.

Obtain an authorization token, and then exchange it for a Data 360 token. For more information, see Obtain a Data 360 access token.

To make sure that your request includes the correct syntax and data types, use synchronous record validation.

To validate the records, send them in a POST request to the /api/v1/ingest/sources/DATA_SOURCE_NAME/DATA_SCHEMA/actions/test endpoint.

If there are errors in the request, the response includes information about the issue that caused the error. Address the issues, and then resubmit the data to the validation endpoint. Make sure to resolve all of the issues before you send the request.

When the API responds with a 200 OK message, you’re ready to send the ingestion request.

When your data is properly configured, you can submit it to the Ingestion API. Issue a POST request to the /api/v1/ingest/sources/DATA_SOURCE_NAME/DATA_SCHEMA endpoint.

If the API accepts the data, it responds with a 202 Accepted response.