EAN-13	0000000546720
UPC-A	000000546720
Product Name	Trader Joe's - Natural Beef Jerky (Teriyaki)
Category	Food: Meats
Short Description	4 oz. (113g)
Created	05-22-2010
Modified	09-05-2018 6:00:54pm
MD5	7700b7ca42d5e9658da6be290e009b70
SHA256	e6a632819da9c163112f70f4106aa5c57f547bbab702e643d3395b988533bf4f
Search Google	by EAN or by Title
Query Time	0.0008430

The attributes are somewhat like fields. They are the individual data items that describe each product. Each product entry will have several attributes. There is no telling which attributes will be attached to each product but they all have the same basic format.

Here is an example of one attribute. When accessing the data feed API, you can get your data in XML or JSON format. Here it is displayed in XML format to make it a little easier to read through.

<attribute>
   <field_name>product</field_name>
   <group_name>Over View</group_name>
   <title>Product Name</title>
   <data_type>varchar</data_type>
   <data_type_description>short text</data_type_description>
   <has_linked_text>0</has_linked_text>
   <has_linked_extra>0</has_linked_extra>
</attribute>

In the above example you will find these elements:

• field_name - The unique name used to access this attribute.
• group_name - The name of the data group this field belongs to.
• title - The label we place on the screen when displaying this attribute to users.
• data_type - The database data type we are using to store this attribute.
• data_type_description - More infomation about the data type.
• has_linked_text - Some numeric fields have a text representation. We store the numeric value but if there is linked text, we use a lookup table to display that text instead of the number to the user.
• has_linked_extra - Some numeric fields have an extra text value that goes along with the number. We use a lookup table to display that text in addition to the number.

Hopefully, this helps you understand the data attributes you find in the data feed API.