GET DEMO Chat

 

 

An Overview of the Indix Product API

Synchronous APIs, Asynchronous APIs, On-Demand APIs, Bulk APIs… which one is best suited for your use case and how are both enterprise businesses as well as small companies leveraging Indix product data to make game changing business decisions? Well, keep reading to find out.

When we launched our V1 API Beta nearly two years ago, we had big aspirations. But I would be lying if I said we knew things would take off the way they have. Now in our third iteration (V2), the Indix APIs have evolved into a comprehensive set of endpoints that are a must-have solution for any brand, retailer, developer, or commerce enabler.

Our synchronous real-time APIs enable the user to query and filter our database, using a wide array of inputs, to obtain summary level information or more detailed offers and/or catalog specific data. Each and every product in our database is comprised of a broad set of attributes and features which we normalize to our own taxonomy. Once a product enters our database, we give it a unique Indix master product ID (MPID) which will always point to the best version of that product. We are constantly improving our product content and this MPID is what you will use to keep up.

Offers-specific endpoints return information around the sale of a particular product or group of products using a plain text query, MPID, UPC, MPN, SKU, URL, brand ID, store ID, or category ID as the input. Here is an example of the output:

apiscreenshot11

The offers API allows you to take advantage of our best in class data ingestion, classification, and matching algorithms to fully understand a product’s footprint in the ecommerce landscape.

Catalog-specific endpoints return the attributes and descriptors that differentiate your product offering from the competition. Once again, you are able to query using plain text, MPID, UPC, MPN, SKU, URL, brand ID, store ID, or category ID, and a sample output will look something like this:

apiscreenshot21

Catalog information can range from the code based identifiers for a product (e.g., UPC, MPN, SKU) to the detailed key:value pair descriptors (e.g., color:blue, size:large) that differentiate the particular product at a variant level. With over 35 billion offers and tens of thousands of attributes, our customers pick Indix because of the comprehensiveness of our data. And when we are missing a product match or attribute, they have the confidence that we will capture and expose that information faster than our competition.

Along with our real-time endpoints, we also offer asynchronous APIs for On-Demand and Bulk use cases. With over 800 million products in our database, it would be impossible to refresh the entire catalog on a daily basis. We use a combination of machine learning logic and customer priorities to determine how often we refresh key data points for a given product (e.g. price, promotion, availability). That said, On-Demand fills the need for customers who require a higher cadence of price and availability information for key products, or during high volatility segments of the year. On-Demand gives you the power of having one of the best and brightest data science teams in the world at your fingertips.

Our Bulk endpoint enables access to enormous quantities of data by submitting an asynchronous job and allowing a nominal amount of time for us to fetch that information. With our Bulk endpoint, our customers can obtain a million products’ worth of information in less than one hour.

USE CASES

To better understand how customers use a combination of endpoints to solve rather complex commerce quandaries, it’s best to use real examples. For instance, a large Fortune 500 technology company uses our bulk endpoint on a daily basis to access offers and catalog data for all products sold by them. Then they create a series of data-driven dashboards for their brand managers and merchandising teams. Based on this information, each user is able to submit more curated On-Demand queries for specific high-impact products. Finally, the real-time endpoints are used for ad-hoc competitive research and analysis allowing the retailer to stay on top of the latest assortment and promotional trends.

Another Indix API success story is of a smaller yet incredibly successful commerce company focused on selling out of stock and excess inventory through flash sales. This company infuses Indix data throughout their value stream to make better decisions around buying and selling inventory. By using our real-time APIs to identify products with sparse descriptors, they have seen a step level efficiency gain compared to previously used manual product identification methods. Once a product’s commerce footprint is understood, the real-time catalog endpoint is used to obtain the detailed attributes that define the given product. During the flash sale, the On-Demand endpoint is used multiple times a day to maintain price competitiveness. This is a great example of Indix product data being infused throughout the lifecycle of a product and bringing value every step of the way.

Since launching our V1 API Beta nearly two years ago, we’ve listened and learned, adding a multitude of endpoints, features and filters based on these learnings. This will surely continue as we strive to create the most comprehensive database of product information in the world. Stay tuned as we explore some of these use cases further in the coming weeks. We urge you to jump on for the ride!

  Download the Pervasive Commerce White Paper
Get API Access Today

2 thoughts on “An Overview of the Indix Product API”

  1. kannan Chetlur says:

    Dear Sathya
    Sorry for sounding ignorant.
    If for example an airline needs to forecast its sales using predictive analysis , would Indix’s product be relevant.
    regards
    Kannan

  2. Shankar Sundaram says:

    Hi Kannan, first off your question is not ignorant at all. Currently our data is focused around physical products but services like you describe are very interesting as a potential future offering.

Leave a Reply

Your email address will not be published. Required fields are marked *