Resource

Activity

Tasks and appointments on a project — the records behind origo's «Aktiviteter» screen. Full CRUD; the delete closes the activity by default and can be asked to remove it permanently.

An activity is one unit of work on a project: a name and a free-text description, a responsible person, a status, a due date, hour estimates, and the type, priority, severity and resolution classifications the project's template offers. Every activity belongs to exactly one project — projectId is required both when you create one and when you replace one. Note what the shape does not carry: there is no start or end time, and no field for time actually spent. estimate and etc (estimate to complete) are forward-looking hour figures and dueDate is a plain local date, so an activity is the task or appointment record itself rather than a time entry.

Status is not writable through any endpoint on this page: a new activity starts at its project's default status, and neither the replace body nor the merge patch can move it.

The endpoint reference below is kept in English in both language trees. It mirrors the API contract verbatim and there is no generator to rebuild it from, so a translated copy would drift from the API the first time an endpoint changes.

Endpoints

Eight endpoints, in the order they are documented below.

• POST /activity — Create an activity
• GET /activity/{activityId} — Get an activity
• GET /activity — List activities
• GET /activity/cursor — List activities by cursor
• GET /activity/timeline — List activities by change time
• PUT /activity/{activityId} — Replace an activity
• PATCH /activity/{activityId} — Partially update an activity
• DELETE /activity/{activityId} — Close or delete an activity

Every endpoint on this page can additionally answer the shared errors — 401, 403, 404 (unknown instance) and 500. They are documented once, under Errors and troubleshooting.

curl -X POST "https://api.visena.example/acme/api/v1/en/activity" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Kickoff meeting",
    "projectId": "pJ7wN2",
    "dueDate": "2026-09-15"
  }'

curl "https://api.visena.example/acme/api/v1/en/activity/aT4cV9" \
  -H "Authorization: Bearer $TOKEN"

curl "https://api.visena.example/acme/api/v1/en/activity?projectId=pJ7wN2&offset=0&limit=20" \
  -H "Authorization: Bearer $TOKEN"

curl "https://api.visena.example/acme/api/v1/en/activity/cursor?limit=100" \
  -H "Authorization: Bearer $TOKEN"

Before you build a synchronisation on the cursor or the timeline read mode, read their sync semantics: which of the two yields one consistent extract that has to be walked in a single pass, which one you resume from, why delivery is at-least-once so you de-duplicate by id, and what neither of them reports about rows that disappear. The site sets all of that out once, for every resource, under Lists, paging and sync.

curl "https://api.visena.example/acme/api/v1/en/activity/timeline?since=2026-08-20T02:00:00Z" \
  -H "Authorization: Bearer $TOKEN"

curl -X PUT "https://api.visena.example/acme/api/v1/en/activity/aT4cV9" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Kickoff meeting",
    "projectId": "pJ7wN2",
    "dueDate": "2026-09-22"
  }'

curl -X PATCH "https://api.visena.example/acme/api/v1/en/activity/aT4cV9" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/merge-patch+json" \
  -d '{
    "dueDate": "2026-09-22",
    "responsiblePersonId": "xK9mQ2"
  }'

curl -X DELETE "https://api.visena.example/acme/api/v1/en/activity/aT4cV9?mode=close" \
  -H "Authorization: Bearer $TOKEN"

Object shapes

The request and response bodies used above, in the order they are first referenced.

ActivityCreateDto

ActivityResponseDto

ActivityRefDto

Priority.

ActivityOffsetListResponse

ActivityListItemDto

The activities on this page, always in ascending order.

CompanyRefDto

The company the owning project belongs to, if any.

OrgNumberDto

Active organizational (registration) numbers; at most one per company.

CountryRefDto

Country this organizational number is registered in.

ActivityListLinks

Navigation links for this page.

ActivityCursorListResponse

ActivityUpdateDto