Usage Reports for Partner API Accounts and Groups
- 08 Oct 2026
- Print
- DarkLight
Usage Reports for Partner API Accounts and Groups
- Updated on 08 Oct 2026
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Usage Reports provide a daily, detailed ledger of Backblaze B2 Cloud Storage usage for standalone Accounts and Groups managed through the Backblaze Partner API. These reports help calculate customer fees based on stored data and applicable transaction fees.
Usage Reports for standalone Accounts and Groups can be enabled by contacting the Backblaze Support Team or your account representative.
Organizations configure Usage Reports through the Enterprise Web Console. For Organization-specific instructions, see **Usage Reports for Organizations**.
For all Backblaze API operations and their corresponding documentation, see API Documentation.
When Usage Reports are first enabled, Backblaze automatically backfills reports for the previous seven days. This means up to one full week of historical usage data will be available immediately upon activation — no additional action is required.
Usage Reports for Organizations
Organizations configure Usage Reports through the Enterprise Web Console rather than the Partner API reporting workflow.
If an Organization contains multiple Billing Accounts, reports are configured separately for each Billing Account.
For configuration instructions, report formats, destination Account requirements, and credential options, see Usage Reports for Organizations.
Usage Reports for Groups
Three CSV file types related to usage are generated daily for each Group: “Groups,” “Locations,” “Usage”, and “Audit”. The “Usage” file contains the amount of storage used and other usage data, while the “Audit” file is a minimal version of the “Usage” file for auditing purposes. The “Groups” and “Locations” files provide lists of files generated daily, primarily for reference purposes.
- “Groups” file (file name:
usage.groups.csv): contains a list of Group identifiers and the corresponding “Locations” file names that you can expect to be generated for the day. - “Locations” file (file name structure:
usage.group-{groupId}.reportingLocations.csv): contains a list of regions. - “Usage” file (file name structure:
usage.group-{groupId}.{reportingLocation}.csv): contains the usage totals generated by each Group member for a given day. - “Audit” file (file name structure:
usage.audit-group-{group_id}.{reporting_location}.csv): a minimal version of the “Usage” file for auditing purposes. This file contains only thebucket_id,date,stored_gb,downloaded_gb, anduploaded_gbfields.
Usage Reports are generated only for the Group members who are located within the same data region as the Group account.
Files for each day are organized into folders named by the {date} (YYYY-MM-DD format) and are uploaded to a special bucket. That bucket is auto-generated by Backblaze once files are available for the Usage Report-enabled administrator account. The bucket name follows the format "b2-reports-$ACCOUNTID" where “$ACCOUNTID” is a Backblaze administrator account identifier.
Groups File
The Groups file name is usage.groups.csv. The file contains a header row and the column names and descriptions below.
| date | Dates in YYYY-MM-DD format in UTC. |
| group_id | Group identifier, integer. |
| reporting_locations_file_name | File name of each "Locations" file to expect per Group. |
Locations File
The “Locations” file name convention is usage.group-{group_id}.reportingLocations.csv. The file contains a header row and the column names and descriptions below.
| date | Dates in YYYY-MM-DD format in UTC. |
| group_id | Group identifier, integer. |
| reporting_location | Region. For example, us-west or us-east. |
| report_file_name | File name for each "Usage" file to expect per Group. |
Usage File
The Usage file name convention is a usage.group-{group_id}.{reporting_location}.csv. One file per Group is generated. The file contains a header row and the data.
In the “Usage” file, a row dedicated to account-level transactions is included. api_txn_class_a/b/c/d are included in this row since Backblaze B2 attributes them to the account level and not the bucket level.
If a bucket does not have any usage to report, that bucket will not appear in the “Usage” file.
| account_email | Email address for Group member. |
| account_id | Backblaze account identifier for account where the Usage Reports are stored, alphanumeric. |
| api_txn_class_a | Number of Class A transactions. |
| api_txn_class_b | Number of Class B transactions. |
| api_txn_class_c | Number of Class C transactions. |
| api_txn_class_d | Number of Class D transactions. |
| bucket_id | Bucket identifier, alphanumeric. |
| bucket_name | Name of the bucket. |
| date | Dates in YYYY-MM-DD format, indicating the UTC day covered by the report. |
| deleted_gb | Number of bytes deleted in gigabytes. |
| downloaded_bytes | Number of bytes downloaded in bytes. Number of bytes downloaded is a billable entity. Number includes the free allocated amount. |
| downloaded_favored_bytes | Number of favored bytes downloaded in bytes. Backblaze does not charge for favored bytes. |
| downloaded_gb | Number of bytes downloaded in gigabytes. |
| group_id | Group identifier, integer. |
| line_version | The revision number of the format. Usually, this is incremented when the number of columns changes. |
| reporting_location | Region. For example, us-west or us-east. |
| resource_group_id | Resource Group identifier. |
| resource_group_name | Resource Group name. |
| resource_name | Subscription identifier. |
| storage_byte_hours | Number of byteHours stored. Number of stored byte hours is a billable entity. Number includes the free allocated amount. |
| stored_gb | Number of bytes stored in gigabytes (at the end of the day). |
| uploaded_gb | Number of bytes uploaded in gigabytes. |
Audit File
The Audit file name convention is a usage.audit-group-{group_id}.{reporting_location}.csv. One file per Group is generated. The file contains a header row and the data.
If a bucket does not have any usage to report, that bucket will not appear in the “Audit” file.
bucket_id | Bucket identifier, alphanumeric. |
| date | Dates in YYYY-MM-DD format, indicating the UTC day covered by the report. |
| downloaded_gb | Number of bytes downloaded in gigabytes. |
| stored_gb | Number of bytes stored in gigabytes (at the end of the day). |
| uploaded_gb | Number of bytes uploaded in gigabytes. |
The format of these files may change in the future. For example, additional columns may be added.
Usage Reports for Standalone Accounts
A “Usage” CSV file and an “Audit” CSV file are generated daily for an account. The “Usage” file contains the amount of storage used and other usage data generated by the account for a given day. The “Audit” file is a minimal version of the “Usage” file for auditing purposes. This file contains only the bucket_id, date, stored_gb, downloaded_gb, and uploaded_gb fields.
Files for each day are organized into folders named by the {date} (YYYY-MM-DD format), and are uploaded to a special bucket. That bucket is auto-generated by Backblaze once files are available for the Usage Report-enabled administrator account. The bucket name follows the format "b2-reports-$ACCOUNTID" where “$ACCOUNTID” is your Backblaze account identifier.
Usage File
The Usage file name convention is a usage.account-{account_id}.csv. One file is generated per account. The file contains a header row and the data.
In the “Usage” file, a row dedicated to account-level transactions is included. api_txn_class_a/b/c are included in this row since Backblaze B2 attributes them to the account level and not the bucket level.
If a bucket does not have any usage to report, that bucket will not appear in the “Usage” file.
| account_email | Email address. |
| account_id | Backblaze account identifier for the account, alphanumeric. |
| api_txn_class_a | Number of Class A transactions. |
| api_txn_class_b | Number of Class B transactions. |
| api_txn_class_c | Number of Class C transactions. |
| api_txn_class_d | Number of Class D transactions. |
| bucket_id | Bucket identifier, alphanumeric. |
| bucket_name | Name of the bucket. |
| date | Dates in YYYY-MM-DD format, indicating the UTC day covered by the report. |
| deleted_gb | Number of bytes deleted in gigabytes. |
| downloaded_bytes | Number of bytes downloaded in bytes. Number of bytes downloaded is a billable entity. Number includes the free allocated amount. |
| downloaded_favored_bytes | Number of favored bytes downloaded in bytes. Backblaze does not charge for favored bytes. |
| downloaded_gb | Number of bytes downloaded in gigabytes. |
| group_id | Empty. |
| line_version | The revision number of the format. Usually, this is incremented when the number of columns changes. |
| reporting_location | Region. For example, us-west or us-east. |
| resource_group_id | Resource Group identifier. |
| resource_group_name | Resource Group name. |
| resource_name | Subscription identifier. |
| storage_byte_hours | Number of byteHours stored. Number of stored byte hours is a billable entity. Number includes the free allocated amount. |
| stored_gb | Number of bytes stored in gigabytes (at the end of the day). |
| uploaded_gb | Number of bytes uploaded in gigabytes. |
Audit File
The Audit file name convention is a usage.audit-account-{account_id}.csv. The file contains a header row and the data.
If a bucket does not have any usage to report, that bucket will not appear in the “Audit” file.
bucket_id | Bucket identifier, alphanumeric. |
| date | Dates in YYYY-MM-DD format, indicating the UTC day covered by the report. |
| downloaded_gb | Number of bytes downloaded in gigabytes. |
| stored_gb | Number of bytes stored in gigabytes (at the end of the day). |
| uploaded_gb | Number of bytes uploaded in gigabytes. |
The format of these files may change in the future. For example, additional columns may be added.
Usage Report Bucket
A Usage Report bucket is reserved strictly for the daily usage files and is therefore restricted. This means that the bucket cannot be modified (for example, it cannot be toggled between private and public) and no files can be uploaded to the bucket. You may store as many of the daily usage files in the bucket as you wish. Like any other bucket in your account, you will be charged every 30 days for the amount stored in the bucket and your account will be charged for downloads and transaction fees (see details here).
Backblaze performs a daily check on the bucket to verify the existence of files from the past seven days and restore any missing files if necessary. When Usage Reports are first enabled, this same process runs immediately, backfilling up to seven days of prior usage data into the reports bucket automatically.
Third-party applications may not support restricted buckets. Do not delete files until they are at least seven days old because the system will regenerate them.
Was this article helpful?