Skip to main content

Wasabi

Wasabi is a cloud storage platform providing S3-compatible object storage. The Wasabi Stats API exposes account and per-bucket utilization metrics, allowing you to ingest storage usage and monitoring data into Nexla for analysis and reporting.

Wasabi icon

Power end-to-end data operations for your Wasabi API with Nexla. Our bi-directional Wasabi connector is purpose-built for Wasabi, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Wasabi or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Wasabi workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Wasabi credential, you need a Wasabi Access Key and Secret Key that have permission to call the Stats API. The Stats API requires keys that are either Root user keys or keys with associated billing permissions. Nexla sends these keys in the Authorization header, combined as AccessKey:SecretKey (the two values joined by a colon).

To obtain your Wasabi credentials, follow these steps:

  1. Sign in to the Wasabi Console with an account that has Root or billing permissions.

  2. In the left-hand menu, click Access Keys.

  3. Click Create Access Key. When prompted, choose to create the key for the Root User (or a sub-user with the required billing permissions).

  4. Wasabi displays the Access Key. Click Show to reveal the Secret Key.

  5. Download or copy both keys and store them somewhere safe. Wasabi does not let you retrieve the Secret Key again after you leave this screen, and there is a limit of two access/secret key pairs per user.

  6. Combine the two values as AccessKey:SecretKey (separated by a colon) when you enter them into the Nexla credential.

The Stats API is served from https://stats.wasabisys.com, which is the default Base URL used by this connector. For more detail, see the Wasabi Stats API documentation and the guide on creating a new access key.

Authenticate

Credentials required

FieldRequiredSecretDescription
API Key ValueYesYesThe Wasabi API key in AccessKey:SecretKey format. Combine your Access Key and Secret Key with a colon separator.
Base URLYesNoThe base URL for the Wasabi Stats API.

Create a credential in Nexla

  1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter your Wasabi API key in the API Key Value field, using the AccessKey:SecretKey format described in Prerequisites. This value is stored securely and sent in the Authorization header for all API requests.

  4. Enter the Base URL for the Wasabi Stats API. Unless you have been directed to a different endpoint, use the default value https://stats.wasabisys.com.

    The Wasabi Stats API requires keys that are either Root user keys or keys with associated billing permissions. If your keys are compromised, revoke them in the Wasabi Console and generate a new access key set.

    For more information about authentication and available metrics, see the Wasabi Stats API documentation.

  5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Wasabi connector tile, then select the credential that will be used to connect to Wasabi, and click Next; or, create a new Wasabi credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Wasabi Stats API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

List Standalone Utilizations

Returns utilization metrics for standalone Wasabi storage accounts. Use this template when you need account-level storage usage data for monitoring, analysis, or reporting.

  • This endpoint automatically paginates through the available records, fetching subsequent pages until no further data is returned.

For detailed information about the response fields and available metrics, see the Wasabi Stats API documentation.

List Standalone Bucket Utilizations

Returns per-bucket utilization metrics for standalone Wasabi storage accounts. Use this template when you need storage usage broken down by individual bucket for monitoring, analysis, or reporting.

  • This endpoint automatically paginates through the available records, fetching subsequent pages until no further data is returned.

For detailed information about the response fields and available metrics, see the Wasabi Stats API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Wasabi data sources can also be manually configured to ingest data from any valid Wasabi Stats API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Wasabi data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.