openapi: 3.1.2 info: description: "You're looking at the current **stable** documentation of the OpenProject APIv3. If you're interested in the current\ndevelopment version, please go to [github.com/opf](https://github.com/opf/openproject/tree/dev/docs/api/apiv3).\n\n## Introduction\n\nThe documentation for the APIv3 is written according to the [OpenAPI 3.1 Specification](https://swagger.io/specification/).\nYou can either view the static version of this documentation on the [website](https://www.openproject.org/docs/api/introduction/)\nor the interactive version, rendered with [OpenAPI Explorer](https://github.com/Rhosys/openapi-explorer/blob/main/README.md),\nin your OpenProject installation under `/api/docs`.\nIn the latter you can try out the various API endpoints directly interacting with our OpenProject data.\nMoreover you can access the specification source itself under `/api/v3/spec.json` and `/api/v3/spec.yml`\n(e.g. [here](https://community.openproject.org/api/v3/spec.yml)).\n\nThe APIv3 is a hypermedia REST API, a shorthand for \"Hypermedia As The Engine Of Application State\" (HATEOAS).\nThis means that each endpoint of this API will have links to other resources or actions defined in the resulting body.\n\nThese related resources and actions for any given resource will be context sensitive. For example, only actions that the\nauthenticated user can take are being rendered. This can be used to dynamically identify actions that the user might take for any\ngiven response.\n\nAs an example, if you fetch a work package through the [Work Package endpoint](https://www.openproject.org/docs/api/endpoints/work-packages/), the `update` link will only\nbe present when the user you authenticated has been granted a permission to update the work package in the assigned project.\n\n## HAL+JSON\n\nHAL is a simple format that gives a consistent and easy way to hyperlink between resources in your API.\nRead more in the following specification: [https://tools.ietf.org/html/draft-kelly-json-hal-08](https://tools.ietf.org/html/draft-kelly-json-hal-08)\n\n**OpenProject API implementation of HAL+JSON format** enriches JSON and introduces a few meta properties:\n\n- `_type` - specifies the type of the resource (e.g.: WorkPackage, Project)\n- `_links` - contains all related resource and action links available for the resource\n- `_embedded` - contains all embedded objects\n\nHAL does not guarantee that embedded resources are embedded in their full representation, they might as well be\npartially represented (e.g. some properties can be left out).\nHowever in this API you have the guarantee that whenever a resource is **embedded**, it is embedded in its **full representation**.\n\n## API response structure\n\nAll API responses contain a single HAL+JSON object, even collections of objects are technically represented by\na single HAL+JSON object that itself contains its members. More details on collections can be found\nin the [Collections Section](https://www.openproject.org/docs/api/collections/).\n\n## Authentication\n\nThe API supports the following authentication schemes:\n\n* Session-based authentication\n* API tokens\n * passed as Bearer token\n * passed via Basic auth\n* OAuth 2.0\n * using built-in authorization server\n * using an external authorization server (RFC 9068)\n\nDepending on the settings of the OpenProject instance many resources can be accessed without being authenticated.\nIn case the instance requires authentication on all requests the client will receive an **HTTP 401** status code\nin response to any request.\n\nOtherwise unauthenticated clients have all the permissions of the anonymous user.\n\n### Session-based authentication\n\nThis means you have to login to OpenProject via the Web-Interface to be authenticated in the API.\nThis method is well-suited for clients acting within the browser, like the Angular-Client built into OpenProject.\n\nIn this case, you always need to pass the HTTP header `X-Requested-With \"XMLHttpRequest\"` for authentication.\n\n### API token as bearer token\n\nUsers can authenticate towards the API v3 using an API token as a bearer token.\n\nFor example:\n\n```shell\nAPI_KEY=opapi-2519132cdf62dcf5a66fd96394672079f9e9cad1\ncurl -H \"Authorization: Bearer $API_KEY\" https://community.openproject.org/api/v3/users/42\n```\n\nUsers can generate API tokens on their account page.\n\n### API token through Basic Auth\n\nAPI tokens can also be used with basic auth, using the user name `apikey` (NOT your login) and the API token as the password.\n\nFor example:\n\n```shell\nAPI_KEY=opapi-2519132cdf62dcf5a66fd96394672079f9e9cad1\ncurl -u apikey:$API_KEY https://community.openproject.org/api/v3/users/42\n```\n\n### OAuth 2.0 authentication\n\nOpenProject allows authentication and authorization with OAuth2 with *Authorization code flow*, as well as *Client credentials* operation modes.\n\nTo get started, you first need to register an application in the OpenProject OAuth administration section of your installation.\nThis will save an entry for your application with a client unique identifier (`client_id`) and an accompanying secret key (`client_secret`).\n\nYou can then use one the following guides to perform the supported OAuth 2.0 flows:\n\n- [Authorization code flow](https://oauth.net/2/grant-types/authorization-code)\n\n- [Authorization code flow with PKCE](https://doorkeeper.gitbook.io/guides/ruby-on-rails/pkce-flow), recommended for clients unable to keep the client_secret confidential\n\n- [Client credentials](https://oauth.net/2/grant-types/client-credentials/) - Requires an application to be bound to an impersonating user for non-public access\n\n### OAuth 2.0 using an external authorization server\n\nThere is a possibility to use JSON Web Tokens (JWT) generated by an OIDC provider configured in OpenProject as a bearer token to do authenticated requests against the API.\nThe following requirements must be met:\n\n- OIDC provider must be configured in OpenProject with **jwks_uri**\n- JWT must be signed using RSA algorithm\n- JWT **iss** claim must be equal to OIDC provider **issuer**\n- JWT **aud** claim must contain the OpenProject **client ID** used at the OIDC provider\n- JWT **scope** claim must include a valid scope to access the desired API (e.g. `api_v3` for APIv3)\n- JWT must be actual (neither expired or too early to be used)\n- JWT must be passed in Authorization header like: `Authorization: Bearer {jwt}`\n- User from **sub** claim must be linked to OpenProject before (e.g. by logging in), otherwise it will be not authenticated\n\nIn more general terms, OpenProject should be compliant to [RFC 9068](https://www.rfc-editor.org/rfc/rfc9068) when validating access tokens.\n\n### Why not username and password?\n\nThe simplest way to do basic auth would be to use a user's username and password naturally.\nHowever, OpenProject already has supported API keys in the past for the API v2, though not through basic auth.\n\nUsing **username and password** directly would have some advantages:\n\n* It is intuitive for the user who then just has to provide those just as they would when logging into OpenProject.\n\n* No extra logic for token management necessary.\n\nOn the other hand using **API keys** has some advantages too, which is why we went for that:\n\n* If compromised while saved on an insecure client the user only has to regenerate the API key instead of changing their password, too.\n\n* They are naturally long and random which makes them invulnerable to dictionary attacks and harder to crack in general.\n\nMost importantly users may not actually have a password to begin with. Specifically when they have registered\nthrough an OpenID Connect provider.\n\n## Cross-Origin Resource Sharing (CORS)\n\nBy default, the OpenProject API is _not_ responding with any CORS headers.\nIf you want to allow cross-domain AJAX calls against your OpenProject instance, you need to enable CORS headers being returned.\n\nPlease see [our API settings documentation](https://www.openproject.org/docs/system-admin-guide/api-and-webhooks/) on\nhow to selectively enable CORS.\n\n## Allowed HTTP methods\n\n- `GET` - Get a single resource or collection of resources\n\n- `POST` - Create a new resource or perform\n\n- `PATCH` - Update a resource\n\n- `DELETE` - Delete a resource\n\n## Compression\n\nResponses are compressed if requested by the client. Currently [gzip](https://www.gzip.org/) and [deflate](https://tools.ietf.org/html/rfc1951)\nare supported. The client signals the desired compression by setting the [`Accept-Encoding` header](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.3).\nIf no `Accept-Encoding` header is send, `Accept-Encoding: identity` is assumed which will result in the API responding uncompressed." title: OpenProject API V3 (Stable) Actions & Capabilities Sprints API version: '3' servers: - url: https://qa.openproject-edge.com description: Edge QA instance - url: https://qa.openproject-stage.com description: Staging instance - url: https://community.openproject.org description: Community instance security: - BasicAuth: [] tags: - description: "Work packages can be assigned to a sprint. This is employed in agile contexts such as Scrum or Kanban to group the work packages to be worked on within a defined time frame towards a defined goal.\n\n## Linked Properties\n\n| Link | Description | Type | Constraints | Supported operations |\n|:-------------------:|----------------------------------------- | ------------- | -------------------------------------------------------------- | -------------------- |\n| self | This sprint | Sprint | not null | READ |\n| definingWorkspace | The workspace in which the sprint is defined | Workspace | | READ |\n| status | The status the sprint is in | URN | | READ |\n\nThe status is represented as a URN and can have the following values:\n\n - **urn:openproject-org:api:v3:sprints:status:in_planning**: The sprint hasn't started yet, it is planned.\n - **urn:openproject-org:api:v3:sprints:status:active**: The sprint is currently active.\n - **urn:openproject-org:api:v3:sprints:status:completed**: The sprint has finished.\n\n## Local Properties\n\n| Property | Description | Type | Constraints | Supported operations |\n| :---------: | --------------------------------------------- | ----------- | ----------- | -------------------- |\n| id | Sprint id | Integer | x > 0 | READ |\n| name | Sprint name | String | not null | READ |\n| description | | Formattable | | READ |\n| startDate | | Date | | READ |\n| finishDate | | Date | | READ |\n| createdAt | Time of creation | DateTime | not null | READ |\n| updatedAt | Time of the most recent change to the sprint | DateTime | not null | READ |" name: Sprints paths: /api/v3/projects/{id}/sprints: get: parameters: - description: ID of the project whose sprints will be listed example: '1' in: path name: id required: true schema: type: integer - description: 'JSON specifying filter conditions. Accepts the same format and filters as returned by the [sprints](https://www.openproject.org/docs/api/endpoints/sprints/) endpoint.' example: '[{ "definingWorkspace": { "operator": "=", "values": ["1"] }" }]' in: query name: filters required: false schema: type: string - description: Page number inside the requested collection. example: '25' in: query name: offset required: false schema: default: 1 type: integer - description: Number of elements to display per page. example: '25' in: query name: pageSize required: false schema: type: integer responses: '200': content: application/hal+json: schema: $ref: '#/components/schemas/SprintCollectionModel' examples: response: $ref: '#/components/examples/SprintCollectionResponse' description: OK headers: {} '403': content: application/hal+json: schema: $ref: '#/components/schemas/SprintCollectionModel' examples: response: $ref: '#/components/examples/SprintCollectionResponse' description: 'Returned if the user lacks permission to list sprints in the queried for project. **Required permission:** view sprints in the project.' headers: {} '404': content: application/hal+json: schema: $ref: '#/components/schemas/ErrorResponse' examples: response: value: _type: Error errorIdentifier: urn:openproject-org:api:v3:errors:NotFound message: The specified project does not exist. description: 'Returned if the project does not exist. **Required permission:** view sprints in the queried for project.' headers: {} tags: - Sprints description: List sprints in the project. The sprints might be ones native to the project or shared with it. This endpoint supports pagination and filtering. operationId: List_sprints_in_project summary: List sprints in project /api/v3/sprints: get: parameters: - description: 'JSON specifying filter conditions. Accepts the same format as returned by the [queries](https://www.openproject.org/docs/api/endpoints/queries/) endpoint. Currently supported filters are: + definingWorkspace: filters sprints based on the project they are defined in. This is opposed to the projects they are shared with.' example: '[{ "definingWorkspace": { "operator": "=", "values": ["1"] }" }]' in: query name: filters required: false schema: type: string - description: Page number inside the requested collection. example: '25' in: query name: offset required: false schema: default: 1 type: integer - description: Number of elements to display per page. example: '25' in: query name: pageSize required: false schema: type: integer responses: '200': content: application/hal+json: schema: $ref: '#/components/schemas/SprintCollectionModel' examples: response: $ref: '#/components/examples/SprintCollectionResponse' description: OK headers: {} tags: - Sprints description: List sprints visible to the user. This endpoint supports pagination and filtering. operationId: List_sprints summary: List sprints /api/v3/sprints/{id}: get: summary: Get sprint operationId: get_sprint tags: - Sprints description: Retrieves a sprint defined by its unique identifier. parameters: - description: Sprint id example: '1' in: path name: id required: true schema: type: integer responses: '200': description: OK content: application/hal+json: schema: $ref: '#/components/schemas/SprintModel' examples: response: $ref: '#/components/examples/SprintResponse' '404': content: application/hal+json: schema: $ref: '#/components/schemas/ErrorResponse' examples: response: value: _type: Error errorIdentifier: urn:openproject-org:api:v3:errors:NotFound message: The requested resource could not be found. description: 'Returned if the sprint does not exist or the client does not have sufficient permissions to see it. **Required permission:** view master backlogs (this will change to view sprints)' components: schemas: CollectionModel: type: object required: - _type - total - count - _links properties: _type: type: string enum: - Collection total: type: integer description: The total amount of elements available in the collection. minimum: 0 count: type: integer description: Actual amount of elements in this response. minimum: 0 _links: $ref: '#/components/schemas/CollectionLinks' SprintModel: type: object required: - id - _type - name - startDate - finishDate - createdAt - updatedAt properties: id: type: integer description: Sprint id minimum: 1 _type: type: string enum: - Sprint name: type: string description: Sprint name description: $ref: '#/components/schemas/Formattable' startDate: type: - string - 'null' format: date finishDate: type: - string - 'null' format: date createdAt: type: string format: date-time description: Time of creation updatedAt: type: string format: date-time description: Time of the most recent change to the sprint _links: type: object required: - self - definingWorkspace properties: self: allOf: - $ref: '#/components/schemas/Link' - description: 'This sprint **Resource**: Sprint' definingWorkspace: allOf: - $ref: '#/components/schemas/Link' - description: 'The workspace to which the sprint belongs. **Resource**: Workspace' status: allOf: - $ref: '#/components/schemas/Link' - description: "The current status of the sprint which can be any of:\n\n - *\"urn:openproject-org:api:v3:sprints:status:in_planning\"*: The sprint hasn't started yet, it is planned.\n - *\"urn:openproject-org:api:v3:sprints:status:active\"*: The sprint is currently active.\n - *\"urn:openproject-org:api:v3:sprints:status:completed\"*: The sprint has finished.\n\n**Resource**: N/A" CollectionLinks: type: object required: - self properties: self: allOf: - $ref: '#/components/schemas/Link' - description: 'This collection resource. **Resource**: Collection' Formattable: type: object required: - format properties: format: type: string enum: - plain - markdown - custom readOnly: true description: Indicates the formatting language of the raw text example: markdown raw: type: string description: The raw text, as entered by the user example: I **am** formatted! html: type: string readOnly: true description: The text converted to HTML according to the format example: I am formatted! example: format: markdown raw: I am formatted! html: I am formatted! Link: type: object required: - href properties: href: type: - string - 'null' description: URL to the referenced resource (might be relative) title: type: string description: Representative label for the resource templated: type: boolean default: false description: If true the href contains parts that need to be replaced by the client method: type: string default: GET description: The HTTP verb to use when requesting the resource payload: type: object description: The payload to send in the request to achieve the desired result identifier: type: string description: An optional unique identifier to the link object type: type: string description: The MIME-Type of the returned resource. example: href: /api/v3/work_packages method: POST SprintCollectionModel: allOf: - $ref: '#/components/schemas/CollectionModel' - type: object required: - _links - _embedded properties: _links: type: object required: - self properties: self: allOf: - $ref: '#/components/schemas/Link' - description: 'This sprint collection **Resource**: Collection' _embedded: type: object required: - elements properties: elements: type: array items: $ref: '#/components/schemas/SprintModel' ErrorResponse: type: object required: - _type - errorIdentifier - message properties: _embedded: type: object properties: details: type: object properties: attribute: type: string example: project _type: type: string enum: - Error errorIdentifier: type: string example: urn:openproject-org:api:v3:errors:PropertyConstraintViolation message: type: string example: Project can't be blank. examples: SprintResponse: description: A sprint resource example value: _type: Sprint id: 3 name: Sprint 11 startDate: '2026-02-02' finishDate: '2026-02-09' createdAt: '2026-02-06T09:30:49.157Z' updatedAt: '2026-02-10T09:53:21.620Z' _links: self: href: /api/v3/sprints/3 title: Sprint 11 definingWorkspace: href: /api/v3/projects/10 title: Scrum project status: href: urn:openproject-org:api:v3:sprints:status:in_planning title: In planning SprintCollectionResponse: description: Simple response of a sprint collection. value: _type: Collection total: 40 count: 20 pageSize: 20 offset: 1 _embedded: elements: - _type: Sprint id: 3 name: Sprint 11 startDate: '2026-02-02' finishDate: '2026-02-09' createdAt: '2026-02-06T09:30:49.157Z' updatedAt: '2026-02-10T09:53:21.620Z' _links: self: href: /api/v3/sprints/3 title: Sprint 11 definingWorkspace: href: /api/v3/projects/10 title: Scrum project status: href: urn:openproject-org:api:v3:sprints:status:in_planning title: In planning - _abbreviated: Further sprint resources shortened for brevity. _links: self: href: /api/v3/sprints?filters=%5B%5D&offset=1&pageSize=20 jumpTo: href: /api/v3/sprints?filters=%5B%5D&offset=%7Boffset%7D&pageSize=20 templated: true changeSize: href: /api/v3/sprints?filters=%5B%5D&offset=1&pageSize=%7Bsize%7D templated: true nextByOffset: href: /api/v3/sprints?filters=%5B%5D&offset=2&pageSize=20 securitySchemes: BasicAuth: type: http scheme: basic