Managing fixed-term contracts just got a lot cleaner. We are excited to announce the ability to pass a cancellation date (end date) directly when provisioning or updating subscriptions in Stigg!

By default, subscriptions in Stigg are evergreen (auto-renewing). While this works perfectly for self-service self-renewing plans, sales-led motions often require fixed-term, non-recurring subscriptions. This update eliminates the manual overhead of handling these contracts.

🆕 What’s new?

You can now explicitly set an expiration date for a subscription at the exact moment of creation or during an update via the Stigg app, API and Salesforce integration. 

By passing the new cancellationDate parameter, Stigg handles the subscription lifecycle and schedules its termination automatically.

💡 Why it matters

• Consolidated API Workflows: Previously, creating a fixed-term subscription required two separate API calls - one to provision the subscription and a second to schedule its cancellation. Now, you can complete this entire workflow in a single, atomic request.
• Streamlined Sales-Led Operations: Seamlessly model precise, non-recurring enterprise pilots, short-term contract extensions, or fixed-duration proof-of-concepts without worrying about stray auto-renewals.

🍿 See it in action

⚒️ Get started

To provision a fixed-term subscription, simply include the cancellationDate (ISO-8601 string) directly when provisioning or updating subscriptions.

To implement this workflow, update your backend provisioning service to map contract end-dates directly to the cancellationDate input field. 

📦 Availability

The cancellationDate parameter is supported across the Stigg API and our latest server-side SDKs:

REST-based SDKs

• TypeScript: v0.1.0-alpha.31
• Python: v0.1.0-alpha.31
• Go: v0.1.0-alpha.29
• Java: v0.1.0-alpha.52
• Ruby: v0.1.0-alpha.29

GraphQL-based SDKs

• Node.js: v4.40.0
• Python / Java / Go / .NET: v6.10.0
• Ruby: v6.8.0

Salesforce integration

Version 1.14.0 or later.