Stigg

Stigg is a monetization and pricing platform that lets software companies define plans, features, and entitlements and enforce them across their products. The Stigg connector uses the Stigg GraphQL API to read customers, subscriptions, plans, features, coupons, and entitlement state, and to provision and update customers, subscriptions, and metered usage.

Power end-to-end data operations for your Stigg API with Nexla. Our bi-directional Stigg connector is purpose-built for Stigg, 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 Stigg or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Stigg 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 Stigg credential, you need a server-type environment API key from your Stigg account. Stigg issues a separate Server API key and Client API key for each environment; the connector uses the Server API key, which is intended for backend access to the Stigg API. The key is sent in the X-API-KEY request header on every call to the Stigg GraphQL endpoint at https://api.stigg.io/graphql.

To obtain your Server API key:

1. Sign in to the Stigg Cloud Console.

2. Navigate to Settings > Account > Environments.

3. Locate the environment you want to connect to in the environments table.

4. Copy the Server API key for that environment.

5. Store the key securely, as you will need it to configure your Nexla credential. Treat the Server API key as sensitive information and keep it confidential.

For more detail on environments and API keys, see the Stigg Environments documentation and the Stigg API reference.

Authenticate

Credentials required

Authenticate to Stigg using a server-type environment API key.

Field	Required	Secret	Description
API Key	Yes	Yes	Stigg server-type environment API key (found under environment settings, keyType SERVER).

Create a credential in Nexla

1. After selecting the data source/destination 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 Stigg Server API key in the API Key field. This is the Server API key you copied from Settings > Account > Environments in the Prerequisites. Nexla sends this value in the X-API-KEY header on every request to the Stigg GraphQL API.

   Each Stigg environment has its own Server API key. Make sure you use the key for the environment (for example, production or development) whose data you intend to read or write. If a key is compromised, rotate it from the Stigg environment settings and update the credential in Nexla.

   For more information on Stigg authentication and the GraphQL API, see the Stigg API reference.

4. 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/destination 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 Stigg connector tile, then select the credential that will be used to connect to Stigg, and click Next; or, create a new Stigg 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 Stigg GraphQL queries. 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 Customers

Retrieve customers from Stigg via the customers GraphQL query.

• This endpoint fetches the customers accessible to your Server API key, including reference ID, email, name, and creation timestamp. Results are paginated automatically, and Nexla follows the cursor to fetch subsequent pages.

For details on customer objects and the customers query, see the Stigg customers documentation.

Get Customer

Retrieve a single customer (with subscriptions, coupon, and promotional entitlements) via the getCustomerByRefId GraphQL query.

• Provide the customer's reference ID (refId) in the Customer Ref ID field to identify which customer to fetch.

For details on customer objects, see the Stigg customers documentation.

Get Active Subscriptions

Retrieve a customer's active subscriptions via the getActiveSubscriptions GraphQL query.

• Provide the customer's reference ID (refId) in the Customer Ref ID field. The endpoint returns each active subscription with its plan and current billing period end.

For details on the Stigg GraphQL API, see the Stigg GraphQL API documentation.

Get Subscription

Retrieve a single subscription (plan, customer, billing period) via the getSubscription GraphQL query.

• Provide the subscription's reference ID (refId) in the Subscription Ref ID field to identify which subscription to fetch.

For details on the Stigg GraphQL API, see the Stigg GraphQL API documentation.

List Plans

Retrieve pricing plans from Stigg via the plans GraphQL query.

• This endpoint fetches plans with reference ID, display name, status, and version number. Results are paginated automatically, and Nexla follows the cursor to fetch subsequent pages.

For details on plans, see the Stigg plans documentation.

List Features

Retrieve features from Stigg via the features GraphQL query.

• This endpoint fetches features with reference ID, display name, feature type, and meter type. Results are paginated automatically, and Nexla follows the cursor to fetch subsequent pages.

For details on features, see the Stigg features documentation.

List Coupons

Retrieve discount coupons from Stigg via the coupons GraphQL query.

• This endpoint fetches coupons with reference ID, name, status, type, and value. Results are paginated automatically, and Nexla follows the cursor to fetch subsequent pages.

For details on coupons, see the Stigg coupon documentation.

Get Customer Entitlements

Retrieve a customer's feature entitlements and usage state via the entitlementsState GraphQL query.

• Provide the customer's reference ID (refId) in the Customer Ref ID field. The endpoint returns each entitlement with its grant status, usage limit, current usage, and unlimited-usage flag.

For details on entitlements, see the Stigg entitlements 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

Stigg data sources can also be manually configured to query any valid Stigg GraphQL operation, including queries 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 Stigg 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.

Use as a destination

Click the + icon on the Nexset that will be sent to the Stigg destination, and select the Send to Destination option from the menu. Select the Stigg connector from the list of available destination connectors, then select the credential that will be used to connect to Stigg, and click Next; or, create a new Stigg credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations that execute Stigg GraphQL mutations. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings. Each template executes a GraphQL mutation against https://api.stigg.io/graphql; provide the full GraphQL request body (query plus variables) in each Nexset record.

Provision Customer

Execute the provisionCustomer GraphQL mutation to create a new customer (and optionally its initial subscription) in Stigg.

• Each record must contain the full GraphQL request body (query and variables) for the mutation. Records are sent one per request.

For details on the Stigg GraphQL API, see the Stigg GraphQL API documentation.

Update Customer

Execute the updateOneCustomer GraphQL mutation to modify an existing customer's details in Stigg.

• Each record must contain the full GraphQL request body (query and variables) for the mutation. Records are sent one per request.

For details on the Stigg GraphQL API, see the Stigg GraphQL API documentation.

Provision Subscription

Execute the provisionSubscriptionV2 GraphQL mutation to create a new subscription for a customer in Stigg.

• Each record must contain the full GraphQL request body (query and variables) for the mutation. Records are sent one per request.

For details on the Stigg GraphQL API, see the Stigg GraphQL API documentation.

Update Subscription

Execute the updateOneSubscription GraphQL mutation to modify an existing subscription (including feature quantities) in Stigg.

• Each record must contain the full GraphQL request body (query and variables) for the mutation. Records are sent one per request.

For details on the Stigg GraphQL API, see the Stigg GraphQL API documentation.

Cancel Subscription

Execute the cancelSubscription GraphQL mutation to terminate a customer's subscription in Stigg.

• Each record must contain the full GraphQL request body (query and variables) for the mutation. Records are sent one per request.

For details on the Stigg GraphQL API, see the Stigg GraphQL API documentation.

Report Usage

Execute the reportUsage GraphQL mutation to log calculated usage for a metered feature in Stigg.

• Each record must contain the full GraphQL request body (query and variables) for the mutation. Records are sent one per request.

For details on the Stigg GraphQL API, see the Stigg GraphQL API documentation.

GraphQL Mutation

Execute any other GraphQL mutation against the Stigg API (for example, archiveCustomer, migrateSubscriptionToLatest, or reportEvent).

• Each record must contain the full GraphQL request body (query and variables) for the mutation. Use this template for mutations not covered by the dedicated endpoints above.

For details on the Stigg GraphQL API, see the Stigg GraphQL API documentation.

Manual configuration

Stigg destinations can also be manually configured to send data to any valid Stigg GraphQL mutation. 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, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

The Stigg API expects JSON in the request body. Each record should contain a complete GraphQL request, with the query string and any variables, so that Nexla can post it to the GraphQL endpoint.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Stigg endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Stigg endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.