This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Backblaze supports external integration through an HTTP-based REST API.
Restriction: REST API does not support resume on upload and mdtm(File modification time) changes. You can use the S3 connection endpoint as a workaround.

1. Access through B2 REST API
#

Create App Keys on Backblaze:
1.) Go to the Backblaze website: Link
2.) Log in to your Backblaze B2 Cloud Storage account.
3.) Navigate to the Buckets section (under B2 Cloud Storage).
4.) Click on App Keys in the left-hand menu.
5.) Click Add a New Application Key.
6.) Configure the key:
• Name your key.
• Set permissions (read/write).
• (Optional) Restrict the key to a specific bucket or folder.
7.) Click Create New Key.
8.) Copy and securely store the Key ID and Application Key. ⚠️ The Application Key is shown only once after creation.



Use the KeyId as User name and the Application Key as Password. Also, make sure to provide the corresponding Bucket Name for access.



The URL pattern looks like this:

b2://<<KeyId>>:<<applicationKey>>@api.backblazeb2.com/<<Bucket Name>>/

2. Access through S3 REST API
#

Create App Keys on Backblaze with S3 Permissions:
1.) Go to BlackBlaze Link and sign in to your Backblaze B2 Cloud Storage account.
2.) In the left-hand menu, go to Buckets, then click on App Keys.
3.) Click Add a New Application Key.
4.) In the key creation form:
• Name your key.
• Under Type of Access, select the appropriate permissions (e.g., read-only or read/write).
• ⚠️ Important: Enable the option for S3 Compatible API access by checking the “Allow access to S3-compatible API” checkbox.
• Optionally, restrict access to a specific bucket.
5. Click Create New Key.
6. Copy and securely store both the Key ID and Application Key. ⚠️ The Application Key is shown only once after creation.



Open the bucket settings and use the s3 endpoint URL for S3 connection.



Use the KeyId as User name and the Application Key as Password. Also, make sure to provide the corresponding Bucket Name for access.
The URL pattern looks like this:

s3://<<KeyId>>:<<applicationKey>>@s3.us-west-000.backblazeb2.com//<<Bucket Name>>/

Required flags:
SHA256 enabled on signing (Signing Version 4) and Include SHA256 to request headers (Signing Version 4 related) flags must be checked.



More info about s3 VFS configuration: S3 integration