Details
-
Bug
-
Resolution: Fixed
-
Medium
Description
Since the recent DNS update, some of our api calls are failing, but only the calls via OAUTH that use the api endpoint https://api.bitbucket.org/2.0
https://bitbucket.org/api/2.0 actually works just fine.
It doesn't seem to be directly DNS related, as far as I can tell, since our other calls are working fine (it must be able to resolve bitbucket still...) and the api.bitbucket route does work if we use basic authentication...