Image
EAN-139781420131819   EAN-13 barcode 9781420131819
Product NameHighland Lover
LanguageEnglish
CategoryBook / Magazine / Publication
Amazon.comA Buy on Amazon ~ 1420131818
SKU155385009738381594955109
Price New3.89 US Dollars    (curriencies)
Price Used3.81 US Dollars    (curriencies)
Width0.97 inches    (convert)
Height6.74 inches    (convert)
Length4.14 inches    (convert)
Weight5.92 ounces    (convert)
AuthorHannah Howell
Page Count352
BindingMass Market Paperback
Published07/03/2012
Long DescriptionA reckless need to break free of his family led Gregor MacFingal Cameron on a quest for a rich bride, only to fall prey to kidnappers and be tossed into a cold cell. But he is soon joined by a frightened young woman, Alana Murray who makes him regret his mercenary search for a wife. After a daring escape, he joins Alana's journey to rescue her sister. Temptation soon leads to seduction, and promises are made, but hard to keep. Alana knows the bond forged by danger and desperation has earned her an ally willing to fight for her sister's cause. But Gregor's tantalizing seduction leaves her breathless, and she seizes her one chance to experience true passion before an arranged marriage seals her fate--never anticipating the inescapable intensity of a man and a love that will change everything.
Similar Items9780821774298: Highland Fire
9780821774274: Highland Groom (Zebra Historical Romance)
9780821773970: Highland Bride (Zebra Historical Romance)
9780821768174: Highland Knight (Zebra Historical Romance)
9780821766149: Highland Vow (Zebra Historical Romance)
9780821760956: Highland Honor
9780759287983: Highland Conqueror
9780759287624: Highland Hearts
9780739434383: Highland Angel
9780446616164: Captive Heart
View 12 more similar items
Created07-16-2013 2:05:46am
Modified10-08-2017 5:38:48am
MD5398c7e776474c80d701b2a98a168bdfa
SHA256d39c26dcea41e494c5a21653a3e54135f55eda5de1fdc35c6d803b54758cec44
Search Googleby EAN or by Title
Query Time0.0205920

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...

When deleting 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