The Capacity Planning REST API lets you programmatically manage capacity planning data in Atlassian Cloud. Use it to automate resource allocation, sync with external tools, or build AI-powered planning workflows.
All endpoints are served under:
1 2https://api.atlassian.com/ex/capacity-planning/{cloudId}/v1
Replace {cloudId} with your Atlassian site's cloud ID. You can find your
cloud ID from https://{your-site}.atlassian.net/_edge/tenant_info.
The API exposes three resources:
| Resource | Description |
|---|---|
| Contributions | Time allocations — how much capacity a person has on a piece of work in a given period |
| Contributor work associations | Assignment links between people and work items |
| Non-project work items | Custom work items that don't exist in Jira (e.g. "Hiring", "On-call", "Team ceremonies") |
List contributions for a contributor on a specific work item within a date range:
1 2 3 4 5curl --request GET \ --url "https://api.atlassian.com/ex/capacity-planning/{cloudId}/v1/contributions?contributorDataId={contributorAri}&workDataId={workAri}&startDate=2026-01-01&endDate=2026-12-31" \ --user "your-email@example.com:{API_TOKEN}" \ --header "Accept: application/json"
See Authentication for all supported authentication methods.
All endpoints return errors as RFC 7807 Problem Details objects with the following structure:
| Status | Title | When |
|---|---|---|
| 400 | Bad Request | Validation failures, malformed input, missing required parameters |
| 403 | Forbidden | Insufficient permissions (site access or work-item level) |
| 404 | Not Found | Resource does not exist or the API is not enabled for this site |
| 409 | Conflict | Duplicate resource (e.g. non-project work item name already exists) |
| 429 | Too Many Requests | Rate limit exceeded |
Rate this page: