API V2 Alpha Documentation


Thanks for the very detailed report. We should investigate on Monday @oldbonsai


A fix is now live. Can you check to see if it the behavior is corrected?


Looks all good to me. Thanks very much for fixing it so soon! :slight_smile:



I am looking to import users learned vocab from Wanikani so they will be excluded from an automated Furigana tool. I see the v1 docs look good. https://www.wanikani.com/api

It is very hard to search this entire thread for examples of the endpoint.
In a CURL request (or requests) how would I get a users learned vocab?

A few CURL examples would be very helpful.



This is exactly what I want but it is V1. I do not want to get sun setted on :slight_smile:


I’m not at my computer, so I can’t do a sample curl request. But all you really need is something like this as a template:

curl 'https://api.wanikani.com/v2/subjects' -H "Authorization: Bearer your_apiv2_key_here"

/v2/subjects contains item info, and /v2/assignments contains the user’s status for each of those items. The records returned by those two endpoints are linked by their corresponding subject_id.

Since both of those endpoints are paginated (i.e. only 1000 records at a time), you’ll need to look at the pages.next_url field for the url to read the next 1000 items.

EDIT: If you plan to get incremental updates, you’ll need to learn to use the updated_after parameter in the URL.


Awesome. That will work! Looking forward to the docs that have those bits. Saw the one Github repo from v2 docs that may need updating from people on here. Thanks again!


Sounds similar to something I have been working on, but I just hardcoded each level for now.

But it raises the question for me of what the proper/legal way to do it is. Is there a terms of use violation for just storing the constants locally?


Not sure about that. Mine allows users to exclude words they learned from any site with mouseover/hotkey, also restrict generation of Furigana by JLPT level. Still doing beta :wink:


Suggestion: With the recent overhaul of content, it would be very helpful if the payload in the GET /users response included a boolean property indicating whether the user has configured their profile to display the old mnemonics or not.