KA's currently in the middle of transitioning to GraphQL hence the occurrence of these bugs. The dev's know about this issue, and it should *hopefully* be patched within a week. 

If you'd like, you can always submit a support ticket

Yeah, I know that. Just felt like postin' one of these because it's really annoying. Not their fault of course.

After this transition, will API still be able to be used? Because I think this is when they are supposed to remove it, but I'm not sure.