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-inventoryadjustment-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 Inventory Adjustment API
version: v1
servers:
- url: https://api.finance.visma.net
tags:
- name: InventoryAdjustment
paths:
/v1/inventoryadjustment/{inventoryAdjustmentNumber}:
get:
tags:
- InventoryAdjustment
summary: Get a specific Inventory Adjustment document
operationId: InventoryAdjustment_GetByinventoryAdjustmentNumber
parameters:
- name: inventoryAdjustmentNumber
in: path
description: Identifies the Inventory Adjustment document
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/InventoryAdjustmentDto'
text/json:
schema:
$ref: '#/components/schemas/InventoryAdjustmentDto'
'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:
- InventoryAdjustment
summary: Update a specific inventory item
description: Response Message has StatusCode NoContent if PUT operation succeed
operationId: InventoryAdjustment_PutByinventoryAdjustmentNumber
parameters:
- name: inventoryAdjustmentNumber
in: path
description: Identifies the inventory item to update
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
requestBody:
description: The data to update for inventory item
content:
application/json:
schema:
$ref: '#/components/schemas/InventoryAdjustmentUpdateDto'
text/json:
schema:
$ref: '#/components/schemas/InventoryAdjustmentUpdateDto'
application/xml:
schema:
$ref: '#/components/schemas/InventoryAdjustmentUpdateDto'
text/xml:
schema:
$ref: '#/components/schemas/InventoryAdjustmentUpdateDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/InventoryAdjustmentUpdateDto'
required: true
x-bodyName: adjustment
responses:
'204':
description: NoContent
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/inventoryadjustment:
get:
tags:
- InventoryAdjustment
summary: Get a range of Inventory Adjustment Dto - ScreenId=IN303000 Request page size…
operationId: InventoryAdjustment_GetAll
parameters:
- name: status
in: query
schema:
enum:
- Hold
- Balanced
- Released
type: string
- name: date
in: query
description: "The date when the inventory document was created\n \nAccepted format:\n* ```yyyy-MM-dd```\n* ```yyyy-MM-dd HH:mm:ss```\n* ```yyyy-MM-dd HH:mm:ss.FFF```\n* ```yyyy-MM-ddTHH:mm:ss```\n* ```yyyy-MM-ddTHH:mm:ss.FFF```\n\n_Note:_ __Date__ and __DateCondition__ are __mutually inclusive__."
schema:
type: string
- name: dateCondition
in: query
description: 'This value represents the condition to be applied when retrieving records usind the __Date__ filter.
Accepted values (without the single quotes):
* ''>'' for greater than
* ''<'' for less than
* ''>='' for greater than or equal
* ''<='' for less than or equal
_Note:_ __Date__ and __DateCondition__ are __mutually inclusive__.'
schema:
type: string
- name: greaterThanValue
in: query
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: orderBy
in: query
description: This field has been deprecated and will be removed in future versions. The OrderBy parameter has no effect on the result.
schema:
type: string
- 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: 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/InventoryAdjustmentDto'
text/json:
schema:
type: array
items:
$ref: '#/components/schemas/InventoryAdjustmentDto'
'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:
- InventoryAdjustment
summary: Create an inventory item
description: Response Message has StatusCode Created if POST operation succed
operationId: InventoryAdjustment_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 inventory adjustment to create
content:
application/json:
schema:
$ref: '#/components/schemas/InventoryAdjustmentUpdateDto'
text/json:
schema:
$ref: '#/components/schemas/InventoryAdjustmentUpdateDto'
application/xml:
schema:
$ref: '#/components/schemas/InventoryAdjustmentUpdateDto'
text/xml:
schema:
$ref: '#/components/schemas/InventoryAdjustmentUpdateDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/InventoryAdjustmentUpdateDto'
required: true
x-bodyName: inventoryAdjustment
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/inventoryadjustment/{adjRefNumber}/action/release:
post:
tags:
- InventoryAdjustment
summary: Release inventory document action
description: The action result dto contains information about the result of running the action
operationId: InventoryAdjustment_ReleaseDocumentByadjRefNumber
parameters:
- name: adjRefNumber
in: path
description: Reference number of the released adjustment to be released
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/ReleaseInventoryDocumentActionResultDto'
text/json:
schema:
$ref: '#/components/schemas/ReleaseInventoryDocumentActionResultDto'
application/xml:
schema:
$ref: '#/components/schemas/ReleaseInventoryDocumentActionResultDto'
text/xml:
schema:
$ref: '#/components/schemas/ReleaseInventoryDocumentActionResultDto'
'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: []
components:
schemas:
dateInInventoryAdjustmentUpdateDto:
properties:
value:
type: string
format: date-time
description: The date when the receipt was created. All transactions included in this document will have this transaction date.
BackgroundApiAcceptedDto:
type: object
properties:
id:
type: string
stateLocation:
type: string
branchNumberInInventoryAdjustmentDto:
properties:
number:
type: string
description: Click the magnifier. > The identifier.
name:
type: string
description: Click the magnifier. > The name.
description: The Branch associated
externalReferenceInInventoryAdjustmentUpdateDto:
properties:
value:
type: string
description: The external reference number of the inventory issue document (for example, the vendor’s reference code).
AttachmentDto:
type: object
properties:
name:
type: string
description: The name of the attachment.
id:
type: string
description: The ID of the attachment
format: uuid
example: 00000000-0000-0000-0000-000000000000
revision:
type: integer
description: The version of the attachment.
format: int32
postPeriodInInventoryAdjustmentUpdateDto:
properties:
value:
type: string
description: The financial period to which the transactions recorded in the document should be posted. Use the format MMYYYY.
InventoryAdjustmentDto:
type: object
properties:
totalCost:
type: number
description: The top part > Total cost > The total cost of the inventory items received. The system automatically calculates this value as a sum of all extended cost values of all received inventory items listed in the Transaction Details tab of this form.
format: double
controlCost:
type: number
description: The top part > Control cost > The manually entered cost of stock items listed in the adjustment. Control cost is available only if the Validate document totals on Entry option is selected on the Inventory preferences window. The user enters this value manually to confirm the total cost as calculated automatically for the document. If the Control Cost and Total Cost values do not match, the system generates a warning message and the document cannot be saved.
format: double
adjusmentLines:
type: array
items:
$ref: '#/components/schemas/InventoryAdjustmentLineDto'
description: Transaction details tab > The inventory adjusment lines
referenceNumber:
type: string
description: The unique reference number of the receipt, which the system automatically assigns according to the numbering sequence selected for receipts on the Inventory Preferences IN.10.10.00) form.
status:
enum:
- Hold
- Balanced
- Released
type: string
description: " The current status of the receipt. The following options are available: \nOn Hold:The receipt/issue is a draft and can be edited. Receipts with this status cannot be released.\nBalanced: The receipt/issue data has been validated by the system and the receipt can be released. It also can be modified or deleted, but changes can be saved only if the receipt is balanced.\nReleased: The receipt/issue has been released and cannot be edited or deleted."
hold:
type: boolean
description: A check box that you select to give the receipt the On Hold status. Clear the check box to save the receipt with the Balanced status.
date:
type: string
description: The date when the inventory document was created. All transactions included in this document will have this transaction date.
format: date-time
postPeriod:
type: string
description: The financial period to which the transactions recorded in the document should be posted. Format MMYYYY.
externalReference:
type: string
description: The external reference number of the inventory issue document (for example, the vendor’s reference code).
description:
type: string
description: A brief description of the inventory issue or its transactions.
totalQuantity:
type: number
description: The total quantity of inventory items, which the system calculates automatically, for the document.
format: double
controlQuantity:
type: number
description: The manually entered quantity of inventory items. Control Qty. is available only if the Validate Document Totals on Entry option is selected on the Inventory Preferences form. If the Control Qty. and Total Qty.values do not match, the system generates a warning message and the issue cannot be saved.
format: double
batchNumber:
type: string
description: The reference number of the batch generated for the receipt. Click the number to open the Journal Transactions (GL.30.10.00) form and view the details of the transactions.
lastModifiedDateTime:
type: string
description: The date when the document was last modified.
format: date-time
branchNumber:
$ref: '#/components/schemas/branchNumberInInventoryAdjustmentDto'
attachments:
type: array
items:
$ref: '#/components/schemas/AttachmentDto'
description: The data containing information about the document attachments
timestamp:
type: string
description: Timestamp of the inventory document
errorInfo:
type: string
metadata:
$ref: '#/components/schemas/MetadataDto'
description: This class represents a inventory issue in InventoryIssueController. Used by getting data.
holdInInventoryAdjustmentUpdateDto:
properties:
value:
type: boolean
description: A check box that you select to give the receipt the On Hold status. Clear the check box to save the receipt with the Balanced status.
branchNumberInInventoryAdjustmentUpdateDto:
properties:
value:
type: string
description: The Branch associated
controlCostInInventoryAdjustmentUpdateDto:
properties:
value:
type: number
format: double
description: The manually entered summary cost for all specified inventory adjustment items.
locationInInventoryAdjustmentLineDto:
properties:
countryId:
type: string
description: Location*.
id:
type: string
description: Click the magnifier > The identifier
name:
type: string
description: Click the magnifier > The displayed name
description: Location > The warehouse location from which the goods are transferred.
InventoryAdjustmentLineUpdateDto:
type: object
properties:
warehouseId:
$ref: '#/components/schemas/DtoValueOfString'
unitCost:
$ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
extCost:
$ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
receiptNumber:
$ref: '#/components/schemas/DtoValueOfString'
operation:
enum:
- Insert
- Update
- Delete
type: string
lineNumber:
$ref: '#/components/schemas/DtoValueOfInt32'
inventoryNumber:
$ref: '#/components/schemas/DtoValueOfString'
locationId:
$ref: '#/components/schemas/DtoValueOfString'
quantity:
$ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
uom:
$ref: '#/components/schemas/DtoValueOfString'
reasonCode:
$ref: '#/components/schemas/DtoValueOfString'
projectId:
$ref: '#/components/schemas/DtoValueOfString'
projectTaskId:
$ref: '#/components/schemas/DtoValueOfString'
description:
$ref: '#/components/schemas/DtoValueOfString'
branchNumber:
$ref: '#/components/schemas/DtoValueOfString'
DtoValueOfInt32:
type: object
properties:
value:
type: integer
format: int32
BranchNumberDto:
type: object
properties:
number:
type: string
description: Click the magnifier. > The identifier.
name:
type: string
description: Click the magnifier. > The name.
reasonCodeInInventoryAdjustmentLineDto:
properties:
id:
type: string
description: Click on the magnifier. > The identifier.
description:
type: string
description: Click on the magnifier. > The description.
description: Reason code > The reason code associated with the transferred goods.
MetadataDto:
type: object
properties:
totalCount:
type: integer
format: int64
maxPageSize:
type: integer
format: int64
DtoValueOfString:
type: object
properties:
value:
type: string
warehouseInInventoryAdjustmentLineDto:
properties:
id:
type: string
description: Click on the magnifier. > The identifier.
description:
type: string
description: Click on the magnifier. > The description.
description: 'Mandatory field: Warehouse* > The warehouse where the item is stocked.'
DtoValueOfNullableOfDecimal:
type: object
properties:
value:
type: number
format: double
ReleaseInventoryDocumentActionResultDto:
type: object
properties:
actionId:
type: string
format: uuid
actionResult:
enum:
- Queued
- InProcess
- Failed
- Done
type: string
errorInfo:
type: string
InventoryAdjustmentUpdateDto:
type: object
properties:
controlCost:
$ref: '#/components/schemas/controlCostInInventoryAdjustmentUpdateDto'
adjustmentLines:
type: array
items:
$ref: '#/components/schemas/InventoryAdjustmentLineUpdateDto'
description: The inventory adjustment lines
referenceNumber:
$ref: '#/components/schemas/referenceNumberInInventoryAdjustmentUpdateDto'
hold:
$ref: '#/components/schemas/holdInInventoryAdjustmentUpdateDto'
date:
$ref: '#/components/schemas/dateInInventoryAdjustmentUpdateDto'
postPeriod:
$ref: '#/components/schemas/postPeriodInInventoryAdjustmentUpdateDto'
externalReference:
$ref: '#/components/schemas/externalReferenceInInventoryAdjustmentUpdateDto'
description:
$ref: '#/components/schemas/descriptionInInventoryAdjustmentUpdateDto'
controlQuantity:
$ref: '#/components/schemas/controlQuantityInInventoryAdjustmentUpdateDto'
branchNumber:
$ref: '#/components/schemas/branchNumberInInventoryAdjustmentUpdateDto'
description: This class represents a inventory issue in InventoryIssueController. Used by getting data.
InventoryAdjustmentLineDto:
type: object
properties:
warehouse:
$ref: '#/components/schemas/warehouseInInventoryAdjustmentLineDto'
unitCost:
type: number
description: Unit cost > The cost of the unit used as base unit for the stock item.
format: double
extCost:
type: number
description: Cost > The cost of the item.
format: double
receiptNumber:
type: string
description: Receipt no. > Reference number for the receipt for the stock item.
poReceiptNumber:
type: string
description: Purchase order receipt number
lineNumber:
type: integer
format: int32
inventoryItem:
$ref: '#/components/schemas/inventoryItemInInventoryAdjustmentLineDto'
location:
$ref: '#/components/schemas/locationInInventoryAdjustmentLineDto'
quantity:
type: number
description: Quantity > The quantity of the transferred goods (in the units indicated below).
format: double
uom:
type: string
description: 'Mandatory field: UoM* > The unit of measure (UoM) used for the goods to be transferred.'
reasonCode:
$ref: '#/components/schemas/reasonCodeInInventoryAdjustmentLineDto'
description:
type: string
description: Description > A brief description of the goods transfer transaction.
attachments:
type: array
items:
$ref: '#/components/schemas/AttachmentDto'
branchNumber:
$ref: '#/components/schemas/BranchNumberDto'
controlQuantityInInventoryAdjustmentUpdateDto:
properties:
value:
type: number
format: double
description: The manually entered quantity of inventory items. Control Qty. is available only if the Validate Document Totals on Entry option is selected on the Inventory Preferences form. If the Control Qty. and Total Qty.values do not match, the system generates a warning message and the issue cannot be saved.
referenceNumberInInventoryAdjustmentUpdateDto:
properties:
value:
type: string
description: The unique reference number of the receipt, which the system automatically assigns according to the numbering sequence selected for receipts on the Inventory Preferences IN.10.10.00) form.
descriptionInInventoryAdjustmentUpdateDto:
properties:
value:
type: string
description: A brief description of the inventory issue or its transactions.
inventoryItemInInventoryAdjustmentLineDto:
properties:
number:
type: string
description: Number of item
description:
type: string
description: Name of item/description
description: 'Mandatory field: Item ID* > The ID of the goods to be transferred.'
securitySchemes:
interactiveapi:
type: oauth2
flows:
authorizationCode:
authorizationUrl: https://connect.visma.com/connect/authorize
tokenUrl: https://connect.visma.com/connect/token
scopes:
vismanet_erp_interactive_api:read: vismanet_erp_interactive_api:read
vismanet_erp_interactive_api:update: vismanet_erp_interactive_api:update
vismanet_erp_interactive_api:create: vismanet_erp_interactive_api:create
# --- truncated at 32 KB (32 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/openapi/visma-inventoryadjustment-api-openapi.yml