Xcode Cloud + Bitbucket integration returns HTTP 403 during App Store Connect connection

Hello Apple Developer Community,

I’m trying to connect a Bitbucket repository to Xcode Cloud through App Store Connect, but the connection consistently fails with an HTTP 403 response.

Environment Product: Xcode Cloud / App Store Connect SCM: Bitbucket Cloud Integration: App Store Connect → Xcode Cloud → Bitbucket Date: September 15, 2026 Time: 3:51:44 PM IST / 10:21:44 UTC Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E HTTP Status: 403

I have Administrator access in both App Store Connect/Apple Developer and the Bitbucket workspace/repository.

What I have already checked

I contacted Bitbucket Support and provided them with the browser network/HAR capture from the failed connection.

Bitbucket confirmed that the App Store Connect Bitbucket callback returned HTTP 403. However, they explained that the browser capture cannot show the subsequent server-to-server communication between Apple/Xcode Cloud and Bitbucket.

Bitbucket therefore asked Apple to investigate the server-side request using the Apple Correlation ID and timestamp.

They indicated that the failure could potentially involve:

Apple rejecting the Bitbucket OAuth callback. Apple receiving the callback but failing while processing it. A server-to-server request from Apple to Bitbucket returning an error. An OAuth authorization-code or access-token exchange failure. The 403 being generated by Apple's callback service. My question

Has anyone experienced a similar HTTP 403 when connecting Bitbucket Cloud to Xcode Cloud through App Store Connect?

Also, is there a known Xcode Cloud/App Store Connect requirement for Bitbucket OAuth or access tokens that could cause this type of 403 even when the user has administrator permissions?

If an Apple engineer is able to review the server-side logs, could the following details help identify the failure?

Apple Correlation ID: TIIRWMUD46W7OMZ7UDWXBRFI7E Timestamp: September 15, 2026, 10:21:44 UTC HTTP Status: 403

Bitbucket has already confirmed that the relevant server-to-server communication is not visible in the browser HAR, so I’m trying to determine which side is generating the 403 and at which stage of the OAuth flow it occurs.

Any guidance from someone familiar with Xcode Cloud + Bitbucket integration would be greatly appreciated.

Thank you.