Image
EAN-139780747594147   EAN-13 barcode 9780747594147
Product NameQueste
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0747594147
SKUNU-GRD-00588213
Price New5.63 US Dollars    (curriencies)
Price Used1.18 US Dollars    (curriencies)
Width1.54 inches    (convert)
Height7.09 inches    (convert)
Length5.08 inches    (convert)
Weight17.6 ounces    (convert)
AuthorAngie Sage
BindingPaperback
Published04/13/2017
FeaturesUsed Book in Good Condition
Long DescriptionFOR USE IN SCHOOLS AND LIBRARIES ONLY. Septimus and Jenna are headed for the mysterious place where all Time meets and the place where they hope they will be able to find Nicko and Snorri, who were trapped back in time. But Merrin Meredith has darker plans for Septimus.
Similar Items9780554342641: Septimus Heap: The Magykal Papers
9780061704161: Septimus Heap: The Magykal Papers
9780060577339: Magyk (Septimus Heap, Book 1)
9780061242441: Septimus Heap, Book Six: Darke
9781148593630: Septimus Heap, Book Five: Syren
9780738821689: Septimus Heap, Book Five: Syren
9780061568206: Septimus Heap, Book Five: Syren
9780060882129: Septimus Heap, Book Five: Syren
9780427004454: Physik (Septimus Heap, Book Three)
9780060577391: Physik (Septimus Heap, Book Three)
9781116026979: Flyte (Septimus Heap, Book 2)
9781116026962: Flyte (Septimus Heap, Book 2)
9780766184381: Flyte (Septimus Heap, Book 2)
9780439900119: Flyte (Septimus Heap, Book 2)
9780060577360: Flyte (Septimus Heap, Book 2)
Created11-16-2012 7:15:12pm
Modified04-13-2017 4:56:53pm
MD5841f02c36564df5fe4ac2c212206542b
SHA256da8e9784bc285590daaacb8efd97c8122f2d1053bc45dc62778be3df7f773d83
Search Googleby EAN or by Title
Query Time0.0304880

Article of interest

This feature started with version 3.3 of the API and it allows you to update many fields of a product in one call. Prior to this, each attribute for a product was updated in a separate call, causing the process to be a bit slow.

It is important to note that bulk updates only work with JSON formatted data. Because of this, you can leave the mode=json out of your call.

You should use a POST call instead of a GET to avoid over running the length limits that can be found when sending long URLs.

Required Parameters

Optional Parameters

Each entry in the fields array is made up of keys and data. Some keys are required and some are optional depending on the data type being used. These entries mirror the single field update calls used when updating data one field at a time.

Details of the fields entries

An example of the JSON to update multiple fields for a single product

The order of each field in the array doesn't matter. We will process them in sequence but sequence makes no difference. So you don't have to sort them or place them in any partcular order.

You can actually update multiple products at the same time. To do this, you still need to pass some basic information for the first product in the required fields (see above). But in the fields JSON, you create an array of products, each with a fields sub-array. The product listed in the update field would be ignored for the most part but must still be valid. So it can be hardcoded when using this method as long as it is a vaild EAN code. 

An example of the JSON to update multiple fields for multiple products

It doesn't matter if you are updating a single product or multiple products. When the response is returned, the top level status is always going to be code 200 assuming your required fields passed the test. Then you will see an array of products even if you only passed in one to be updated. Each product entry and each field entry will have a status so you will know if individual updates worked or failed. This includes the imageURL you passed.

An example of the JSON returned after an update call


The return results in each img or status field

Examples of how to update images

Here are two examples of updating images. These both use a GET that you can test in your browser as soon as you insert your keycode. No other fields are being updated in these two examples. You would normally want to use POST in your code because there can be issues with very long GET requests losing data off the end. But these examples will work properly as GET or POST.

This first example is updating a single product image in simple mode using only form variables (no JSON)

https://eandata.com/feed/?test=1&v=3&keycode=[YOUR-CODE]&update=0025192251344&field=*bulk*&imageURL=https://schworak.com/image/0025192251344-Jaws.jpg

This next example is also updating a single product image, but because it is using JSON, you could pass multiple products in the outer "fields" array. Notice that each inner product block also has a "fields" list when using JSON.

https://eandata.com/feed/?test=1&v=3&keycode=[YOUR-CODE]&update=0025192251344&field=*bulk*&fields=[{%22ean%22:%220025192251344%22,%22imageURL%22:%22https://schworak.com/image/0025192251344-Jaws.jpg%22,%22fields%22:[]}]

Close

Search

Close

Share

Close

Dialog