SourceTree Add/Edit Account with API Token

Hi @Thomas Krenn ,

Can you try clearing your credential manager? There have been some discussions around this, but here's one example of how things will/might look: https://community.atlassian.com/forums/Sourcetree-questions/Setting-up-API-Token-with-SourceTree/qaa-p/3261626#M47510

As for how to create an API token, can you try following these steps (once you clear the credential manager): https://community.atlassian.com/forums/Sourcetree-questions/Unsure-how-to-use-the-API-password-with-sourcetree/qaa-p/3184506#M46897

Cheers,
Tobi

Your second guess is the right one. The kibsa.at address is your Atlassian account, and that's what belongs in User Email.

The other one isn't an account at all. That's the bit tripping you up. In a remote like https://name@bitbucket.org/workspace/repo.git you're looking at git's own user@host syntax, where the part before the @ is your Bitbucket username and bitbucket.org is the host it's talking to. It reads like an email because the URL format makes it look like one, but there's no Atlassian account registered under it. So if that's what went into the field, the error was doing its job when it said "must be used with an atlassian registered email".

So if the failed attempt had the bitbucket.org one in that field, give it one more go with kibsa.at. If you'd already used kibsa.at and it still bounced, you've hit the shakier side of SourceTree's token handling and I'd stop there. OAuth is working for you, it doesn't lean on a credential helper at all, and someone on a near-identical thread last week ended up in the same place and it's held since.

That error is coming from SourceTree's account check, not from git. It calls api.bitbucket.org/2.0/user to read your profile, and that call wants your Atlassian account email as the username. Git wants x-bitbucket-api-token-auth instead, which is why the same token sails through the URL method while the Accounts tab keeps refusing.

Your version is fine, so don't chase that. API tokens are supported from 3.4.24 on Windows and you're on 3.4.31.

I'd suspect the account entry rather than the token. The message is SourceTree telling you the identity it sent wasn't an Atlassian-registered email, and an entry first created back in the app-password days can still be carrying your Bitbucket username underneath, with Refresh API Token quietly reusing it. Remove the account completely. Then add it again with Auth Type set to API Token, your Atlassian email in User Email, token in the API Token field.

If it still bounces after a clean re-add, switch that account to OAuth. SourceTree holds the token itself there, so no credential helper is involved and there's nothing cached to fall back on. Someone hit the same runaround on a near-identical thread last week, went OAuth, and reported back that it's held up since.