Join Free
+ Reply to Thread
Results 1 to 4 of 4
  1. #1

    Inconsistency in names of merchants across api endpoints

    Trends API is returning merchants:
    Code:
    ....
    {
    
        "count": 24,
        "value": "Endless.com",
        "extendedFieldValue": "endless com"
    
    },
    {
    
        "count": 20,
        "value": "QVC.com",
        "extendedFieldValue": "qvc com"
    
    },
    ...
    But Products Search API does not find any product for qvc com or endless com. So can you update trends API or dont change these names in Product Search API, its not good for SEO, when we are still changing the URL.

    NETPOOL:
    http://thenetpool.com/search/store/Endless.com 0 products
    http://thenetpool.com/search/store/Endless 114.920 products

    http://thenetpool.com/search/store/QVC.com 0 products
    .....

  2. #2
    We're in the process of normalizing the rest of the brands and merchants. Different networks have different names in their feeds, so we are merging all of the forms and updating all of our data

  3. #3
    how is this coming along? i've noticed trends api is using the old names and products api is using the new names and merchantIds.

    will this api be updated soon, preferably with filterMerchantId ?

  4. #4
    Since trends is based on commission data, we don't have merchantId's for past commissions, but everything going forward does. We are working to see how much of the old data can be converted over. I will make that a higher priority and get a filter in place.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts