Hi! We have identified that it is indeed a problem on our side. The fix should be implemented during this week. I will notify in a separate message when it has been deployed.
Thank you for the report and helping us!
An unrelated suggestion: please consider moving away from using api-proxy.pipedrive.com. We return company domains in OAuth token responses that should be used instead. More information in the documentation.
api-proxy domain could be deprecated in the future, so if possible, migrate already now 