How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Backblaze Authorization API

Account authorization and token management

Backblaze Authorization API is one of 7 APIs that Backblaze publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authorization. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 2 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version v4.

Requests are made against a single base URL, https://api.backblazeb2.com.

2 operations 2 paths 6 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v4
Server
https://api.backblazeb2.com
Authentication
HTTP Bearer, HTTP Basic
Resource Areas
1

Authentication & Security 2

Backblaze Authorization API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (ApplicationKeyAuth). It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

  • ApplicationKeyAuth — Authorization token obtained from b2authorizeaccount
  • BasicAuth — HTTP Basic auth using applicationKeyId as username and applicationKey as password

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Authorization 2

Account authorization and token management

GET
/b2api/v4/b2_authorize_account
Backblaze B2 Native API Authorize Account
authorizeAccount → 200401
POST
/b2api/v4/b2_get_download_authorization
Backblaze B2 Native API Get Download Authorization
getDownloadAuthorization body → 200401

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are AllowedCapabilities (4 properties), AuthorizeAccountResponse (4 properties), ErrorResponse (3 properties), GetDownloadAuthorizationResponse (3 properties). Each schema is shown below with its type and property counts.

GetDownloadAuthorizationRequest
object
3 properties 3 required
ApiInfo
object
API endpoint information
1 property
AuthorizeAccountResponse
object
Response from the b2authorizeaccount operation
4 properties
GetDownloadAuthorizationResponse
object
3 properties
ErrorResponse
object
Standard B2 error response
3 properties
AllowedCapabilities
object
What the credentials allow
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

backblaze-authorization-api-openapi.yml Raw ↑

Other APIs Backblaze publishes across the network.

Backblaze S3-Compatible API
Backblaze Application Keys API
Backblaze Buckets API
Backblaze Files API
Backblaze Large Files API
Backblaze Notifications API
Where this information came from

This is an independent, third-party profile of Backblaze Authorization API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.