LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  May 2009

CODE4LIB May 2009

Subject:

Re: Amazon product API will require a crypto signature

From:

Jonathan Rochkind <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 11 May 2009 10:51:10 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (92 lines)

In fact, I believe that library-sector developers have asked Amazon and 
been told that their use is allowed. But definitely, there's no 
guarantee this will always continue be true. The terms of use don't seem 
to have substantially changed to me, but they could always start 
enforcing them more strictly -- for new accounts created to use the 
Product Advertising API, it looks like there actually will be a manual 
review step where Amazon staff approves you or doesn't, which never 
existed before.

So, while I'm still using it, I'm also keeping in mind what backup plans 
I have if they ever ask me to stop.

Here are the things I use Amazon API for, with alternates:

1) To take an ISBN, and look up more complete metadata for it.  
Alternatives:
    A) Google Books Data API (free for everyone; yes, there is a GBS API 
which is explicitly authorized for non-javascript access. GBS API will 
also allow you to find OCLCnums and LCCNs that correspond to an ISBN, 
when GBS has that data, which it often does thanks to the OCLC 
relationship.)
    B) WorldCat API (OCLC members)
    C) Books In Print API, although BiP seems to be making up their mind 
about whether they'll throw this in for free with an existing BiP online 
subscription, or charge extra for it.
    D) OpenLibrary? (Is this true?)

2) Cover images. Alternatives:
    A) CoverThing
    B) Google Books
    C) OpenLibrary


3) To find an ASIN, in order to make a link to the Amazon page.  
Ironically, this is actually what the API is _for_, and what Amazon 
would actually WANT you to do, but it's the thing that's least 
replaceable.  If you have the ISBN, and if you assume the ASIN is the 
same as the ISBN, you don't need an API.  This is often true, but not 
guaranteed to be true, and I think will become less true when the new 
ISBN-13 namespace starts to be used.   In my case, I use the ASIN to 
identify if Amazon has a search-inside and/or limited-excerpts 
available, but the API actually doesn't support that, I've been 
screen-scraping all along for that, once I have the ASIN.



Tim Spalding wrote:
> They're also tightened up the API in various ways, and renamed it the
> "Amazon.com Product Advertising API." Although I know of no case when
> Amazon has shut down a library, it would be hard for any to claim
> their site had "as their principal purpose advertising and marketing
> the Amazon Site and driving sales of products and services on the
> Amazon Site."
>
> I think it's a terrible mistake for them. Their marginal cost is zero;
> they don't need to do this. Data openness was a key factor in Amazon's
> rise. And that was when thee were no other options. With viable other
> options just emerging—Open Library, Google, at least—now is hardly the
> time to make it less attractive.
>
> Tim
>
> On Mon, May 11, 2009 at 9:40 AM, Jonathan Rochkind <[log in to unmask]> wrote:
>   
>> The Amazon products API keeps changing it's name, and has just been changed
>> to Amazon "Product Advertising API" -- it's the one you use to look up books
>> in Amazon and get metadata for them, though.
>>
>> It looks from an email I got from Amazon that ss of August 15th, you'll need
>> to cryptographically sign requests to this API, to have them responded to.
>> It looks like kind of a pain.
>>
>> I think a bunch of people on this list may be using this API. Beware.
>> Instructions for how to cryptographically sign requests the way they want
>> can be found here:
>>
>> http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/Query_QueryAuth.html
>> http://docs.amazonwebservices.com/AWSECommerceService/latest/DG/rest-signature.html
>>
>>
>>
>> Like I said, it's looking like a pain to me. There are lots of details to
>> get right. If you URI-escape not _exactly_ the same way they do, it's not
>> going to work. Etc.
>>
>> Jonathan
>>
>>     
>
>
>
>   

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager