Image
EAN-13	9780811879644
Product Name	The Worst-Case Scenario Survival Handbook: Paranormal
Language	English
Category	Book / Magazine / Publication
Short Description	Paperback
Amazon.com	Buy on Amazon ~ 081187964X
SKU	081187964X-11-XBZN
Price New	2.96 US Dollars    (curriencies)
Price Used	0.25 US Dollars    (curriencies)
Width	0.5 inches    (convert)
Height	7 inches    (convert)
Length	5.13 inches    (convert)
Weight	6.4 ounces    (convert)
Author	David Borgenicht, Ben H. Winters
Page Count	192
Binding	Paperback
Published	05/11/2011
Features	Used Book in Good Condition
Long Description	On hit TV shows, in best-selling books, blockbuster films, video games, and comics, pop culture has been overrun by hordes of vampires, zombies, werewolves, ghosts, wizards, and other paranormal creatures. Luckily, the authors of the Worst-Case Scenario Survival Handbook series are back with all-new, expert advice designed to help readers fend off the furry, fanged, freaky, and frightful. This classic handbook format is packed with new illustrated instructions for crucial scenarios ranging from the domestic (How to Host a Cocktail Party When Your House is Haunted) to the scary (How to Survive a Zombie Attack in the First Day, First Week, and Long Term) to the practical (How to Break Up with a Vampire).
Similar Items	9780756916398: The Worst-Case Scenario Survival Handbook: Man Skills 9780590509336: The Worst-Case Scenario Survival Handbook: Man Skills 9780811853132: The Worst-Case Scenario Survival Handbook: Life 9780811845380: The Worst-Case Scenario Survival Handbook: Extreme Edition 9780439153836: The Worst-Case Scenario Survival Handbook: Extreme Edition 9780811825559: The Worst-Case Scenario Survival Handbook 9780152004583: The Worst-Case Scenario Survival Handbook 0765145025553: The Worst-Case Scenario Survival Handbook 9780811842303: Worst-Case Scenario Survival Handbook: College 9780811831314: The Worst Case Scenario Survival Handbook: Travel View 7 more similar items
Created	11-16-2012 12:06:02pm
Modified	06-01-2017 8:14:30am
MD5	7767a6447dfb23a730a4b50597eaab43
SHA256	18e2796eb3e364570452b3f48a7a5684cf81e74f7b5ba2a934ed5414dee72792
Search Google	by EAN or by Title
Query Time	0.0228112

Article of interest

This describes how to use version 2.x of the data feed. Version 1.x of the feed is no longer supported in any way.

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.

You must always pass these...

• keycode : 16 digit code (your app doesn't need to log in, it only needs the keycode)
• mode : json, xml or csv

When looking up data...

• find : 8, 12 or 13 digits to search for
• comp : yes/no (optional, defaults to "yes". if "no" skip the company lookup)
• pending : yes/no (optional, defaults to "no". if "yes" pending updates may be returned)
• search : normal/deep - if this is omitted or any unexpected value, a normal search will be performed. A deep search  will take longer than a normal search. Our web bots will make an effort to locate more information about the product. This only happens if we have no information on file already. This can take a couple extra seconds or up to a minute. Your app needs to be able to deal with this delay. (defaults to normal)

When updating data...

• update : 8, 12 or 13 digits to search for
• field : The product field to update (sorry, no company updates allows)
• value : The new value (will go into a pending area until validated)

• Only products information can be updated (no company info)
• Only update one field per request
• Update may be ignored if other pending updates exist
• Error result status is returned if updating a locked product
• To upload product images, see this blog article.

To download the list of categories...

• get : category

The feed return data structure...

All fieds are returned regardless of the result. Check the status code before trying to make use of any of the data returned. As long as the code you send is valid (not an error) the barcode field will hold a link to a baccode graphic. If you get a 404 error because we can't find the product, you may still get valid data in the company section so you may want to check the company name field.

You will need to make requests for the content of the long description in a separate call get=long_desc to the GET or POST request. In this case, you will only get back the long description. The return structure of the long description data looks like this...