1 / 3
May 2018

We now offer a new API to obtain your current product data directly from our system, which is primarily useful for programming a dynamic site to populate item details from our database -- e.g., having the price displayed on your sales page always match the item's current price set in Seller Admin, rather than having to update it in Admin and in your site separately. More ambitious developers could also use this to program a storefront-builder CMS plugin, or a product summarizer, etc.

To view the API data format and example query code (in Curl, PHP, Node.js, Ruby, and Python), simply sign into Seller Admin and click Products API in the sidebar; note this is only available via our new Admin interface, which you can enable for your account via the Try New Features button when you're logged in.

On the API panel you can also choose whether the API will return data for all of your products or just "public" ones which you have listed in an E-junkie Shop in our site's Marketplace25. We also don't provide a Javascript code example, as that method would necessarily expose your secret API key in your JS code, so this approach is not recommended if you want to keep any of your product details reported by the API confidential.

Making use of this API is a matter of general programming skill beyond the scope of support we can feasibly provide, but we'd be glad to help clarify aspects of the API to developers making use of it -- e.g., explaining which variable names correspond to their respective Admin settings, etc.

  • created

    May '18
  • last reply

    Aug '22
  • 2

    replies

  • 2.4k

    views

  • 2

    users

  • 1

    like

  • 1

    link

4 years later

Just took a look at the new API. A few questions:

  1. Is there a way to regenerate our API key? For example, if our key gets exposed and we want to retire the old key and regenerate a new key.
  2. Will the API be versioned at some point? Versioning would help keep existing functionality while creating new versions without breaking prior versions. Ex: https://api.e-junkie.com/api/v1/
  3. As the current version is still beta, should we expect breaking changes when using the API?

Thanks!

  1. We don't have a self-serve way to regenerate your Key, but if need be our Devs could probably do it manually for you by request;
  2. We don't expect any need to version the Products API, but in case that ever changes, something like you proposed would be a good approach;
  3. There should not be any breaking changes (and if there were, that would be a good case to version the API), only adding functionality (e.g. adding properties not currently supported) and fixing functionality that may be discovered to be broken already.