I did some digging into the WK API error problem today, and the API appears to be broken when a updated_after query results in multiple pages of results. For those not familiar with the API, it has pagination, which means that if a query results in 1000 or fewer results, it just returns them normally. However, if there are more than 1000 results, the API just returns the first 1000, plus a link to the next “page” of results to get more.
I only use the custom leech review script I wrote once a week (every Saturday morning), and it of course it has to update its local review database each time by doing an updated_after query for reviews since the previous week. However, I did a lot more reviews than usual last week and must have hit 1000 reviews in one week for the first time, causing multiple pages of results to be returned, which broke the API.
If this is correct, than the API was probably always broken, and it’s just that last week was the first time I actually did enough reviews to run into this bug. Imagine doing so many reviews you break Wanikani!
There have been some times I was forced to skip a week or two of leech reviews due to vacation, but in those cases, I was also doing negligible reviews for the same reason, so I probably never hit 1000 even after a two or three week gap in those cases.
Sun Dec 26 2021:
Time spent: 29m
Reviews completed: 143
Reviews remaining: 4097
Reviews in next week: 4515 (+418)
Reviews in next month: 4926 (+411)
Accuracy: 76.22% (109/143)
Accuracy on resurrected items: 88.51% (77/87)
Accuracy on non-resurrected items: 57.14% (32/56)
Current item counts:
Apprentice: 2574
Guru: 1528
Master: 531
Enlightened: 653
Burned 1797
