How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Visma Project Task API

The ProjectTask API from Visma — 2 operation(s) for projecttask.

Visma Project Task API is one of 193 APIs that Visma publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include ProjectTask. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, rate-limit docs, and a support channel.

This API exposes 4 operations across 2 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.finance.visma.net.

4 operations 2 paths 26 schemas 2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.finance.visma.net
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Visma Project Task API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (interactiveapi) using the authorizationCode flow, exposing 5 scopes.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

ProjectTask 4
GET
/v1/projecttask/{internalId}
Get project task information by internal id
ProjectTask_GetTaskByinternalId 2 params → 200202
PUT
/v1/projecttask/{internalId}
Update a specific Task
ProjectTask_PutByinternalId 3 params body → 204412202
POST
/v1/projecttask/{internalId}
Create a Task
ProjectTask_PostByinternalId 2 params body → 201202
GET
/v1/projecttask
Get all project tasks for one project
ProjectTask_GetAllTasks 30 params → 200202

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are TaskExtendedDto (23 properties), EmployeeDto (17 properties), contactInEmployeeDto (14 properties), ProjectTaskUpdateDto (10 properties). Each schema is shown below with its type and property counts.

taxCategoryInTaskExtendedDto
object
VAT category The tax category for the project task.
2 properties
TaskEmployeeUpdateDto
object
2 properties
visibilityInTaskExtendedDto
object
Information retrieved from the Summary tab
10 properties
DtoValueOfString
object
1 property
BranchNumberDto
object
2 properties
contactInEmployeeDto
object
General information tab Contact section
14 properties
rateTableInTaskExtendedDto
object
Rate table The rate table to be used in the allocation rules, if applicable.
2 properties
countyInAddressDto
object
County The county or province.
2 properties
countryInAddressDto
object
Country The country.
4 properties
DtoValueOfNullableOfProjTaskStatus
object
1 property
defSubInTaskExtendedDto
object
General ledger accounts tab Default values section Default subaccount The subaccount to be used as one of the sources of possible segment values for subaccount…
3 properties
BackgroundApiAcceptedDto
object
2 properties
employeeClassInEmployeeDto
object
Additional information about Employee User ///
2 properties
DtoValueOfNullableOfBoolean
object
1 property
AttributeIdValueDto
object
3 properties
DtoValueOfNullableOfDateTime
object
1 property
MetadataDto
object
2 properties
defAccrualAccountInTaskExtendedDto
object
General ledger accounts tab Default values section Accrual account The default accrual account to be used in project transactions for the project task.
3 properties
defAccrualSubInTaskExtendedDto
object
General ledger accounts tab Default values section Accrual subaccount The default accrual subaccount to be used in project transactions for the project task.
3 properties
addressInEmployeeDto
object
General information tab Address info section
8 properties
ProjectTaskUpdateDto
object
10 properties
branchInTaskExtendedDto
object
Summary tab Billing and Allocation settings Branch information: branch number and name.
2 properties
EmployeeDto
object
This class represents an Employee in EmployeeController. Used for getting data.
17 properties
VisibilityUpdateDto
object
10 properties
defAccountInTaskExtendedDto
object
General ledger accounts tab Default values section Default account The account to be used as one of the sources of possible accounts for the invoices and trans…
3 properties
TaskExtendedDto
object
23 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

visma-projecttask-api-openapi.yml Raw ↑

Other APIs Visma publishes across the network.

Visma Business NXT GraphQL API
Visma Account API
Visma Accounts API
Visma Agreements API
Visma Allocation Periods API
Visma Approval API
Visma App Store Activation Status API
Visma Article Account Codings API
Visma Article Labels API
Visma Articles API
Visma Attachment API
Visma Attachment Links API
Where this information came from

This is an independent, third-party profile of Visma Project Task API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.