We've made the Datastores API publicly available on Github. You can find it here:

Datastores API

We provide the following API calls:

Datastores allow you to upload and store large volumes of data, within MXO , providing access to that data in real-time, for use in decisioning. You can use the stored data to personalize offers and provide customers with recommendations.

You decide what data you want to include in a Datastore, ensuring MXO has access to the right data at the right time and enabling you to provide a customer with the optimal customer experience. That data might include information currently stored in your CRM, Campaign tools, or other SOR.

Storing the data within MXO provides you with optimal performance in terms of making that data available to MXO for real-tme decisioning. Attributes stored in Datastores are encrypted at rest at the attribute level, and again at disk level.

You can create and populate multiple Datastores, depending on your requirements.

This enables you to provide MXO with access to different types of data using different schemas. You define the schema when creating your Datastore.

When you create a Datastore, you can specify both a primary key and secondary key as references for your data.

The primary key identifies a specific set of data in your datastore and is used to look up data for decisioning. Typically, this is a customer identifier such as a Customer key.

The secondary key provides an additional way to look up data. This may be an identifier that can reference multiple records in your datastore. For example, productid.

If you want to reference non-customer data for use in decisioning, such as additional information about your Propositions, you can provide a fixed value for the primary key, a fixed primary key. This enables MXO to retrieve the same set of data for all customers. If you use a fixed primary key, you must also provide a secondary key.

For example, a sports team might want to store information about its players. Using a datastore allows you to update the data in your own external system, without having to duplicate those changes in MXO .

You can include up to 40 columns of data in a Datastore. Up to five of those columns can be the larger size, with a 4000 character limit per column. All other columns have a 500 character limit.

You can retrieve up to 50 rows of data per customer key or fixed primary key on a single API request.

A company want to make use of MXO 's fast access data capabilities, by providing MXO with customer reference data, currently stored in their CRM, for use in real-time decisioning.

For more information about this example use case, see Step 6 - Use Datastore data in an Eligibility Rule.