Does Bitbucket Cloud SCM support using an api_token in the Authorization header without Base64 Encod

[Pankaj Kumar Malviya]

Does Bitbucket Cloud SCM support using an api_token in the Authorization header without Base64 encoding and without the Basic prefix?

I have been using Bitbucket Cloud SCM APIs, such as repository fetch and others. When I pass the API token directly, without the Authorization header, the API works fine.

However, I am unable to find documentation for this approach and believe the documentation is missing.

The documentation states:
App passwords have been replaced by API tokens.
As of September 9, 2025, app passwords can no longer be created. Use API tokens with scopes instead. All existing app passwords will be disabled on June 9, 2026. Migrate any integrations before then to avoid disruptions.

Please suggest the correct way to use the API token:

Authorization: Basic Base64Encode({username}:{api_token})

OR

Authorization: {api_token} (There is no documentation for this method, but it currently works.)