EAN-139780758229359   EAN-13 barcode 9780758229359
Product NameEaster Bunny Murder (Lucy Stone Mysteries)
CategoryBook / Magazine / Publication
Short DescriptionHeight:0.91 inches / Length:8.82 inches / Weight:0.77 pounds / Width:5.46 inches
Amazon.comA Buy on Amazon ~ 0758229356
Price New8.45 US Dollars    (curriencies)
Price Used1.76 US Dollars    (curriencies)
Width1.04 inches    (convert)
Height8.49 inches    (convert)
Length5.61 inches    (convert)
Weight12.32 ounces    (convert)
AuthorLeslie Meier
Page Count304
FeaturesUsed Book in Good Condition
Long Description
Lucy Stone has always loved covering the annual Easter egg hunt for the Pennysaver. Hosted by elderly socialite Vivian Van Vorst at Pine Point, it's a swanky event where the eggs are as likely to contain savings bonds as they are jelly beans. But when Lucy arrives, a man dressed as the Easter Bunny emerges, only to drop dead moments later. Lucy discovers the victim is VV's grandson, and soon learns that not all is as it seems at idyllic Pine Point. Always a social butterfly, VV has been skipping lunch dates with friends, and her much-needed donations to local charities have stopped with no explanation. Maybe she's going senile, or maybe her heirs are getting a little too anxious to take over her estate...
Similar Items9780575033665: Christmas Carol Murder (A Lucy Stone Mystery)
9780802817662: Sweet Tea Revenge (A Tea Shop Mystery)
9780425252888: Sweet Tea Revenge (A Tea Shop Mystery)
9780758229335: Chocolate Covered Murder (A Lucy Stone Mystery)
9780307629791: Christmas Carol Murder (A Lucy Stone Mystery)
9780758229311: English Tea Murder (Lucy Stone Mysteries)
9780152019174: Red Velvet Cupcake Murder (Hannah Swensen Mysteries)
9780738803722: Red Velvet Cupcake Murder (Hannah Swensen Mysteries)
9780470094495: Red Velvet Cupcake Murder (Hannah Swensen Mysteries)
9781410440099: English Tea Murder (Lucy Stone Mysteries)
View 12 more similar items
Created11-20-2012 11:48:34pm
Modified06-24-2017 1:15:54pm
Search Googleby EAN or by Title
Query Time0.0217710

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.