​
Overview

This Go module provides a wrapper to Stigg’s GraphQL API based on the operations that are in use by the Stigg’s Node.js SDK. It leverages the gqlgenc library to generate the types under the hood and by default utilizes the http.Client module to execute the API requests.

​
Installing the SDK

The first step is to install the Stigg SDK as a dependency in your application:

go get github.com/stiggio/api-client-go/v2

​
Retrieving the server API Key

In the Stigg app, go to Settings > Account > Environments.

Copy the Server API key of the relevant environment.

​
Initializing the SDK

Import the Stigg client and initialize it with the API key:

import (
  "context"
  "github.com/stiggio/api-client-go/v2"
  "os"
)

// Ptr is a helper function that returns a pointer to whatever 
// value we pass to it, will be widely used in the examples below
func Ptr[T any](v T) *T {
  return &v
}

func main() {
  apiKey := os.Getenv("STIGG_SERVER_API_KEY")

  client := stigg.NewStiggClient(apiKey, nil, nil)

  // client is initialized
}

​
Provisioning customers

When a new customer is provisioned within your application (for example: as part of your registration or onboarding process), you should also provision them in Stigg.

The customer’s billing information can also be passed to Stigg when a customer is created or updated. When Stigg is integrated with additional service, this information will be propagated to the active integrations. The billing information is not persisted on Stigg’s servers.

You can optionally pass subscriptionParams to create subscription for that customer using a single operation. Doing so, will allow Stigg admins to override the requested subscription with no-code from the Stigg Console using the product’s Customer Journey configuration.

result, err := client.ProvisionCustomer(context.Background(), stigg.ProvisionCustomerInput{
  CustomerID: Ptr("customer-id"),
  Name:  Ptr("Acme"), 						// optional
  Email: Ptr("john@example.com"), 	// optional - billing email address
  CouponRefID: Ptr("coupon-id"),	// optional
  SubscriptionParams: &stigg.ProvisionCustomerSubscriptionInput{ // optional
    PlanID: "plan-revvenu-basic",
    BillingCountryCode: Ptr("DK"), // optional, required for price localization, must be in the ISO-3166-1 format   
  },
  BillingInformation: &stigg.CustomerBillingInfo{ // optional
    Language: Ptr("en"),
    Timezone: Ptr("America/New_York"),
    BillingAddress: &stigg.Address{
      Country:      Ptr("US"),
      City:         Ptr("New York"),
      State:        Ptr("NY"),
      AddressLine1: Ptr("123 Main Street"),
      AddressLine2: Ptr("Apt. 1"),
      PhoneNumber:  Ptr("+1 212-499-5321"),
      PostalCode:   Ptr("10164"),
    },
    ShippingAddress: &stigg.Address{
      Country:      Ptr("US"),
      City:         Ptr("New York"),
      State:        Ptr("NY"),
      AddressLine1: Ptr("123 Main Street"),
      AddressLine2: Ptr("Apt. 1"),
      PhoneNumber:  Ptr("+1 212-499-5321"),
      PostalCode:   Ptr("10164"),
    },
  },
  AdditionalMetaData: map[string]interface{}{ // optional
    "Key": "Value",
  },
})

​
Updating customers

Customer information can also be updated whenever you like assuming it already exists, for example: In order to update the customer’s email, you only need to send the new email value without the rest of the customer. Due to the fact that the customer’s billing information is not persisted on Stigg’s servers, in order to update it, the entire billing information object must be passed each time.

result, err := client.UpdateCustomer(context.Background(), stigg.UpdateCustomerInput{
  CustomerID:  Ptr("customer-id"),
  Name:  Ptr("Acme"),
  Email: Ptr("john@example.com"),
  BillingInformation: &stigg.CustomerBillingInfo{
    Language: Ptr("en"),
    Timezone: Ptr("America/New_York"),
    BillingAddress: &stigg.Address{
      Country:      Ptr("US"),
      City:         Ptr("New York"),
      State:        Ptr("NY"),
      AddressLine1: Ptr("123 Main Street"),
      AddressLine2: Ptr("Apt. 1"),
      PhoneNumber:  Ptr("+1 212-499-5321"),
      PostalCode:   Ptr("10164"),
    },
  },
  AdditionalMetaData: map[string]interface{}{
    "Key": "Value",
  },
})

​
Getting customer data

result, err := client.GetCustomerByID(context.Background(), stigg.GetCustomerByRefIDInput{
  CustomerID: "customer-f9942a",
})

​
Getting customer active subscriptions

