possible to query my own library via one of the APIs?

Is it possible to query my own library (preferably via some kind of token, but at minimum via my login credentials) through one of the librarything APIs? I've seen some posts that indicate that might be possible via the "JSON" API (which I assume is the javascript API), but when I try to view the docs for the javascript or basic APIs I get a username/password prompt that my librarything credentials don't satisfy, so I'm kinda lost! Am I barking up the wrong tree, or is this possible: in which case how do I get access to the docs?

Many thanks!

Mike

>1 maspotts: It isn't you. The username/password is a relic from a previous bug. They moved all of the wiki help stuff, and (as I recall) the old bits are causing this. Best that you provide the precise link that's causing this, so that when staff gets around to this (and I remind you that it's Saturday), they can see precisely where the problem is, and update it.

I may come back with a link to the main bug report, but it's been a long day for me, so I'm not sure that I'll make it before tomorrow.

Thanks! These are the urls with the bogus auth dialogs:

https://www.librarything.com/wiki/index.php/LibraryThing_APIs
https://www.librarything.com/wiki/index.php/LibraryThing_JSON_Books_API

both linked from this page:

https://www.librarything.com/services/

(I'm inferring that it is going to turn out to be possible to query my library then?) :)

Thanks again!

>3 maspotts: Information in the old wiki has been transferred to the new one. Use the following URLs until https://www.librarything.com/services/ is updated:

https://wiki.librarything.com/index.php/LibraryThing_APIs
https://wiki.librarything.com/index.php/LibraryThing_JSON_Books_API

Thanks: that's great!

I'm now trying to figure out if I can make my use case work, given the available APIs: I want to create a workflow (using the iOS workflow.io app) that I can use to quickly check whether I have a given *work* in my library. It will snapshot a barcode and extract the ISBN (that functionality is already built into the workflow app), then query LT to map the ISBN to a Work (looks like I can use "What Work?" for that) and then finally search my library to see if I have any editions of that Work already. I don't see how to do that last step yet: the books api doesn't seem to take a Work id as input, and I'd rather not have to download my entire library and filter in place each time (if I can avoid it)!

Am I missing any obvious solutions, by any chance?

PS: This workflow is intended for my own personal use btw, although I'd be happy to share it.

PPS: I know I can already do this using the LT app, but that involves a lot of tapping and typing, whereas I'm trying to achieve a hands-free point-and-shoot based on the barcode (with optional typing of ISB/title/author if there's no barcode).

PPPS: Actually the best solution (in the context of the iOS workflow.io app) would be if this functionality was available via the LT app itself :) Or, failing that, if the LT app made a "search my library" API available to the workflow.io app (many iOS apps do expose APIs which the workflow.io app can take advantage of).

BTW I just noticed that the link from the first APIs page to the blog post describing "What Work?" is a 404:

http://www.librarything.com/thingology/2009/03/new-api-what-work.php

Looks like it should be this instead:

http://blog.librarything.com/thingology/2009/03/new-api-what-work/

Update: that blog post points to this API endpoint (no authentication):

http://www.librarything.com/api/whatwork.php?isbn=0380815591

but it just returns a blank page, for every example I tried.

I reported the broken "What Work" API in a separate topic:

https://www.librarything.com/topic/287164

>7 maspotts: You probably want to report that in the Bug Collectors group. Those posts are monitored by staff, while this group is not.

https://www.librarything.com/groups/bugcollectors

Sorry for the trouble, folks. >4 rodneyvc: was right—these incorrect links were holdovers from the wiki migration. I've updated those links now, and all should be well. No need to open a bug report. Apologies again for the error on our part.

Thanks! And thanks for the redirect to Bug Collectors: hadn't found that!