I was tinkering with setting up a new Backblaze B2 bucket and ran into an issue. If I create the application key via the b2 command line app to limit the permissions, I can’t seem to get it to connect:
2026/06/02 14:48:22 TRACE BACKBLAZE_CALL [0] URL request 'POST https://api.backblazeb2.com/b2api/v1/b2_authorize_account' returned 400 This request is not currently supported on API version number 1
Looking a little more into it, it seems that they are now on the v4 API. There are rules on bucket restrictions when using the latest cli (which uses the v4 API I believe). Someone had a similar issue when using rclone:
This comment seems to suggest that “even though the application key was created with a single-bucket restriction, it is not compatible with API versions below v4”.
I haven’t dug into the Backblaze API, but curious if there’s any plans to upgrade and use the latest API?
For now I will switch to using the S3 compatible method of connecting.