result, err := client.GetActiveSubscriptions(context.Background(), stigg.GetActiveSubscriptionsInput{
  CustomerID: "customer-f9942a",

  // Optional, pass it to get subscription of specific resource 
  ResourceID: Ptr("resource-01"),
})

​
Provisioning subscriptions

When a customer subscribes to a new plan (for example: during an upgrade from a free plan to a paid plan, or downgrade from a higher tier to a lower tier), a subscription needs to be created in Stigg.

When provisioning of a paid subscription is attempted, Stigg is integrated with a billing solution and payment details have not been previously provided by the customer, Stigg will auto-magically redirect customers to a the billing solution’s checkout page. After the customer enters the required payment details in the presented checkout page, the relevant subscription will be created in both Stigg and the billing solution.

When no payment is required or when Stigg is not integrated with a billing solution, the subscription will be immediately created in Stigg.

When a customer subscribes to a new plan (free, paid, trial, etc.), provision a subscription in Stigg. The provision result can be a successfully created subscription, or a redirect link to stripe checkout in case payment is needed.

result, err := client.ProvisionSubscription(context.Background(), stigg.ProvisionSubscriptionInput{
  // Mandatory, subscription customer ID
  CustomerID: "customer-demo-01",

  // Mandatory, subscription plan ID
  PlanID: "plan-revvenu-essentials",

  // Optional, required only for paid subscriptions  
  BillingPeriod: Ptr(stigg.BillingPeriodMonthly),

  // Optional, required for multiple subscription for same product
  ResourceID: Ptr("resource-01"),                

  // Optional, required for subscriptions with per unit pricing
  BillableFeatures: []*stigg.BillableFeatureInput{
    {
      FeatureID: "feature-01-templates",
      Quantity:  20,
    },
  },

  // Optional, list of subscription addons and quantities
  Addons: []*stigg.SubscriptionAddonInput{
    {
      AddonID:  "addon-revvenu-extra-campaigns",
      Quantity: Ptr(int64(3)),
    },
  }

  // Optional, required for price localization, must be in the ISO-3166-1 format
  BillingCountryCode: Ptr("DK"),   					

  // Optional, parameters used for the hosted checkout
  CheckoutOptions: &stigg.CheckoutOptions{ 
    SuccessURL: "https://your-success-url.com",
    CancelURL:  "https://your-cancel-url.com",
  }
})
  1. A customer can have both a non-trial (free or paid) subscription and trial subscription to different plans of the same product in parallel - this logic allows customers to trial a higher tier plan, while still paying for an existing plan.
  2. When the customer has a trial subscription for plan X of product A and a new subscription is created for the same plan, the new subscription will be created as as non-trial (paid) subscription - this logic follows an upgrade flow of a trial subscription to a paid subscription of a specific plan.
  3. Except in the above mentioned cases, when a customer has an active subscription for product X, and another subscription for the same product is created with start date S, the existing subscription will automatically be cancelled and the new subscription will start on start date S.
  4. It’s also possible to explicitly skip the trial period of the selected plan by providing the skipTrial: true parameter to the provisionSubscription() method.

​
Updating subscriptions

Updating an existing subscription, this can be used to update the feature quantity that the customer is subscribed for or the add-ons.

result, err := client.UpdateSubscription(context.Background(), stigg.UpdateSubscriptionInput{
  SubscriptionID: Ptr("subscription-plan-revvenu-essentials-dc847c"),
  BillingPeriod: Ptr(stigg.BillingPeriodMonthly),
  BillableFeatures: []*stigg.BillableFeatureInput{
    {
      FeatureID: "feature-01-templates",
      Quantity:  6,
    },
  },
  Addons: []*stigg.SubscriptionAddonInput{
    {
      AddonID:  "addon-revvenu-extra-campaigns",
      Quantity: Ptr(int64(2)),
    },
  }
})

​
Cancel subscription

result, err := client.CancelSubscription(context.Background(), stigg.SubscriptionCancellationInput{
  SubscriptionRefID: "subscription-plan-revvenu-essentials-dc847c",
  SubscriptionCancellationTime: Ptr(stigg.SubscriptionCancellationTimeImmediate),
})

Subscription cancellation will take place according to the defined product behavior.

​
Getting the entitlement of a customer for a specific feature

Used to check if the customer has access to a feature, the usage limit, and the current usage.

