Send data to Dimension Labs via our REST API. Currently these endpoints are designed for realtime data flows and sending historical data (anything older than the last 24 hours).
The REST API operates off of two primary endpoints which is for incoming messages and outgoing messages.
This design aligns your data with the Dimension Labs conversational data schema that we use to harmonize unstructured omni-channel data.
For customers who are not sending conversational data this detail can be confusing because we typically don't think of sources like 'customer reviews', 'surveys', or 'news articles' in terms of conversations. Most simply put, the rule to follow is that any content generated by a user / customer / source external to the enterprise should always be sent to the incoming messages endpoints.
For example, online reviews are incoming messages from a customer, responses to those reviews (if available) are outgoing from the enterprise. Regarding survey data, treat survey questions as the outgoing messages from the enterprise and the responses as incoming messages. In the case of news articles they should be included as incoming messages.
Option 1: Real-Time Tracker
Sending data to the following endpoints should be done at the time of receiving it. Data sent to these end points should have a timestamp that is within 24 hours of the time of sending.
Incoming Messages
Outgoing Messages
Option 2: Historical Tracker
Sending data to the following endpoints is used when sending data with a timestamp that falls outside of the last 24-hours. Note that any data sent to the historical endpoints will not be processed as part of the nightly enrichment and instead need to be manually backfilled in the platform.
Incoming Messages
Outgoing Messages
Additional Notes:
Some of our integrations have specific platform variables and this information can be accessed within the integration pages themselves.