Stigg Contracts — Entitlements and Invoicing

A contract is the source of truth for a sales-led deal: what the customer can do, and what you charge for it. It groups subscriptions for one customer, and those subscriptions grant the entitlements — the contract is the agreement they belong to, not a second entitlement mechanism. It can also carry a billing contract, which produces invoices. The halves are independent — a contract with no billing contract still provisions access.

The contract itself holds no commercial terms. No price, quantity or commitment fields — only a name, PO number, activation window, and its subscription links. Negotiated price and committed volumes live on the custom subscription (priceOverrides, charges, unitQuantity, minimumSpend — stigg-subscriptions). Priced line items exist only on the billing half, below.

Before You Start

Per the umbrella stigg skill: search first. Confirm shapes and field names against the docs.

No SDK surface. Contracts are not in @stigg/node-server-sdk or @stigg/js-client-sdk. Use REST (canonical here, https://api.stigg.io/api/v1, header X-API-KEY) or GraphQL.