Potential Upcoming Changes to WaniKani API

[seanblue]

@Hubbit200

I’d be inclined to believe (and would hope) that that was just a badly worded way of saying that they don’t want the API to be used by someone to pre-fetch / store WaniKani data (such as kanji info, mnemonics, etc.) and then distribute / provide it to users, rather than what I assume is your interpretation of it meaning creating something that makes use of API calls while the user is using it

Hopefully!

@MadAsgardian

You’ll often see posts here asking why WK is broken, neglecting to mention they’re using a depricated third-party app or haven’t updated their scripts in months. This is extra work for WK’s team. Is any third-party app officially approved by WK?

@anon99047008

Not a one.

Everything in this e-mail exchange is the exact same stance they have had the entire time I’ve been around.

I think this is an unfair comparison. The public API is completely different from scripts that rely on internal code or HTML structure. If a third party app is solely relying on the public API in accordance with the API documentation and guidelines, then it should never break. If it breaks it’s likely because WaniKani broke the API contract, whether intentionally or due to a bug, and that would be WaniKani’s fault, not the fault of the app developer. The whole point of a public API is that it has a defined contract that doesn’t change. On the other hand, many scripts break because they are relying on internal code which WaniKani has no obligation to keep as-is.