Importing feature usage

Importing feature usage is supported only for metered features with a Calculated Usage meter type.

Before importing feature usage, ensure that the relevant customers have been imported to Stigg.

Using the CLI

Create a file named usage.json containing the latest usage data for all features. The file must follow this schema:

{
  "usages": [
    {
      "customerId": "lorem-ipsum",
      "resourceId": "site-1", // optional - required for multiple subscriptions product
      "featureId": "feature-seats",
      "usage": 5
    }
    // ...
  ]
}

Initiate the bulk import process:

npx @stigg/bulk-import --usage-file usage.json

The import function is idempotent; therefore, importing usage multiple times will produce the same result.

Using the API and SDKs

Use the Report Usage Bulk endpoint and include the updateBehavior: UsageUpdateBehavior.SET property in each usage report.

The Report Usage Bulk endpoint supports up to 100 records per request and has a rate limit of 600 requests per minute. Requests are processed synchronously.

Importing subscriptions Overview

⌘I

Getting started

Developer tools

Governance (Private Beta)

Modeling your pricing in Stigg

Managing customers, subscriptions and entitlements

Getting usage data into Stigg

Snap-in widgets

Native integrations

Importing and exporting data

Going live

Workflow automation

Rolling out pricing changes with confidence

Price localization

Managing your account

High-availability and scale

Security & compliance

Using the CLI

Using the API and SDKs

​Using the CLI

​Using the API and SDKs

Using the CLI

Using the API and SDKs