EAN-139780739331774   EAN-13 barcode 9780739331774
Product NameA Single Shard
CategoryBook / Magazine / Publication
Amazon.comA Buy on Amazon ~ 0739331779
BindingAudio CD
Published05/30/2006
Long DescriptionTree-ear is an orphan boy in a 12th-century Korean potters’ village. When he accidentally breaks a pot, he must work for the master to pay for the damage by setting off on a difficult and dangerous journey that will change his life forever.
Similar Items0024543563396: City of Ember
9781400084968: A Year Down Yonder
9780553494105: Bud, Not Buddy
9781148028507: The City Of Ember (The First Book Of Ember)
9781147750102: The City Of Ember (The First Book Of Ember)
9781145827134: The City Of Ember (The First Book Of Ember)
9781141801855: The City Of Ember (The First Book Of Ember)
9781141373000: The City Of Ember (The First Book Of Ember)
9781141174218: The City Of Ember (The First Book Of Ember)
9781116065039: The City Of Ember (The First Book Of Ember)
9781115445849: The City Of Ember (The First Book Of Ember)
9780935312171: The City Of Ember (The First Book Of Ember)
9780375822742: The City Of Ember (The First Book Of Ember)
9780307243188: Maniac Magee
9781581307702: Single Shard - Teacher Guide By Novel Units, Inc.
9781553194910: A Single Shard (Literature Kit)
9781433210433: The Bronze Bow
9780061808128: To Kill A Mockingbird
9781427204455: The Cricket In Times Square (Chester Cricket And His Friends)
9781400085552: Number The Stars
9780804168434: The Book Thief
9780743931588: A Guide For Using A Single Shard In The Classroom (Literature Unit (Teacher Created Materials))
9780618025435: A Guide For Using A Single Shard In The Classroom (Literature Unit (Teacher Created Materials))
9780062285300: The One And Only Ivan Cd
Created11-12-2012 2:34:25pm
Modified05-07-2017 10:18:52pm
MD53ca15302d681f3b81de404678e3cdb1f
SHA2569fbc017789a71296ab94c359e5b46696e48c8562d8c6131027f78e92acd9dcb9
Search Googleby EAN or by Title
Query Time0.0390232

Article of interest

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.

IMPORTANT: Starting with version 3.2, we have a new property and a new way of dealing with product images. Read about it here.

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