Migrating from App Password to API Token - Authentication failed

[Brandon OBrien]

I currently have several repositories with BitBucket and I'm trying to switch from using App Passwords to the new API Token.  I already  have the repositories cloned to my desktop and have been working on them for years.

I'm just trying to make the transition but I keep getting authorization failed notices.

I've tried both of the following from the command line in MacOS Terminal when I'm in the directory:

`git remote set-url origin https://{my_username}:{api_token}@bitbucket.org/{workspace}/{repo_name}.git`

and 

`git remote set-url origin https://{my_username}@bitbucket.org/{workspace}/{repo_name}.git`

(i obviously used my actual username, worskpace and repo_name in the curly brackets above)

Both of which give me the following error after I try to push a commit to bitbucket:

`remote: You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated.
fatal: Authentication failed for 'https://bitbucket.org/{workspace}/{repo_name}.git/'`

What do I need to do in order to get this to work?  The API token is just a normal API token without any scopes.  I would think this means I can use it for any of my repositories using any command (like a push).