| EAN-13 | 0013308154221  |
| UPC-A | 013308154221  |
| Product Name | Assorted $1.50 Dollar Days |
| Short Description | Each |
| Created | 07-01-2006 |
| Modified | 09-25-2017 4:11:47pm |
| MD5 | 824b67dbaf9b07992d51ac66014e69fc |
| SHA256 | 6de2796d8aedd055c8d8e24cfed4d6c62ca722686b788e10936b6cd923e6a1b4 |
| Search Google | by EAN or by Title |
| Query Time | 0.0055101 |
An article of interest
Making use of the tools we offer
Accessing the data feed using a REST format
The data feed API is URL based, but if you prefer to use the REST interface, you can do most things using that method.
Your API key should be in the request header "x-api-key" but will also work on the URL if you prefer using keycode=????????
When accessing the API using REST, the URL needs to be in this format:
https://eandata.com/feed/{version}/{action}/{dataID}/
version: The API version you are trying to access starting with the letter "v" followed by the version number as an integer. (ie: v3 or v2)
action: The action you wish to perform. Not all actions are currently available using the API. The ones that work currently are:
- find: perform a data lookup
- search: perform a text search
- asin-to-ean: convert an Amazon ASIN into an EAN
- imdb-to-ean: convert and IMDB ID into an EAN
dataID: This is the data you are searching for. For "find" this is an EAN or UPC code. For "search" this can be any text properly encoded for he URL.
To get your data back as XML, put "application/xml" in your "accept" header. If you prefer JSON (the default format) you can leave off the "accept" header or send "application/json". You can also include your preference on the URL using mode=json or mode=xml but using the request header is the preferred method.
We will continue to add more REST interface features in the future so be sure to check back on this page every once in a while.
*** Updating data via the REST interface is not ready yet but will require test=1 on the URL as the first variable if you are testing your application to prevent actual data updates. Placing it later on the URL could cause this variable to be skipped if you have errors in your URL.