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-project-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 API
version: v1
servers:
- url: https://api.finance.visma.net
tags:
- name: Project
paths:
/v1/project/{projectID}:
get:
tags:
- Project
summary: Get a specific Project
description: 'Data for a single project
The response headers include an ETag after a successful GET operation.'
operationId: Project_GetByprojectID
parameters:
- name: projectID
in: path
description: Identifies the Project
required: true
schema:
type: string
- 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/ProjectDto'
text/json:
schema:
$ref: '#/components/schemas/ProjectDto'
'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/project/internal/{internalID}:
get:
tags:
- Project
summary: Get a specific Project by internal ID
description: 'Data for a single project
The response headers include an ETag after a successful GET operation.'
operationId: Project_GetByinternalID
parameters:
- name: internalID
in: path
description: Identifies the Project
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/ProjectDto'
text/json:
schema:
$ref: '#/components/schemas/ProjectDto'
'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/project:
get:
tags:
- Project
summary: Get a range of Projects - ScreenId=PM301000 The requested page size must be…
operationId: Project_GetAll
parameters:
- name: status
in: query
description: Use drop down and select Status.
schema:
enum:
- Planned
- Active
- Completed
- Cancelled
- OnHold
- PendingApproval
type: string
- name: systemTemplate
in: query
description: If the project is a template
schema:
type: boolean
- name: visibleInAP
in: query
description: If the project is visible in AP
schema:
type: boolean
- name: startDate
in: query
description: Project’s start date
schema:
type: string
format: date-time
- name: expandAttribute
in: query
description: Expands project atributes
schema:
type: boolean
- name: attributes
in: query
description: Identifies the attributes
schema:
type: string
- name: taskStatus
in: query
description: Use drop down and select Status.
schema:
enum:
- Planned
- Active
- Cancelled
- Canceled
- Completed
type: string
- name: taskVisibleInAp
in: query
description: If the project task is visible in the Supplier ledger
schema:
type: boolean
- name: taskVisibleInAr
in: query
description: If the project task is visible in the Customer ledger
schema:
type: boolean
- name: taskVisibleInCa
in: query
description: If the project task is visible in the Cash management workspace
schema:
type: boolean
- name: taskVisibleInCr
in: query
description: If the project task is visible in the CRM workspace
schema:
type: boolean
- name: taskVisibleInEa
in: query
description: If the project task is visible in the Expense workspace
schema:
type: boolean
- name: taskVisibleInGl
in: query
description: If the project task is visible in the General ledger workspace
schema:
type: boolean
- name: taskVisibleInIn
in: query
description: If the project task is visible in the Inventory workspace
schema:
type: boolean
- name: taskVisibleInPo
in: query
description: If the project task is visible in the Purchases workspace
schema:
type: boolean
- name: taskVisibleInSo
in: query
description: If the project task is visible in the Sales workspace
schema:
type: boolean
- name: taskVisibleInTa
in: query
description: If the project task is visible in the Time entities workspace
schema:
type: boolean
- name: nonProject
in: query
description: Set to true to return the non-project.
schema:
type: boolean
- name: publicId
in: query
description: Identifies the Project by its publicId
schema:
type: string
format: uuid
- 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: 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: branch
in: query
description: The branch name.
schema:
type: string
- name: onHold
in: query
description: If the project is on hold
schema:
type: boolean
- 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/ProjectDto'
text/json:
schema:
type: array
items:
$ref: '#/components/schemas/ProjectDto'
'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:
- Project
summary: Create an project
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: Project_Post
parameters:
- 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: Define the data for the project to create
content:
application/json:
schema:
$ref: '#/components/schemas/ProjectUpdateDto'
text/json:
schema:
$ref: '#/components/schemas/ProjectUpdateDto'
application/xml:
schema:
$ref: '#/components/schemas/ProjectUpdateDto'
text/xml:
schema:
$ref: '#/components/schemas/ProjectUpdateDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/ProjectUpdateDto'
required: true
x-bodyName: projectUpdateDto
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/project/tasks:
get:
tags:
- Project
summary: Get all tasks for a project
operationId: Project_GetTasks
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: []
/v1/project/action/changeProjectId/{internalId}:
post:
tags:
- Project
summary: Updates the ProjectID for the specified project
description: 'The action result dto contains information about the result of running the action.
Response Message has StatusCode BadRequest or InternalServerError if POST operation failed.'
operationId: Project_ChangeProjectIDActionByinternalId
parameters:
- name: internalId
in: path
description: Internal identifier of the project for which the project ID will be changed
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 POST operation is successful, the server responds with 200 OK 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 new project ID for the poject
content:
application/json:
schema:
$ref: '#/components/schemas/ChangeProjectIdActionDto'
text/json:
schema:
$ref: '#/components/schemas/ChangeProjectIdActionDto'
application/xml:
schema:
$ref: '#/components/schemas/ChangeProjectIdActionDto'
text/xml:
schema:
$ref: '#/components/schemas/ChangeProjectIdActionDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/ChangeProjectIdActionDto'
required: true
x-bodyName: changeProjectIdActionDto
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/ChangeProjectIdActionResultDto'
text/json:
schema:
$ref: '#/components/schemas/ChangeProjectIdActionResultDto'
application/xml:
schema:
$ref: '#/components/schemas/ChangeProjectIdActionResultDto'
text/xml:
schema:
$ref: '#/components/schemas/ChangeProjectIdActionResultDto'
'412':
description: Project version does not match with If-Match header
content:
application/json: {}
text/json: {}
application/xml: {}
text/xml: {}
'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'
application/xml:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
text/xml:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
security:
- interactiveapi: []
/v1/project/{projectId}:
put:
tags:
- Project
summary: Update a specific Project
description: 'Response Message has StatusCode NoContent 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: Project_PutByprojectId
parameters:
- name: projectId
in: path
description: Identifies the Project
required: true
schema:
type: string
- 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 clien
# --- truncated at 32 KB (78 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/openapi/visma-project-api-openapi.yml