Medallia Experience Cloud is the fabric over which customer and employee experiences can be captured, organized, analyzed, and actioned. Bringing data into Medallia is essential for making that fabric work for you.

Medallia offers two APIs — Data Import and Custom Import — to bring that data in. They are backed by Medallia’s powerful ETL layer and accessed via the /inbound/v1/{importer-name} and the /inbound/v2/async/{importer-name} endpoints, where {importer-name} identifies the specific Import API being targeted.

Data Import APIs

Data Import APIs are out-of-the-box import connectors that are published as part of Medallia Apps. These are often industry-standard and reflect best practices.

Visit the Medallia Xchange to explore the available Apps and learn more about each data integration that they offer.

Custom Import APIs

Custom Import APIs are unique to each client instance, being developed to match your existing data structures.

Raw data is passed through a preprocessor pipeline and then through an import processor.

Data is published to the Import API using an HTTP POST request.

Medallia's ETL layer also supports pulling data from an SFTP/S3 source, which then routes the data through the Import API.

Processing Modes

Import APIs support three processing modes:

  • Non-concurrent — Each incoming request is processed asynchronously, generally (but not guaranteed) in the order received. Use this mode only for very low-volume feeds.

📘

Feed File API processing mode

The Feed File API is only compatible with the /inbound/v2/async endpoints and is currently available for non-concurrent processing modes. Support for concurrent modes will be added in a future release.

  • Concurrent synchronous — Requests are processed immediately upon receipt. Use this mode for high-volume production feeds.
  • Concurrent asynchronous — Requests are queued for asynchronous processing, but processing occurs in near-real-time batches with some delay introduced to allow for grouping and de-duplication of requests. Use this mode only if advised by Medallia.

Feed File APIs

As of the Summer 2023 release, Medallia introduced a new set of APIs, called Feed File APIs, used to extract the processing results of non-concurrent import requests.

To use the Feed File APIs, set up the v2 Import API in non-concurrent mode. When doing so, API requests to import data will return a feed file ID. The feed file ID identifies an import job to update data in Medallia Experience Cloud.

Use this ID with the endpoints to track processing results at a summary or record level. The results are available once a feed file has completed processing.

Introspection Import API

As of the Fall 2023 release, Medallia introduced a set of introspection APIs used to discover the setup of Import API endpoints to understand import data structures programmatically.

Use this API to discover all available Import API endpoints for a Medallia Experience Cloud instance, or zero in on an individual endpoint to see all the input information that is available for an import job.