Create a Master App Key for the Partner API
    • Dark

    Create a Master App Key for the Partner API

    • Dark

    Article Summary

    App keys control access to your Groups. The master app key has all bucket capabilities, access to all Groups, and has no restrictions or expiration. The master app key is necessary to create an authorization token for Partner API calls.

    For all of the Backblaze API operations and their corresponding documentation, see API Documentation.

    Create a Master App Key

    1. Sign in to your Backblaze account.
    2. In the left navigation menu under Account, click Application Keys.
    3. In the Master Application Key section, click Generate New Master Application Key.
    4. Click Yes! Generate Master Key.
    Because your master app key is shown only when you generate it, save your master app key in a secure location if you plan to use it more than once.

    The term "master application key ID" was formerly called an "account ID." If you use an integration in which the terminology was not updated to reflect this change, the master application key ID works in place of your account ID. For a standard app key, you can use that key's keyID in place of an account ID.

    You can find your master app key ID on the Application Keys page.

    Obtain an Authorization Token

    Use the master app key with the b2_authorize_account operation to create an authorization token.

    When you call the Partner API to obtain an authorization token, you must include the version number in the URL. For the Partner API, you should specify version three (v3) in your call. It is important to note that version three is specific to the Groups functionality broadly and the Partner API specifically. If your application makes use of the Backblaze B2 Cloud Storage Native API for other calls, the token that you obtain for the Partner API will not work for Native API calls because the Native API continues to require version two (v2) of the API.

    Use the Token for Partner API Calls

    Use the token in the header for Partner API calls:

    Was this article helpful?