Does (or will) Bunpro have a public API?

[imasaru]

Hey, there! I’m sure this is unnecessary to say, but this problem seems to have been fixed now.

[atrpid]

@Jake Would it be possible to include upcoming grammar (including ghost reviews) with a better granulation in the Bunpro API? The response could either comprise of review items with datetimes (preferably) or (after feeding the API with the desired granulation as a parameter) number of reviews in each timeframe.

[Yalgie]

Hey, @Jake I couldn’t seem to see any other updated threads about the API - I was wondering if any new endpoints have been added in? I was interested in having a /known_grammar endpoint to get all the grammar the user has learned/started if that’s possible. I can grab the most recent 50 items with the current endpoint which I can work with if not though. Cheers!

[Jake]

Hey! Right now bringing the public API up to date is on our internal roadmap but is a ways down the road yet.

[jamie.kapilivsky]

@Jake Just wanted to check in to again to see if the public API has made any progress up the roadmap yet. Thanks for all your hard work!

[Sully22]

I am also curious about this. I created a small review stats tool(https://nihongostats.com) for BunPro and Wanikani using the APIs from the previous iOS app. But it appears those APIs have been deprecated and removed so my tool no longer works with BunPro .

It would be awesome to have a public API documented.

[sergiop]

Any updates regarding the API? The links I saw regarding the API have 404 error.

[danyramdas]

Any updates regarding the API?

[simias]

Wanikani uses API and scripts as an excuse for not improving the core product (they don’t even have a first party mobile app in 2023). Offering a public API is a big
commitment in terms of stability (one that WaniKani broke when they decided to disable the review API a few months ago, rendering many community scripts and tools useless).

As long as Bunpro continues improving the core product and implement features that users ask for, I’m fine with it remaining a fully closed product. The script/API culture surrounding WaniKani is a mess and not something that other products should seek to emulate, IMO.

Of course my argument here is a bit of a strawman, Bunpro could keep improving the platform while also providing a stable public API, but that’s a non trivial development effort and I think it’s absolutely reasonable for the devs to make that a low priority.

@DamirH

I would definitely like to see a public API to allow for stuff like WKs timeline etc. I believe that the Bunpro UI is a bit unintuitive and I think user scripts would help alleviate that a great deal.

That’s specifically what I don’t want to happen. If the bunpro UI is bad then it needs to be fixed, not worked around with third party tools that can break at any moment because they’re not officially supported by the platform and the maintainers do it as a hobby. WaniKani is borderline unusable for me without at least 3 different userscripts. That’s not normal.

[iamomgphil]

I think getting the reviews you have to do could be a game changer, i built a little study tool and can help with a dash board

[godwheel]

I love WaniKani and the API has opened up some cool third party feature and I love how I can take some of my progress to other apps. For example if I learn a Kanji in WaniKani the furigana is not offered. This helps strengthen my Kanji retention because my mind is doing the work for those I know.