Membership Contracts
Update minimum billing cycles for subscription contract
Sets the minimum number of billing cycles (payments) required before a customer can cancel their subscription. This is commonly used to enforce commitment periods or prevent early cancellations.
Full behavior, validation rules, and side effects
Key Features:
- Commitment Enforcement: Require customers to stay subscribed for a minimum period
- Cancellation Prevention: Blocks cancellation until minimum cycles are met
- Contract Terms: Implements contractual minimum billing requirements
- Flexible Duration: Set any number from 0 (no minimum) to higher values
Common Use Cases:
- 3-Month Minimum: Set minCycles=3 for quarterly commitment
- Annual Contract: Set minCycles=12 for yearly subscriptions
- Trial Completion: Require 1-2 cycles before allowing cancellation
- Remove Restriction: Set minCycles=0 or null to remove minimum
Behavior:
- Customer portal will show “X cycles remaining until cancellation allowed”
- Cancellation button disabled until minimum met
- Does not affect pausing subscriptions
- Applies to future billing cycles, not retroactive
Parameters:
- contractId (required): The subscription contract ID
- minCycles (optional): Number of minimum cycles (null or 0 = no minimum)
Authentication: Requires API key authentication via X-API-Key header or api_key parameter
PUT
Update minimum billing cycles for subscription contract
Documentation Index
Fetch the complete documentation index at: https://developers.appstle.com/llms.txt
Use this file to discover all available pages before exploring further.
Headers
Query Parameters
Subscription contract ID
API Key (Deprecated - Use Header X-API-Key instead)
Minimum number of billing cycles required (null or 0 = no minimum)
Response
Min cycles updated successfully, returns updated subscription contract
Available options:
ACTIVE, PAUSED, CANCELLED, EXPIRED, FAILED, $UNKNOWN Available options:
SUCCEEDED, FAILED, $UNKNOWN