We pushed some changes out this morning which drastically increased the perfomance of the current (v1) of the API. Some end points are seeing a couple magnitudes of reduced response times, notably the vocabulary end point.
Before it would time out when doing a non filtered request for users who have progressed significantly. To get around this developers did multiple filtered requests. This is no longer required since the endpoint should no longer tiemout.
I don’t remember… it’s been a few years since I tried it. But it was fairly common for it to fail the first time due to browser timeout. Retrying usually worked fairly quickly, I’m guessing because the information was pulled into server cache.
I’m somewhat hesitant about switching to unfiltered requests for vocab since it still takes a while, especially since splitting it up works so much faster. But maybe I can increase it from 5 levels per request to something higher. I’ll experiment later.
Hey @viet uh…think I’ve run into a small change in the API. Occasionally, A user’s burned field in their user_specific in the vocabulary_list, which was previously a boolean, now contains null. Please let me know if I’m wrong about this, but Kaniwani is now puking up a fair few errors on user’s trying to unlock lower levels when this is the case. Seems pretty sporadic though, I haven’t encountered it myself yet.