The issue has been resolved and the API is running smoothly again. We'll continue to monitor closely.
We're investigating some errors coming from the API & working on an immediate fix.
12:29 EST - 19 December 2016