{"id":85355,"date":"2018-09-13T17:40:47","date_gmt":"2018-09-14T00:40:47","guid":{"rendered":"https:\/\/www.backblaze.com\/blog\/?p=85355"},"modified":"2025-12-11T12:52:58","modified_gmt":"2025-12-11T20:52:58","slug":"backblaze-b2-api-version-2-beta-is-now-open","status":"publish","type":"post","link":"https:\/\/www.backblaze.com\/blog\/backblaze-b2-api-version-2-beta-is-now-open\/","title":{"rendered":"Backblaze B2 API Version 2 Beta is Now Open"},"content":{"rendered":"

\"cloud<\/p>\n

Since B2 cloud storage<\/a> was introduced nearly 3 years ago, we\u2019ve been adding enhancements and new functionality to the B2 API, including capabilities like CORS support and lifecycle rules. Today, we\u2019d like to introduce the beta of version 2 of the B2 API, which formalizes rules on application keys, provides a consistent structure for all API calls<\/a> returning information about files, and cleans up outdated request parameters and returned data. All version 1 B2 API calls will continue to work as is, so no changes are required to existing integrations and applications.<\/p>\n

The API Versions<\/em> section of the B2 documentation on the Backblaze website<\/a> provides the details on how the V1 and V2 APIs differ, but in the meantime here\u2019s an overview into the what, why, and how of the V2 API.<\/p>\n

What Has Changed Between the B2 Cloud Storage Version 1 and Version 2 APIs?<\/h2>\n

The most obvious difference between a V1 and V2 API call is the version number in the URL. For example:<\/p>\n

https:\/\/apiNNN.backblazeb2.com\/b2api\/v1\/b2_create_bucket<\/p>\n

https:\/\/apiNNN.backblazeb2.com\/b2api\/v2\/b2_create_bucket<\/p>\n

In addition, the V2 API call may have different required request parameters and\/or required response data. For example, the V2 version of b2_hide_file<\/code> always returns accountId<\/code> and bucketId<\/code>, while V1 returns accountId<\/code>.<\/p>\n

The documentation for each API call<\/a> will show whether there are any differences between API versions for a given API call.<\/p>\n

No Change is Required For V1 Applications<\/h3>\n

With the introduction of V2 of the B2 API there will be V1 and V2 versions for every B2 API call. All applications using V1 API calls will continue to work with no change in behavior. In some cases, a given V2 API call will be different from its companion V1 API call as noted in the B2 API documentation. For the remaining API calls a given V1 API call and its companion V2 call will be the same, have identical parameters, return the same data, and have the same errors. This provides a B2 developer the flexibility to choose how to upgrade to the V2 API.<\/p>\n

Obviously, if you want to use the functionality associated with a V2 API version, then you must use the V2 API call and update your code accordingly.<\/p>\n

One last thing: beginning today, if we create a new B2 API call it will be created in the current API version (V2) and most likely will not be created in V1.<\/p>\n

Standardizing B2 File Related API Calls<\/h3>\n

As requested by many B2 developers, the V2 API now uses a consistent structure for all API calls returning information about files. To enable this there are some V2 API calls that return additional fields, for example:<\/p>\n