The GraphQL endpoint
The GraphQL API has a single endpoint:Retrieving the server API Key
In the Stigg app, go to Settings > Account > Environments. Copy the Server API key of the relevant environment.Discovering the GraphQL API
GraphQL explorer
You can run queries on real Stigg data using our GraphQL Explorer, an integrated development environment in your browser that includes docs, syntax highlighting, and validation errors.To authenticate you need to pass the Server API key in the X-API-KEY request header.
GraphQL API playground
Interact with Stigg’s GraphQL directly from your browser.
GraphQL introspection
GraphQL is introspective. This means you can query a GraphQL schema for details about itself. To perform an introspection query, send aPOST request to the GraphQL endpoint and include your Server API key using the X-API-KEY header.
For example, to fetch all available root types:
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 passsubscriptionParams 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.
Query
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. QueryGetting customer data
QueryGetting customer active subscriptions
QueryGetting a subscription
QueryProvisioning subscriptions
When a customer subscribes to a new plan (free, paid, trial, etc.), provision the subscription in Stigg. QueryUpdating subscriptions
Updating an existing subscription, this can be used to update the feature quantity that the customer is subscribed for. QueryCancel subscription
QueryGetting 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. QueryGetting 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. QueryReporting usage measurements to Stigg
The Stigg API 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:- Calculated usage - usage that has been aggregated and calculated by your application. This type is useful for features, such as: seats.
- 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).
Stigg's metering and aggregation capabilities
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
#QueryRaw events
#QueryreportEvent method.
Response
The mutation has no return value
Getting available coupons
QueryEstimate subscription cost
You can estimate the subscription cost using theestimateSubscription method. This can help the customer to understand the costs before paying.
Query
updateSubscription method, which also returns a breakdown of the proration amounts:
Query
Migrating subscriptions to the latest plan and add-on version
When changes to plans and add-ons are rolled out only to new subscriptions, grandfathering takes place. In order to prevent a SKU sprawl, Stigg allows you to manually migrate subscriptions to the latest plan and add-on version on a subscription-by-subscription basis. QueryArchiving & unarchiving customers
When a customer is archived:- Its PII (name and email address) will be nullified.
- It will no longer appear in the Stigg app UI.
- It will no longer be returned by the Stigg API and SDKs.
