Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/visma-projecttask-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Visma.net ERP Project Task API
version: v1
servers:
- url: https://api.finance.visma.net
tags:
- name: ProjectTask
paths:
/v1/projecttask/{internalId}:
get:
tags:
- ProjectTask
summary: Get project task information by internal id
description: 'Data for a single project task.
The response headers include an ETag after a successful GET operation.'
operationId: ProjectTask_GetTaskByinternalId
parameters:
- name: internalId
in: path
description: The organisation code.
required: true
schema:
type: integer
format: int32
- name: erp-api-background
in: header
description: 'Accepts the request and queues it to be executed in the background by our least busy worker. Responds with 202 Accepted and a document containing a JobId reference and details state location.
Supported values:
* a URL: when the background operation is finished, a notification will be posted to the URL with a document containing a reference id, status code and a details state location.
* "none" (without quotes): Fire and forget; no notification will be sent when background operation is finished.
* "subscription[:<name_1>=<value_1>,..,<name_n>=<value_n>]" (without quotes): when the background operation is finsihed, a notification is posted to the Webhook subscription set up in Developer Portal for your integration client.
Optionally a set of name-value pairs can be added. These will be sent as headers in the POST request to the Webhook subscription''s url.
To find status and details of a background-api operation, GET .. v1/background/{id}. To get the response payload of a background-api operation, if any, GET .. v1/background/{id}/content'
schema:
type: string
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/TaskExtendedDto'
text/json:
schema:
$ref: '#/components/schemas/TaskExtendedDto'
'202':
description: Server accepted and queued the request for background execution.
content:
application/json:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
text/json:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
security:
- interactiveapi: []
put:
tags:
- ProjectTask
summary: Update a specific Task
description: 'Response Message has StatusCode No Content if PUT operation succeed.
Response Message has StatusCode BadRequest if PUT operation failed.
The response headers include an ETag after a successful PUT operation.'
operationId: ProjectTask_PutByinternalId
parameters:
- name: internalId
in: path
description: Identifies the task by its internalID
required: true
schema:
type: integer
format: int32
- name: erp-api-background
in: header
description: 'Accepts the request and queues it to be executed in the background by our least busy worker. Responds with 202 Accepted and a document containing a JobId reference and details state location.
Supported values:
* a URL: when the background operation is finished, a notification will be posted to the URL with a document containing a reference id, status code and a details state location.
* "none" (without quotes): Fire and forget; no notification will be sent when background operation is finished.
* "subscription[:<name_1>=<value_1>,..,<name_n>=<value_n>]" (without quotes): when the background operation is finsihed, a notification is posted to the Webhook subscription set up in Developer Portal for your integration client.
Optionally a set of name-value pairs can be added. These will be sent as headers in the POST request to the Webhook subscription''s url.
To find status and details of a background-api operation, GET .. v1/background/{id}. To get the response payload of a background-api operation, if any, GET .. v1/background/{id}/content'
schema:
type: string
- name: If-Match
in: header
description: 'The If-Match HTTP header allows clients to update a resource only if its current version matches a specific ETag. This mechanism helps prevent conflicts when multiple clients attempt to modify the same resource simultaneously.
The If-Match header should be included in the request headers using the following syntax: If-Match: "etag_value"
* If the update is successful, the server responds with 204 No Content and includes the new ETag value in the response headers.
* If the ETag on the server does not match the value provided in the If-Match header, the server responds with 412 Precondition Failed.'
schema:
type: string
requestBody:
description: Defines the data for the Task to update
content:
application/json:
schema:
$ref: '#/components/schemas/ProjectTaskUpdateDto'
text/json:
schema:
$ref: '#/components/schemas/ProjectTaskUpdateDto'
application/xml:
schema:
$ref: '#/components/schemas/ProjectTaskUpdateDto'
text/xml:
schema:
$ref: '#/components/schemas/ProjectTaskUpdateDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/ProjectTaskUpdateDto'
required: true
x-bodyName: projectTaskUpdateDto
responses:
'204':
description: NoContent
content:
application/json:
schema:
type: object
text/json:
schema:
type: object
'412':
description: Project Task version does not match with If-Match header
content:
application/json: {}
text/json: {}
'202':
description: Server accepted and queued the request for background execution.
content:
application/json:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
text/json:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
security:
- interactiveapi: []
post:
tags:
- ProjectTask
summary: Create a Task
description: 'Response Message has StatusCode Created if POST operation succeed.
Response Message has StatusCode BadRequest or InternalServerError if POST operation failed.
The response headers include an ETag after a successful POST operation.'
operationId: ProjectTask_PostByinternalId
parameters:
- name: internalId
in: path
description: Identifies the project by its internalID
required: true
schema:
type: integer
format: int32
- name: erp-api-background
in: header
description: 'Accepts the request and queues it to be executed in the background by our least busy worker. Responds with 202 Accepted and a document containing a JobId reference and details state location.
Supported values:
* a URL: when the background operation is finished, a notification will be posted to the URL with a document containing a reference id, status code and a details state location.
* "none" (without quotes): Fire and forget; no notification will be sent when background operation is finished.
* "subscription[:<name_1>=<value_1>,..,<name_n>=<value_n>]" (without quotes): when the background operation is finsihed, a notification is posted to the Webhook subscription set up in Developer Portal for your integration client.
Optionally a set of name-value pairs can be added. These will be sent as headers in the POST request to the Webhook subscription''s url.
To find status and details of a background-api operation, GET .. v1/background/{id}. To get the response payload of a background-api operation, if any, GET .. v1/background/{id}/content'
schema:
type: string
requestBody:
description: Defines the data for the Task to update
content:
application/json:
schema:
$ref: '#/components/schemas/ProjectTaskUpdateDto'
text/json:
schema:
$ref: '#/components/schemas/ProjectTaskUpdateDto'
application/xml:
schema:
$ref: '#/components/schemas/ProjectTaskUpdateDto'
text/xml:
schema:
$ref: '#/components/schemas/ProjectTaskUpdateDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/ProjectTaskUpdateDto'
required: true
x-bodyName: projectTaskUpdateDto
responses:
'201':
description: Created
content:
application/json:
schema:
type: object
text/json:
schema:
type: object
'202':
description: Server accepted and queued the request for background execution.
content:
application/json:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
text/json:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
security:
- interactiveapi: []
/v1/projecttask:
get:
tags:
- ProjectTask
summary: Get all project tasks for one project
operationId: ProjectTask_GetAllTasks
parameters:
- name: projectId
in: query
description: Identifies the Project
schema:
type: string
- name: publicId
in: query
description: Identifies the project by publicId
schema:
type: string
format: uuid
- name: projectInternalId
in: query
description: Identifies the project by internal id
schema:
type: integer
format: int32
- name: description
in: query
description: Identifies the Project task description
schema:
type: string
- name: taskCd
in: query
description: Identifies the Project task ID
schema:
type: string
- name: taskCdDesc
in: query
description: Identifies the Project task ID and description
schema:
type: string
- name: status
in: query
description: The status of the document.
schema:
enum:
- Planned
- Active
- Cancelled
- Canceled
- Completed
type: string
- name: expandAttribute
in: query
description: Expands project atributes
schema:
type: boolean
- name: visibleInAp
in: query
description: If the project task is visible in the Supplier ledger
schema:
type: boolean
- name: visibleInAr
in: query
description: If the project task is visible in the Customer ledger
schema:
type: boolean
- name: visibleInCa
in: query
description: If the project task is visible in the Cash management workspace
schema:
type: boolean
- name: visibleInCr
in: query
description: If the project task is visible in the CRM workspace
schema:
type: boolean
- name: visibleInEa
in: query
description: If the project task is visible in the Expense workspace
schema:
type: boolean
- name: visibleInGl
in: query
description: If the project task is visible in the General ledger workspace
schema:
type: boolean
- name: visibleInIn
in: query
description: If the project task is visible in the Inventory workspace
schema:
type: boolean
- name: visibleInPo
in: query
description: If the project task is visible in the Purchases workspace
schema:
type: boolean
- name: visibleInSo
in: query
description: If the project task is visible in the Sales workspace
schema:
type: boolean
- name: visibleInTa
in: query
description: If the project task is visible in the Time entities workspace
schema:
type: boolean
- name: restrictedEmployee
in: query
description: Id of the employee where access restrictions apply
schema:
type: string
- name: restrictedUser
in: query
description: Id of the Odp User where access restrictions apply
schema:
type: integer
format: int64
- name: greaterThanValue
in: query
description: Greater than value. The item which is the object for this, varies from API to API.
schema:
type: string
- name: numberToRead
in: query
description: This field has been deprecated and will be removed in future versions. Use pagenumber and pagesize for pagination purposes. Pagenumber and pagesize does not work with NumberToRead and SkipRecords.
schema:
type: integer
format: int32
- name: skipRecords
in: query
description: This field has been deprecated and will be removed in future versions. Use pagenumber and pagesize for pagination purposes. Pagenumber and pagesize does not work with NumberToRead and SkipRecords.
schema:
type: integer
format: int32
- name: lastModifiedDateTime
in: query
description: 'This value, generated by the system, indicates the last time the record was modified. Use it to retrieve all records that have been modified since that time, up to the present.
Accepted format:
* ```yyyy-MM-dd```
* ```yyyy-MM-dd HH:mm:ss```
* ```yyyy-MM-dd HH:mm:ss.FFF```
* ```yyyy-MM-ddTHH:mm:ss```
* ```yyyy-MM-ddTHH:mm:ss.FFF```
_Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__.'
schema:
type: string
- name: lastModifiedDateTimeCondition
in: query
description: 'This value represents the condition to be applied when retrieving records.
Accepted values (without the single quotes):
* ''>'' for greater than
* ''<'' for less than
* ''>='' for greater than or equal
* ''<='' for less than or equal
_Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__.'
schema:
type: string
- name: createdDateTime
in: query
description: 'This value, generated by the system, indicates the creation date and time. Use it to retrieve all records that have been created since that time, up to the present.
Accepted format:
* ```yyyy-MM-dd```
* ```yyyy-MM-dd HH:mm:ss```
* ```yyyy-MM-dd HH:mm:ss.FFF```
* ```yyyy-MM-ddTHH:mm:ss```
* ```yyyy-MM-ddTHH:mm:ss.FFF```
_Note:_ __CreatedDateTime__ and __CreatedDateTimeCondition__ are __mutually inclusive__.'
schema:
type: string
- name: createdDateTimeCondition
in: query
description: 'This value represents the condition to be applied when retrieving records.
Accepted values (without the single quotes):
* ''>'' for greater than
* ''<'' for less than
* ''>='' for greater than or equal
* ''<='' for less than or equal
_Note:_ __CreatedDateTime__ and __CreatedDateTimeCondition__ are __mutually inclusive__.'
schema:
type: string
- name: pageNumber
in: query
description: Pagination parameter. Page number.
schema:
type: integer
format: int32
- name: pageSize
in: query
description: 'Pagination parameter. Number of items to be collected.
Please use a page size lower or equal to the allowed max page size which is returned as part of the metadata information.
If requested page size is greater than allowed max page size, request will be limited to max page size.'
schema:
type: integer
format: int32
- name: erp-api-background
in: header
description: 'Accepts the request and queues it to be executed in the background by our least busy worker. Responds with 202 Accepted and a document containing a JobId reference and details state location.
Supported values:
* a URL: when the background operation is finished, a notification will be posted to the URL with a document containing a reference id, status code and a details state location.
* "none" (without quotes): Fire and forget; no notification will be sent when background operation is finished.
* "subscription[:<name_1>=<value_1>,..,<name_n>=<value_n>]" (without quotes): when the background operation is finsihed, a notification is posted to the Webhook subscription set up in Developer Portal for your integration client.
Optionally a set of name-value pairs can be added. These will be sent as headers in the POST request to the Webhook subscription''s url.
To find status and details of a background-api operation, GET .. v1/background/{id}. To get the response payload of a background-api operation, if any, GET .. v1/background/{id}/content'
schema:
type: string
responses:
'200':
description: OK
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/TaskExtendedDto'
text/json:
schema:
type: array
items:
$ref: '#/components/schemas/TaskExtendedDto'
'202':
description: Server accepted and queued the request for background execution.
content:
application/json:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
text/json:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
security:
- interactiveapi: []
components:
schemas:
BackgroundApiAcceptedDto:
type: object
properties:
id:
type: string
stateLocation:
type: string
branchInTaskExtendedDto:
properties:
number:
type: string
description: Click the magnifier. > The identifier.
name:
type: string
description: Click the magnifier. > The name.
description: 'Summary tab > Billing and Allocation settings > Branch information: branch number and name.'
TaskEmployeeUpdateDto:
type: object
properties:
operation:
enum:
- Insert
- Update
- Delete
type: string
employeeId:
$ref: '#/components/schemas/DtoValueOfString'
VisibilityUpdateDto:
type: object
properties:
visibleInGl:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
visibleInAp:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
visibleInAr:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
visibleInSo:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
visibleInPo:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
visibleInEa:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
visibleInTa:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
visibleInIn:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
visibleInCa:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
visibleInCr:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
contactInEmployeeDto:
properties:
employeeContact:
type: string
description: Employee contact > The link to the contact record associated with the employee.
title:
enum:
- Doctor
- Miss
- Mr
- Mrs
- Ms
- Prof
type: string
description: Title > The courtesy title to be used for the employee.
firstName:
type: string
description: First name > The first name of the employee.
midName:
type: string
description: Middle name > The middle name of the employee.
lastName:
type: string
description: 'Mandatory field: Last name* > The last name of the employee.'
phone3:
type: string
description: Phone 3 > An additional phone number of the employee.
contactId:
type: integer
format: int32
name:
type: string
description: Name > The legal name of to appear on the documents.
attention:
type: string
description: Attention > The attention line as it is used in your customer's/supplier's/company's business letters. The intention of this line is to direct the letter to the right person if the letter is not addressed to any specific person.
email:
type: string
description: Email > The email address of the customer/supplier/company as a business entity.
web:
type: string
description: Web > The website of the company, if one exists.
phone1:
type: string
description: Phone 1 > The default phone number.
phone2:
type: string
description: Phone 2 > An additional phone number.
fax:
type: string
description: Fax > The fax number.
description: General information tab > Contact section >
DtoValueOfNullableOfDateTime:
type: object
properties:
value:
type: string
format: date-time
DtoValueOfNullableOfBoolean:
type: object
properties:
value:
type: boolean
countryInAddressDto:
properties:
id:
type: string
description: 'Mandatory field: Country ID* > The unique two-letter country ID according to international standard ISO 3166.'
name:
type: string
description: 'Mandatory field: Country name* > The complete name of the country.'
errorInfo:
type: string
metadata:
$ref: '#/components/schemas/MetadataDto'
description: Country > The country.
DtoValueOfNullableOfProjTaskStatus:
type: object
properties:
value:
enum:
- Planned
- Active
- Cancelled
- Canceled
- Completed
type: string
rateTableInTaskExtendedDto:
properties:
id:
type: string
description: Click on the magnifier. > The identifier.
description:
type: string
description: Click on the magnifier. > The description.
description: Rate table > The rate table to be used in the allocation rules, if applicable.
defAccountInTaskExtendedDto:
properties:
type:
type: string
number:
type: string
description: Number of item
description:
type: string
description: Name of item/description
description: 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 transactions for the project task.
addressInEmployeeDto:
properties:
addressId:
type: integer
format: int32
addressLine1:
type: string
description: Address 1 > The first line of the customer's/supplier's/company's/employee's contact address.
addressLine2:
type: string
description: Address 2 > The second line of the address.
addressLine3:
type: string
description: Address 3 > The third line of the address.
postalCode:
type: string
description: Postcode > The postcode.
city:
type: string
description: City > The city.
country:
$ref: '#/components/schemas/countryInAddressDto'
county:
$ref: '#/components/schemas/countyInAddressDto'
description: General information tab > Address info section >
ProjectTaskUpdateDto:
type: object
properties:
taskId:
$ref: '#/components/schemas/DtoValueOfString'
description:
$ref: '#/components/schemas/DtoValueOfString'
plannedStart:
$ref: '#/components/schemas/DtoValueOfNullableOfDateTime'
plannedEnd:
$ref: '#/components/schemas/DtoValueOfNullableOfDateTime'
startDate:
$ref: '#/components/schemas/DtoValueOfNullableOfDateTime'
rateTable:
$ref: '#/components/schemas/DtoValueOfString'
status:
$ref: '#/components/schemas/DtoValueOfNullableOfProjTaskStatus'
visibility:
$ref: '#/components/schemas/VisibilityUpdateDto'
restrictEmployees:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
employees:
type: array
items:
$ref: '#/components/schemas/TaskEmployeeUpdateDto'
MetadataDto:
type: object
properties:
totalCount:
type: integer
format: int64
maxPageSize:
type: integer
format: int64
BranchNumberDto:
type: object
properties:
number:
type: string
description: Click the magnifier. > The identifier.
name:
type: string
description: Click the magnifier. > The name.
EmployeeDto:
type: object
properties:
employeeUserId:
type: string
description: Employee internal user ID. This is the ID of the user linked to the employee
format: uuid
example: 00000000-0000-0000-0000-000000000000
employeeId:
type: integer
description: 'Mandatory field: The top part > Employee ID* > The unique identifier, which is assigned to the employee in accordance with the configuration of the EMPLOYEE segmented key.'
format: int32
employeeNumber:
type: string
description: General information tab > Employee settings section > Employee ref. no. > A reference number for the employee.
employeeName:
type: string
description: The top part > Employee name > The name of this employee.
status:
enum:
- Active
- OnHold
- HoldPayments
- Inactive
- OneTime
type: string
description: 'Mandatory field: The top part > Status > The status of the employee. The following options are available: Active, On hold, Hold payments, Inactive, One-time.'
department:
type: string
description: 'Mandatory field: General information tab > Employee section > Department* > The department the employee works for.'
contact:
$ref: '#/components/schemas/contactInEmployeeDto'
address:
$ref: '#/components/schemas/addressInEmployeeDto'
lastModifiedDateTime:
type: string
format: date-time
employeeClass:
$ref: '#/components/schemas/employeeClassInEmployeeDto'
branch:
$ref: '#/components/schemas/BranchNumberDto'
calendarID:
type: string
employeeLogin:
type: string
workGroupDescription:
type: array
items:
type: string
timeStamp:
type: string
description: 'Identifier that represents a specific version of the resource.
It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers)'
format: byte
errorInfo:
type: string
metadata:
$ref: '#/components/schemas/MetadataDto'
description: This class represents an Employee in EmployeeController. Used for getting data.
DtoValueOfString:
type: object
properties:
value:
type: string
taxCategoryInTaskExtendedDto:
properties:
number:
type: string
description: Number of item
description:
type: string
description: Name of item/description
description: VAT category > The tax category for the project task.
TaskExtendedDto:
type: object
properties:
internalId:
type: integer
description: Internal ID* > The internal ID of the task.
format: int32
projectInternalId:
type: integer
description: Project Internal ID* > The internal ID of the project.
format: int32
defAccount:
$ref: '#/components/schemas/defAccountInTaskExtendedDto'
defSub:
$ref: '#/components/schemas/defSubInTaskExtendedDto'
defAccrualAccount:
$ref: '#/components/schemas/defAccrualAccountInTaskExtendedDto'
defAccrualSub:
$ref: '#/components/schemas/defAccrualSubInTaskExtendedDto'
taxCategory:
$ref: '#/components/schemas/taxCategoryInTaskExtendedDto'
lastModifiedDateTime:
type: string
description: Information collected from system.
format: date-time
createdDateTime:
type: string
description: Information collected from the system. Not visible on the screen.
format: date-time
taskId:
type: string
description: 'Mandatory field: > Task ID* > The ID of the task.'
description:
type: string
description: 'Mandatory field: Description > The description of the task.'
plannedStart:
type: string
format: date-time
plannedEnd:
type: string
format: date-time
startDate:
type: string
description: Start date > The date when the task was actually started.
format: date-time
endDate:
type: string
description: End date > The date when the task was actually finished.
format: date-time
branch:
$ref: '#/components/schemas/branchInTaskExtendedDto'
rateTable:
$ref: '#/components/schemas/rateTableInTaskExtendedDto'
status:
enum:
- Planned
- Active
- Cancelled
- Canceled
- Completed
type: string
description: 'Mandatory field: Status* > The status of the task, which can be one of the following: In planning, Active, Cancelled, Completed.'
restrictEmployees:
type: boolean
description: Summary tab > Task properties section > Restrict employees > A check box that indicates (if selected) that only the employees listed on the Employees tab of this window can create activities and documents associated with the current task.
visibility:
$ref: '#/components/schemas/visibilityInTaskExtendedDto'
timeStamp:
type: string
description: 'Identifier that represents a specific version of the resource.
It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers)'
format: b
# --- truncated at 32 KB (36 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/openapi/visma-projecttask-api-openapi.yml