cannot use bitbucket api token to call conflict endpoint

[Gia Gao]

I used bitbucket API token to call conflicts endpoint, but it returns 403, I have assigned all scope in the bitbucket list but still not working.

It works well for other bitbucket endpoints

Is it a bug? or I need other way to call conflicts endpoint?

[Mark C]

Hi @Gia Gao

Welcome to the community.

To use access tokens, you will need to use it as an authorization bearer header instead of basic authorization.

Here's an example curl command:

curl --request GET \
  --url 'https://api.bitbucket.org/2.0/repositories/{workspace}/{repository}' \
  --header 'Authorization: Bearer <repository_access_token>' \
  --header 'Accept: application/json'

Regards,
Mark C

[Gia Gao]

Hi Mark, thanks for the reply. 

I have tried with bearer type, but still not working, and I am not using the repository access token, I am using the API token for calling the bitbucket API, I assume they are different things.

[Mark C]

Hi @Gia Gao

I see. Could you try the Curl command mentioned here instead?

curl --request POST \
 --url 'https://api.bitbucket.org/2.0/repositories/{workspace}/{repository}/commits' \
 --user '{atlassian_account_email}:{api_token}' \
 --header 'Accept: application/json'

Regards,
Mark C

[Gia Gao]

Hi @Mark C 

I tried with curl command, it works and returns 302 found, but I don't understand why it is still not working in postman though I am using exactly the same headers. Is there anything I missed?

[Kristian Walker _Adaptavist_]

Hi Gia,

I have clicked the Request Assistance button so that Atlassian support can look into this issue for you.

I hope this helps.

Regards,

Kristian

[Gia Gao]

Thanks！