Platform subscription tiers that determine which Service Lines an organization can activate, usage limits, and available features across all workspaces.
The Scrums.com API is planned and not yet publicly available. Endpoints and behaviour are subject to change before release.
Plans define the tiers of access to the Scrums.com platform. An organization’s active Plan determines which Service Lines can be activated, what usage limits apply, which features are available, and what level of support is included.Plans are managed by Scrums.com and are read-only via the API. Organizations subscribe to plans via Subscriptions.
Every execution_model and product_line combination available on a Service Line is gated by the active plan. A plan lists its permitted product lines under allowed_product_lines. Attempting to create a Service Line for a product line not on the plan returns a 403 error with code plan_limit_exceeded.
Plans declare limits on: workspaces, concurrent active Service Lines, users, API calls per month, agent credits per month, and integration connections. Exceeding a hard limit returns 429 rate_limited or 403 plan_limit_exceeded depending on the resource.
Verify allowed_product_lines before building integrations. If you are building an integration that activates a specific product line (e.g., agent gateway), check that the target organization’s plan permits it before attempting Service Line creation.
Cache the plan list. Plans change infrequently. Cache the response from GET /v1/plans for at least one hour rather than querying on every request.
Treat null limits as unlimited, not as missing data. The API explicitly signals uncapped limits with null. Do not treat a null limit as an error or missing value.
