We have identified the issue on one of our API servers and fixed it accordingly. Now the API operates normally again.
