This issue has been identified, and we're currently working on a fix. If you encounter this error, we recommend retrying the request to the endpoint you're using after a few seconds. After a couple of retries, the request should return a successful response