OpenProject Activities API

## Local Properties | Property | Description | Type | Constraints | Supported operations | | :---------: | ------------- | ---- | ----------- | -------------------- | | id | Activity id | Integer | x > 0 | READ | | version | Activity version | Integer | x > 0 | READ | | comment | | Formattable | | READ / WRITE | | details | | Array of Formattable | | READ | | createdAt | Time of creation | DateTime | | READ | | updatedAt | Time of update | DateTime | | READ | Activity can be either _type `Activity` or _type `Activity::Comment`.

OpenAPI Specification

openproject-activities-api-openapi.yml Raw ↑
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 Activities 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: '## Local Properties


    | Property    | Description      | Type                 | Constraints | Supported operations |

    | :---------: | -------------    | ----                 | ----------- | -------------------- |

    | id          | Activity id      | Integer              | x > 0       | READ                 |

    | version     | Activity version | Integer              | x > 0       | READ                 |

    | comment     |                  | Formattable          |             | READ / WRITE         |

    | details     |                  | Array of Formattable |             | READ                 |

    | createdAt   | Time of creation | DateTime             |             | READ                 |

    | updatedAt   | Time of update   | DateTime             |             | READ                 |


    Activity can be either _type `Activity` or _type `Activity::Comment`.'
  name: Activities
paths:
  /api/v3/activities/{id}:
    get:
      summary: Get an activity
      operationId: get_activity
      tags:
      - Activities
      description: Returns the requested activity resource identified by its unique id.
      parameters:
      - name: id
        description: Activity id
        in: path
        required: true
        schema:
          type: integer
        example: 1
      responses:
        '200':
          description: OK
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/ActivityModel'
              examples:
                response:
                  $ref: '#/components/examples/ActivityResponse'
    patch:
      summary: Update activity
      operationId: update_activity
      tags:
      - Activities
      description: Updates an activity's comment and, on success, returns the updated activity.
      parameters:
      - name: id
        description: Activity id
        in: path
        required: true
        schema:
          type: integer
        example: 1
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ActivityCommentWriteModel'
      responses:
        '200':
          description: OK
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/ActivityModel'
              examples:
                response:
                  $ref: '#/components/examples/ActivityResponse'
        '400':
          $ref: '#/components/responses/InvalidRequestBody'
        '403':
          description: 'Returned if the client does not have sufficient permissions.


            **Required permission:** edit journals'
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                response:
                  value:
                    _type: Error
                    errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
                    message: You are not allowed to edit the comment of this journal entry.
        '406':
          $ref: '#/components/responses/MissingContentType'
        '415':
          $ref: '#/components/responses/UnsupportedMediaType'
        '422':
          description: Returned if the client tries to modify a read-only property.
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                response:
                  value:
                    _type: Error
                    errorIdentifier: urn:openproject-org:api:v3:errors:PropertyIsReadOnly
                    message: The ID of an activity can't be changed.
  /api/v3/activities/{id}/attachments:
    get:
      summary: List attachments by activity
      operationId: list_activity_attachments
      tags:
      - Activities
      description: List all attachments of a single activity.
      parameters:
      - name: id
        description: ID of the activity whose attachments will be listed
        in: path
        required: true
        schema:
          type: integer
        example: 1
      responses:
        '200':
          description: OK
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/Attachments_Model'
        '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 activity does not exist or the client does not have sufficient permissions\nto see it.\n\n**Required permission:** \n- `view_work_packages`\n- for internal comments: `view_internal_comments`\n\n*Note: A client without sufficient permissions shall not be able to test for the existence of an activity.\nThat's why a 404 is returned here, even if a 403 might be more appropriate.*"
    post:
      summary: Add attachment to activity
      operationId: create_activity_attachment
      tags:
      - Activities
      description: Adds an attachment to the specified activity.
      parameters:
      - name: id
        description: ID of the activity to receive the attachment
        in: path
        required: true
        schema:
          type: integer
        example: 1
      requestBody:
        content:
          multipart/form-data:
            schema:
              $ref: '#/components/schemas/FileUploadForm'
      responses:
        '200':
          description: OK
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/AttachmentModel'
        '400':
          description: 'Returned if the client sends a not understandable request. Reasons include:


            * Omitting one of the required parts (metadata and file)


            * sending unparsable JSON in the metadata part'
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                response:
                  value:
                    _type: Error
                    errorIdentifier: urn:openproject-org:api:v3:errors:InvalidRequestBody
                    message: The request could not be parsed as JSON.
        '403':
          description: 'Returned if the client does not have sufficient permissions.


            **Required permission:** view_work_packages or view_internal_comments (for internal comments)


            *Note that you will only receive this error, if you are at least allowed to see the activity*'
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                response:
                  value:
                    _type: Error
                    errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
                    message: You are not allowed to add attachments to this activity.
        '404':
          description: 'Returned if the activity does not exist or the client does not have sufficient permissions

            to see it.


            **Required permission:** view_work_packages or view_internal_comments (for internal comments)


            *Note: A client without sufficient permissions shall not be able to test for the existence of an activity.

            That''s why a 404 is returned here, even if a 403 might be more appropriate.*'
          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.
        '406':
          $ref: '#/components/responses/MissingContentType'
        '415':
          $ref: '#/components/responses/UnsupportedMediaType'
        '422':
          description: 'Returned if the client tries to send an invalid attachment.

            Reasons are:


            * Omitting the file name (`fileName` property of metadata part)


            * Sending a file that is too large'
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                response:
                  value:
                    _type: Error
                    errorIdentifier: urn:openproject-org:api:v3:errors:PropertyConstraintViolation
                    message: File is too large (maximum size is 5242880 Bytes).
  /api/v3/activities/{id}/emoji_reactions:
    get:
      summary: List emoji reactions by activity
      operationId: list_activity_emoji_reactions
      tags:
      - Activities
      description: List all emoji reactions of a single activity.
      parameters:
      - name: id
        description: ID of the activity whose emoji reactions will be listed
        in: path
        required: true
        schema:
          type: integer
        example: '1'
      responses:
        '200':
          description: OK
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/EmojiReactions_Model'
        '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 activity does not exist or the client does not have sufficient permissions

            to see it.


            **Required permission:**

            - `view_work_packages`

            - for internal comments: `view_internal_comments`


            *Note: A client without sufficient permissions shall not be able to test for the existence of an activity.

            That''s why a 404 is returned here, even if a 403 might be more appropriate.*'
    patch:
      summary: Toggle emoji reaction for an activity
      operationId: toggle_activity_emoji_reaction
      tags:
      - Activities
      description: 'Toggle an emoji reaction for a given activity. If the user has already reacted with the given emoji,

        the reaction will be removed. Otherwise, a new reaction will be created.


        **Note:** The response contains the complete collection of all emoji reactions for this activity.


        **Required permission:**

        - `add_work_package_comments`

        - for internal comments: `add_internal_comments`'
      parameters:
      - name: id
        description: ID of the activity to toggle emoji reaction for
        in: path
        required: true
        schema:
          type: integer
        example: '1'
      requestBody:
        required: true
        content:
          application/hal+json:
            schema:
              type: object
              required:
              - reaction
              properties:
                reaction:
                  type: string
                  description: The emoji reaction identifier
                  example: thumbs_up
                  enum:
                  - thumbs_up
                  - thumbs_down
                  - grinning_face_with_smiling_eyes
                  - confused_face
                  - heart
                  - party_popper
                  - rocket
                  - eyes
      responses:
        '200':
          description: OK
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/EmojiReactionModel'
        '400':
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                response:
                  value:
                    _type: Error
                    errorIdentifier: urn:openproject-org:api:v3:errors:BadRequest
                    message: 'Bad request: reaction does not have a valid value'
          description: Returned if the request is invalid. For example, if the reaction is not valid.
        '403':
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                response:
                  value:
                    _type: Error
                    errorIdentifier: urn:openproject-org:api:v3:errors:MissingPermission
                    message: You are not authorized to access this resource.
          description: Returned if the client does not have sufficient permissions to toggle the emoji reaction for the activity.
        '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 activity does not exist or the client does not have sufficient permissions

            to see it.'
  /api/v3/work_packages/{id}/activities_emoji_reactions:
    get:
      summary: List emoji reactions by work package activities
      operationId: list_work_package_activities_emoji_reactions
      tags:
      - Activities
      description: List all emoji reactions of all activities of a single work package.
      parameters:
      - name: id
        description: ID of the work package whose activities' emoji reactions will be listed
        in: path
        required: true
        schema:
          type: integer
        example: 1
      responses:
        '200':
          description: OK
          content:
            application/hal+json:
              schema:
                $ref: '#/components/schemas/EmojiReactions_Model'
        '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 work package does not exist or the client does not have sufficient permissions

            to see it.


            **Required permission:**

            - `view_work_packages`

            - for internal comments: `view_internal_comments`


            *Note: A client without sufficient permissions shall not be able to test for the existence of a work package.

            That''s why a 404 is returned here, even if a 403 might be more appropriate.*'
components:
  schemas:
    ActivityModel:
      type: object
      properties:
        _type:
          type: string
          enum:
          - Activity::Comment
        id:
          type: integer
          description: Activity id
          minimum: 1
        version:
          type: integer
          description: Activity version
          minimum: 1
        comment:
          $ref: '#/components/schemas/Formattable'
        details:
          type: array
          items:
            $ref: '#/components/schemas/Formattable'
        internal:
          type: boolean
          description: Whether this activity is internal (only visible to users with view_internal_comments permission)
        createdAt:
          type: string
          format: date-time
          description: Time of creation
        updatedAt:
          type: string
          format: date-time
          description: Time of update
        _embedded:
          type: object
          properties:
            attachments:
              allOf:
              - $ref: '#/components/schemas/Attachments_Model'
              - description: Collection of attachments for this activity
            workPackage:
              allOf:
              - $ref: '#/components/schemas/WorkPackageModel'
              - description: 'The work package this activity belongs to


                  # Conditions


                  Only embedded when the `journable` of the activity is a work package'
            emojiReactions:
              allOf:
              - $ref: '#/components/schemas/EmojiReactions_Model'
              - description: Collection of emoji reactions for this activity
        _links:
          type: object
          properties:
            self:
              allOf:
              - $ref: '#/components/schemas/Link'
              - description: 'This activity


                  **Resource**: Activity'
            workPackage:
              allOf:
              - $ref: '#/components/schemas/Link'
              - description: 'The work package this activity belongs to


                  **Resource**: WorkPackage'
            user:
              allOf:
              - $ref: '#/components/schemas/Link'
              - description: 'The user who created this activity


                  **Resource**: Principal'
            update:
              allOf:
              - $ref: '#/components/schemas/Link'
              - description: Update this activity
            attachments:
              allOf:
              - $ref: '#/components/schemas/Link'
              - description: 'The attachment collection of this activity


                  **Resource**: Attachments'
            addAttachment:
              allOf:
              - $ref: '#/components/schemas/Link'
              - description: 'Attach a file to the activity


                  # Conditions


                  **Permissions**:

                  - `add_work_package_comments`

                  - for internal comments: `add_internal_comments`'
            emojiReactions:
              allOf:
              - $ref: '#/components/schemas/Link'
              - description: 'The emoji reactions collection of this activity


                  **Resource**: EmojiReactions'
      example:
        id: 1
        _type: Activity::Comment
        _embedded:
          attachments:
            _type: Collection
            total: 1
            count: 1
            _embedded:
              elements:
              - _type: Attachment
                id: 30388
                fileName: Task_Ensure_financing___4___OpenProject_DEV.jpeg
                fileSize: 540992
                description:
                  format: plain
                  raw: ''
                  html: ''
                status: uploaded
                contentType: image/jpeg
                digest:
                  algorithm: md5
                  hash: d02d312b25383b595a9fa10f1a8999fe
                createdAt: '2025-04-08T15:37:19.275Z'
                _links:
                  self:
                    href: /api/v3/attachments/30388
                    title: Task_Ensure_financing___4___OpenProject_DEV.jpeg
                  author:
                    href: /api/v3/users/435
                    title: Firstname
                  container:
                    href: /api/v3/activities/79090
                  staticDownloadLocation:
                    href: /api/v3/attachments/30388/content
                  downloadLocation:
                    href: /api/v3/attachments/30388/content
                  delete:
                    href: /api/v3/attachments/30388
                    method: delete
            _links:
              self:
                href: /api/v3/activities/79090/attachments
          emojiReactions:
            _type: Collection
            total: 2
            count: 2
            _embedded:
              elements:
              - _type: EmojiReaction
                id: 1-thumbs_up
                reaction: thumbs_up
                emoji: 👍
                reactionsCount: 3
                firstReactionAt: '2024-04-08T15:37:19.275Z'
                _links:
                  self:
                    href: /api/v3/emoji_reactions/1-thumbs_up
                  reactable:
                    href: /api/v3/activities/1
                  reactingUsers:
                  - href: /api/v3/users/435
                    title: John Doe
                  - href: /api/v3/users/436
                    title: Jane Smith
                  - href: /api/v3/users/437
                    title: Bob Johnson
              - _type: EmojiReaction
                id: 1-heart
                reaction: heart
                emoji: ❤️
                reactionsCount: 1
                firstReactionAt: '2024-04-08T15:38:19.275Z'
                _links:
                  self:
                    href: /api/v3/emoji_reactions/1-heart
                  reactable:
                    href: /api/v3/activities/1
                  reactingUsers:
                  - href: /api/v3/users/435
                    title: John Doe
            _links:
              self:
                href: /api/v3/activities/1/emoji_reactions
          workPackage:
            _type: WorkPackage
            id: 10403
            lockVersion: 2
            subject: Ensure financing
            description:
              format: markdown
              raw: Lorem ipsum dolor sit amet.
              html: <p>Lorem ipsum dolor sit amet.</p>
            scheduleManually: true
            startDate: null
            dueDate: null
            derivedStartDate: null
            derivedDueDate: null
            estimatedTime: null
            derivedEstimatedTime: null
            derivedRemainingTime: null
            duration: null
            ignoreNonWorkingDays: false
            percentageDone: null
            derivedPercentageDone: null
            createdAt: '2025-03-24T13:11:09.480Z'
            updatedAt: '2025-04-14T11:00:02.411Z'
            _links:
              self:
                href: /api/v3/work_packages/10403
                title: Ensure financing
              type:
                href: /api/v3/types/1
                title: Task
              status:
                href: /api/v3/statuses/1
                title: New
              project:
                href: /api/v3/projects/918
                title: RVC Test
              schema:
                href: /api/v3/work_packages/schemas/11-2
              author:
                href: /api/v3/users/1
                title: OpenProject Admin - admin
              priority:
                href: /api/v3/priorities/2
                title: Normal
              ancestors: []
        _links:
          self:
            href: /api/v3/activity/1
            title: Priority changed from High to Low
          workPackage:
            href: /api/v3/work_packages/1
            title: quis numquam qui voluptatum quia praesentium blanditiis nisi
          user:
            href: /api/v3/users/1
            title: John Sheppard - admin


# --- truncated at 32 KB (70 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/openproject/refs/heads/main/openapi/openproject-activities-api-openapi.yml