Here is an outline of what we plan on doing before we ship the API:
Implement comma delimited list filters instead of form arrays
Implement /reviews endpoint (read only; srs state before evaluation, wrong answer counts)
Implement /level_progressions endpoint (timestamps of important events such as unlocked_at, started_at, passed_at, completed_at, abandoned_at [for resets])
Change handling of resets (records still persist, but data cleared out. Should address this issue.
Add radical SVG (and PNG) to subject radical objects (will be used as the primary visual for radicals)
Implement soft deleting
Proper API documentation
And items we will add, but wonât hold back the API release:
Add vocabulary audio and sentences (this is pending API terms we are getting draft up)
Switched over to comma delimited list filters instead of form param arrays for multi element values (See doc for examples under the filter section)
Added /reviews endpoint
Added /level_progressions endpoint
Updated the way user resets are handled, which affects the API. assignment and review_statistic objects of level greater than Userâs new level will just have their data wiped out with the defaults and the updated_at timestamp will be touched.
I guess this would handle when individual user data is no longer relevant, but what about when you remove content from WaniKani? Is there any way from the API to see if content was deleted?
I havenât built scripts with the old or new API, so maybe nobody actually needs that. But I was curious.
Such a huge fan of the changes! Thank you!
Is there a radical content overhaul in the works as well? Iâve heard about this multiple times, but never from an official source.
We arenât the best people to ask about content changes. Thatâs more @anon20839864 and @koichi domain.
The API v2 is mainly concerned with technical changes. I can tell you from the technical end we are moving towards using SVG for the primary radical visuals instead of using a missmash of custom fonts and existing unicode. We will distribute the SVG (and PNG) via the API, and will include unicode as secondary information if it exists.