EAN-130000000007283   EAN-13 barcode 0000000007283
UPC-A000000007283   UPC-A barcode 000000007283
UPC-E00072803   UPC-E barcode 00072803
Product Name0000000007283
Amazon.com12-13-2018 3:45:20pm
UPCChecker.com12-13-2018 3:45:22pm
Upcdatabase.org12-13-2018 3:45:21pm
Created10-02-2015 1:19:19am
Modified12-13-2018 3:45:20pm
MD59b6d24416935dcc48775520a17e66269
SHA2562b986ebc115d1f90e4c2680b91386052d7ac21283dd6026aa6c3079ff7a8acf7
Search Googleby EAN or by Title
Query Time0.0104110

This describes how to use version 3.x of the data feed. Version 2.x of the feed is still supported. Version 1.x of the feed is no longer supported in any way.

Accessing the data requires your account to have an active data feed. This switch can be turned on or off on the data feed page. This is also where you will be able to view your KEYCODE which is required to make calls to the feed.

Main changes from version 2.x to 3.x include (but not limited to)...

Calls to the data feed are made via HTTP GET or HTTP POST requests. There are only a few required parameters when making a call.

Most other parameters are optional and they will alter the way data is returned to you and how your request is processed. You can also pass in your own values that you need carried through. Any parameter that the system doesn't recognize will be returned AS-IS in the status block. This can be handy in situations where you are pulling the data in an asyncronus manor and need extra information passed into your callback routine.

When performing a lookup...

When updating data...

There are some special "get" operations that need no other parameters. You would not use "find" or "update" when using these. Only use the "keycode", "mode" and "get" for these items. These operations are important because many of our elements are data driven and that data changes over time. We normally don't remove attributes or categories but we do often add to the collection.

The returned data can come back in JSON or XML format. In either case the structure of the data is the same. Because it is easier to read, we will be using XML to demonstrate the layout of the result. Here is the data layout. Notice that this is a complex object and some elements have child elements and some elements may be arrays with repeating content.

The easiest way to get the feel of the data is to make several requests using your web browser and ask for the data in XML format. Although JSON is often easier to work with in code, the XML output is often easier for people to read because of the nice markup tags that wrap around each element and the web browser will usually do a nice job of indenting to make it clear which elements are stored within other elements.

Close

Search

Close

Share

Close

Dialog