Bearer authentication support for API tokens
- Announced
- APIs
- rest-bitbucket-cloud
- Severity
- notable, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3387
Bitbucket has added support for bearer authentication for API tokens.
What’s changing: Bitbucket Cloud has added support for Bearer authentication when using API tokens. You can now authenticate your API requests by sending the token in a Bearer authorization header, providing a more standard and secure alternative to Basic authentication.
curl --request POST \
--url 'https://api.bitbucket.org/2.0/repositories/{workspace}/{repository}/commits' \
--header "Authorization: Bearer {api_token}" \
--header 'Accept: application/json'
What you need to do: No action is required. Bitbucket Cloud continues to support both Basic and Bearer authentication for API tokens. If you have existing integrations using Basic authentication, they will continue to work without modification.
For more information on creating and using tokens, see the API tokens documentation.
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.