result, err := client.GetEntitlement(context.Background(), stigg.FetchEntitlementQuery{
  CustomerID: "customer-demo-01",
  FeatureID:  "feature-01-templates",
  Options: &stigg.EntitlementOptions{
    RequestedUsage: Ptr(float64(0)),
  },
  ResourceID: Ptr("resource-01"),  // optional, pass it to get entitlement of specific resource
})

if result.Entitlement.IsGranted {
  // customer has access to the feature 
} else {
  // access denied
}

​
Getting all of the entitlements of a customer

Used to check to what features the customer has access to, the usage limit , and the current usage of each entitlement.

result, err := client.GetEntitlements(context.Background(), stigg.FetchEntitlementsQuery{
  CustomerID: "customer-demo-01",
  
  // Optional, pass it to get entitlements of specific resource
  ResourceID: Ptr("resource-01")
})

​
Reporting usage measurements to Stigg

The Stigg SDK allows you to report usage measurements for metered features. The reported usage will be used to track, limit and bill the customer’s usage of metered features.

Stigg supports metering of usage from the following data sources:

  1. Calculated usage - usage that has been aggregated and calculated by your application. This type is useful for features, such as: seats.
  2. Raw events - raw events from your application, which Stigg filters and aggregates aggregate to calculate customer usage. This type is useful for features, such as: monthly active users (MAUs).

More details about Stigg’s metering and aggregation capabilities can be found here:

Stigg's metering and aggregation capabilities
  1. Reporting of measurements to Stigg should be done only after the relevant resources have been provisioned in your application.
  2. To ensure that the provisioned resources are aligned with the measurements that are reported to Stigg, ensure that customers are not allowed to allocate new resources until an acknowledgement about the processed measurement is received from the Stigg backend.

Validating that a measurement was successfully reported to Stigg is also possible in the customer details section of the relevant customer in the Stigg app.

​
Calculated usage

result, err := client.ReportUsage(context.Background(), stigg.ReportUsageInput{
  Value:      5,
  CustomerID: "customer-demo-01",
  FeatureID:  "feature-02-campaigns",
  ResourceID: Ptr("resource-01"),  // optional, pass it to report usage for specific resource
})

​
Raw events

result, err := client.ReportEvent(context.Background(), stigg.UsageEventsReportInput{
  UsageEvents: []*stigg.UsageEventReportInput{
    {
      CustomerID:     "customer-test-id",
      ResourceID:     Ptr("resource-01"), // optional, pass it to report event for specific resource
      EventName:      "user_login",
      IdempotencyKey: "227c1b73-883a-457b-b715-6ba5a2c69ce4",
      Dimensions: map[string]interface{}{
        "user_id":    "user-01",
        "user_email": "john@example.com",
      },
      Timestamp: Ptr("2022-10-26T15:01:55.768Z"), // optional, pass it to report event with specific timestamp
    },
  },
})

It’s also possible to send a batch of events in one invocation. To do so, simply pass an array of events to the reportEvent method.

​
Getting available coupons

result, err := client.GetCoupons(context.Background())

​
Estimating subscription cost

You can estimate the subscription cost using the estimateSubscription method. This can help the customer to understand the costs before paying.

result, err := client.EstimateSubscription(context.Background(), stigg.EstimateSubscriptionInput{
		CustomerID:      "customer-demo-01",
		PlanID:          "plan-revvenu-essentials",
		BillingPeriod:   Ptr(stigg.BillingPeriodMonthly),
		PriceUnitAmount: Ptr(float64(4)), // optional, required for plans with per-unit pricing
		Addons: []*stigg.SubscriptionAddonInput{{ // optional
			AddonID:  "addon-10-campaigns",
			Quantity: Ptr(int64(5)),
		}},
		BillingCountryCode: Ptr("DK"),          // optional, required for price localization, must be in the ISO-3166-1 format
		ResourceID:         Ptr("resource-01"), // optional, required for multiple subscription for same product
		BillingInformation: Ptr(stigg.SubscriptionBillingInfo{
			TaxRateIds: []string{"tax-rate-1"},
		}),
	})

You can also estimate the cost of updating an existing subscription using the updateSubscription method, which also returns a breakdown of the proration amounts:

result, err := client.EstimateSubscriptionUpdate(context.Background(), stigg.EstimateSubscriptionUpdateInput{
  SubscriptionID: "subscription-plan-revvenu-basic-558071",
  UnitQuantity:   Ptr(float64(4)),
  Addons: []*stigg.SubscriptionAddonInput{{
    AddonID:  "addon-10-campaigns",
    Quantity: Ptr(int64(5)),
  }},
})

​
Full SDK reference

Go SDK reference

​
SDK changelog