166
An API
Long-term
Nadia
Mar 14, 2021
An Application Programming Interface (API) for people/developers to hook StoryGraph data into their own websites or build their own apps on top of our platform.
Comments
An Application Programming Interface (API) for people/developers to hook StoryGraph data into their own websites or build their own apps on top of our platform.
This would be huge! But as a dev, I know it's not a small project ๐ Just tossing in my support for this idea. Was browsing Libby and was thinking how nice it would be to have my storygraph wishlist linked.
professordaddy I didn't really understand what this request meant but this example is awesome! yes this would be great. Especially cause I found out by accident that if you delete the libby app from your phone you lose anything you've tagged as something you want to read when you re-download it. learned that one the hard way and was very sad. would be nice to have just one TBR/wishlist that could link through different platforms!
Looking forward to this so someone can make a koreader plugin that pushes my progress to StoryGraph.
jarulf Not only this, but we could also pull data from story graph into koreader database and have them synced (for example when you read on different mediums, physical, audiobooks, etc.)
Really wish this was higher priority than just "Long-term". I'm sort of stuck with GoodReads, at least partially, until this is in place... and I'd love to dump GoodReads. Calibre integration would be excellent.
gizmotoy Sorry. Lots to finesse on the core product first!
Nadia I get it. It is the last remaining major feature for me, though. Hopefully โlongโ term isnโt too long.
I work in data/BI and would love to use my Storygraph data for personal dashboards (and to practice my API skills)
Would love to have an API so I could create either an integration with calibre or even better, directly from my Kobo device :)
Would love to be able to pull in any of my StoryGraph data, especially currently reading, to my personal Notion dashboard.
snslayer Came here looking for exactly this!!!
momalwaysreads I wanted to add onto this! Definitely something that's on my radar, especially to track upcoming releases and seeing how long it takes me to read books with a timeline.
snslayer I'm sooo curious about this ๐
I need this so bad for my blog.
Just a +1 on this, mainly so that IFTTT or Zapier could feed updates on reading progress or finished books to DayOne or a spreadsheet. IDK if kindle finish can be a source to IFTTT/Zapier and then feed to TSG, but I'd still love it even if TSG can be source-only.
Heck even a public RSS feed for a specific user would be great. Love for an automatic way for me to push my reading history into my discord bot.
This is the only thing keeping me on goodreads
That'd be great! Maybe I'd be able to let my ebook reader and audiobook player automatically update my reading stats that way.
Was hoping for an API so I could build a coda.io pack. Not keen to maintain tracking in multiple places.
Would love an api, looking to try to build a slack intergration app similar to /booky with goodreads, but with Storygraph instead.
Would love to be able to build a sync to my Obsidian Vault. Plus build fun video games on top of this ๐
joehart ๐๐๐
Imagine if StoryGraph was featured in one of your talks. ๐ญ๐
A Libby App/ StoryGraph integration is basically my dream pairing, and an API would help make that possible.
bookcasey ditto! Would love a libby story graph integration!
Would this connect StoryGraph to Kindle possibly?
milpeaches I don't think so, unless somebody else found a way to create their own app for that.
I would love an api so I could combine my libib to mark which ones I owned easier :)
Iโd love to embed my current reads or other data on my personal website. A basic REST API to read my own profile data would be slick!
Just upvoted this and wanted to add that queries about an API for TSG are popping up more often on Mastodon now, often from users of Calibre. So when this feature DOES get an ETA, it will have a lot of eager beta testers. ๐
Seconding this. Found my way here because a colleague used GR API to connect with our local library in the city so that he'd get know when items in his TRL were available there. Was thinking about doing my own for SG, but hopefully sometime in the future :fingers_crossed:
Enabling book bloggers to hook-up to StoryGraph would be a separate feature and does not necessarily require an open API. Are their any associated costs per Ingram or other ISBN database pulls?
Having watched first hand the challenge of Groupon rewriting their code to enable an API ...oof. Yes, there is a huge advantage to enabling devs to build off StoryGraph, but there's also a massive expense. It might be useful to talk with some people at Twilio who ran their developer side marketing (aka hackathons) or other experienced Developer Evangelists on the cost/benefit as well as to see if there's an option for outside help.
This would be cool for book bloggers like me! Iโd love to be able to display some of my profile automatically on my website.
I would also love an API! I use Readwise to track my highlights, and I pull the highlights into my Obsidian daily note. I'd love to also pull in StoryGraph data to show my reading progress even if I didn't add any highlights.
Just want to add my support of this idea. I would love to be able to build a series tracking app off of TSG shelved books and allow others to be able to use it. With an API, you get a cool community of developers making things that may never make it down the pipeline but are useful for all. With the small dev team for the actual site, it can go a long way in enhancing what TSG can do and be used for.
Just wanted to jump on and also say this would be so useful for various interoperability things. Specially I started thinking about this again for Calibre integration but could be very useful for integration with all sorts of social and book platforms.
Just to share a quick comment, I think an API could go a long way to enriching StoryGraph by bringing over folks who tinker and develop additional tools, apps, etc. With Goodreads winding down its API usage, it's a good time to strike while the iron's hot.
Is there any sort of ETA for this implementation? I know that the team at The StoryGraph is working hard on many improvements across the board, and I'm very happy to see them come to fruition. However, I have a programming friend who's looking to convert from GoodReads to StoryGraph with his Discord bot for our book club. We all love TSG and cannot wait to sew in its use within the server on a more permanent level to what we already utilize with this platform.
Thanks again for all your hard work!
Hello! Thank you for this. There isn't an ETA. I write a little bit about that here: https://roadmap.thestorygraph.com/changelog/our-public-roadmap-is-live-.
I'm a team of one app/web developer at the moment and this isn't a priority, though we of course do want to cater to people who need it!
It would be awesome if some time next year some work was started on it, and having your feedback is helpful when thinking about priorities!
Yes! This would be so helpful for app developers!
This would be a game changer!
I want a calibre plug-in so badly
This is why I started thinking about the API again. I used to use the Goodreads API all the time and had an extensive tag and shelf synchronisation.
Thatโs why I donโt leave Goodreads so far.