Developer
News and Updates
Get Support
Sign in
Get Support
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Last updated Jul 20, 2026

Preview: This section describes a preview feature. Preview features are deemed stable; however, they remain under active development and may be subject to shorter deprecation windows. Preview features are suitable for early adopters in production environments. We release preview features so partners and developers can study, test, and integrate them prior to General Availability (GA).

Authorization

Access to the Capacity Planning REST API is controlled by two layers: user permissions (always enforced) and OAuth scopes (enforced when using OAuth 2.0 authentication).

Permission model

All API requests — regardless of authentication method — require the authenticated user to have the appropriate Jira site permissions for capacity planning features. The API enforces the same permission checks as the Capacity Planning UI — a user cannot access or modify data they wouldn't be able to see in the product.

OAuth scopes

When using OAuth 2.0, each request must carry a token with the appropriate scope. Each resource has a separate read and write scope.

ScopePermits
read:contribution:capacity-planningRead contributions (time allocations)
write:contribution:capacity-planningCreate, update, and clear contributions
read:contributor-work-association:capacity-planningRead assignment links between people and work
write:contributor-work-association:capacity-planningCreate and delete assignment links
read:non-project-work:capacity-planningRead non-project work items
write:non-project-work:capacity-planningCreate, update, and delete non-project work items

Regardless of the API token type, the request acts as the authenticated user with their existing site and project permissions.

Scope requirements by endpoint

EndpointMethodRequired scope (OAuth only)
/v1/contributionsGETread:contribution:capacity-planning
/v1/contributionsPOSTwrite:contribution:capacity-planning
/v1/contributions:clearPOSTwrite:contribution:capacity-planning
/v1/contributor-work-associationsPOSTwrite:contributor-work-association:capacity-planning
/v1/contributor-work-associations/by-contributorGETread:contributor-work-association:capacity-planning
/v1/contributor-work-associations/by-workGETread:contributor-work-association:capacity-planning
/v1/contributor-work-associations:deletePOSTwrite:contributor-work-association:capacity-planning
/v1/non-project-work-itemsGETread:non-project-work:capacity-planning
/v1/non-project-work-itemsPOSTwrite:non-project-work:capacity-planning
/v1/non-project-work-items/{id}GETread:non-project-work:capacity-planning
/v1/non-project-work-items/{id}PUTwrite:non-project-work:capacity-planning

Rate this page: