List the OpenProject projects visible to the API user, with their identifiers. Paginated via pageSize and offset.

List work packages, newest-id last. Defaults to open items only in the default project. status must be open, closed, or all — "all" includes closed items. project: "all" searches across every project even when OPENPROJECT_PROJECT_ID is set.

Fetch one work package in full detail, including custom fields, priority, version, and time aggregates. When the local hours ledger is installed, hoursLedger reports the sheet side of the task's time separately — never summed with spentTime.

Create a work package. Returns the created id. Notifications are off unless notify=true. Every change to a tracked project needs one of these before work starts.

Update a work package. lockVersion is fetched automatically, so concurrent edits fail loudly rather than silently overwriting. Notifications are off unless notify=true.

Add a markdown comment to a work package. Notifications are off unless notify=true.

List the work package types available in a project, with their names.

List the time-entry activity categories (Management, Development, …) with their ids. Needed to log time under the right category.

List logged time. Hours are returned both as ISO-8601 duration and as a decimal, plus a total, so "how much time went into this" needs no arithmetic downstream.

Log time against a work package. Accepts decimal hours (1.5) or an ISO-8601 duration ("PT1H30M"). The entry is always attributed to the API key's own user — OpenProject makes that field read-only, so time cannot be logged on someone else's behalf. When the local hours ledger is installed, the result includes hoursLedger (the sheet's side for this task) so double-logging across the two ledgers is visible at the moment of the write.

List every status name, so an update can name one that exists.

List the principals that can own a work package, with their ids. Falls back from the project's assignable users to /principals to /users, so it works on a key that cannot read /api/v3/users. source reports which list answered.

List priority names, so a create or update can name one that exists.

List comments and activities on a work package.

List documents (the Documents module), newest first. A document is a titled container for attachments with a markdown description. APIv3 has no document create or delete (UI-only), so documents are read and updated only. project: "all" searches every project even when OPENPROJECT_PROJECT_ID is set.

Fetch one document in full detail: title, markdown description, project, dates, and its attachments (file name, size, type, status, download URL).

Update a document title and/or description. The description replaces the whole markdown body. Documents carry no lockVersion, so concurrent edits are last-write-wins — unlike work packages, the API offers no optimistic locking. The "description" {"raw": …} form documented for other resources corrupts the stored text on documents (verified on 17.3, contract unchanged through 17.7); a plain string is what the UI itself sends.

Upload a file to a document: the API key needs the manage_documents permission in the document's project. content is the file bytes as base64. The upload is capped at the instance's attachment size limit, read from /api/v3/configuration.