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-cashtransaction-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 Cash Transaction API
version: v1
servers:
- url: https://api.finance.visma.net
tags:
- name: CashTransaction
paths:
/v1/cashTransaction/{referenceNbr}:
get:
tags:
- CashTransaction
summary: Get a specific Transaction - ScreenID=CA304000
description: 'Data for the Cash Transaction
The response headers include an ETag after a successful GET operation.'
operationId: CashTransaction_GetByreferenceNbr
parameters:
- name: referenceNbr
in: path
description: Returns data for the selected Cash transaction
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/CashTransactionDto'
text/json:
schema:
$ref: '#/components/schemas/CashTransactionDto'
'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:
- CashTransaction
summary: Update a specific CashTransaction - ScreenID=CA304000
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: CashTransaction_PutByreferenceNbr
parameters:
- name: referenceNbr
in: path
description: Identifies the Cash Transaction 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
- 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 Cash Transaction to update
content:
application/json:
schema:
$ref: '#/components/schemas/CashTransactionUpdateDto'
text/json:
schema:
$ref: '#/components/schemas/CashTransactionUpdateDto'
application/xml:
schema:
$ref: '#/components/schemas/CashTransactionUpdateDto'
text/xml:
schema:
$ref: '#/components/schemas/CashTransactionUpdateDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/CashTransactionUpdateDto'
required: true
x-bodyName: cashTransaction
responses:
'204':
description: NoContent
content:
application/json:
schema:
type: object
text/json:
schema:
type: object
'412':
description: Cash transaction document 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: []
/v1/cashTransaction:
get:
tags:
- CashTransaction
summary: Get all Transaction - ScreenID=CA304000
description: Data for the Cash Transaction
operationId: CashTransaction_GetAll
parameters:
- name: numberToRead
in: query
description: This field has been deprecated and will be removed in future versions.
schema:
type: integer
format: int32
- name: skipRecords
in: query
description: This field has been deprecated and will be removed in future versions.
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: 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/CashTransactionDto'
text/json:
schema:
type: array
items:
$ref: '#/components/schemas/CashTransactionDto'
'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:
- CashTransaction
summary: Create a Cash Transaction- ScreenID=CA304000
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: CashTransaction_CreateCashTransaction
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: Defines the data for the Cash Transaction to create
content:
application/json:
schema:
$ref: '#/components/schemas/CashTransactionUpdateDto'
text/json:
schema:
$ref: '#/components/schemas/CashTransactionUpdateDto'
application/xml:
schema:
$ref: '#/components/schemas/CashTransactionUpdateDto'
text/xml:
schema:
$ref: '#/components/schemas/CashTransactionUpdateDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/CashTransactionUpdateDto'
required: true
x-bodyName: cashTransaction
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/cashTransaction/{referenceNbr}/action/release:
post:
tags:
- CashTransaction
summary: Release cash transaction - ScreenID=CA304000
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
In this endpoint, If-Match can also be checked against resource current version when calling with ''erp-api-background'' HTTP header.'
operationId: CashTransaction_ReleaseByreferenceNbr
parameters:
- name: referenceNbr
in: path
description: Reference number of the cash transaction 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
- 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
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/ReleaseCashTransactionActionResultDto'
text/json:
schema:
$ref: '#/components/schemas/ReleaseCashTransactionActionResultDto'
application/xml:
schema:
$ref: '#/components/schemas/ReleaseCashTransactionActionResultDto'
text/xml:
schema:
$ref: '#/components/schemas/ReleaseCashTransactionActionResultDto'
'412':
description: Cash transaction document 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/cashTransaction/{referenceNbr}/action/reverse:
post:
tags:
- CashTransaction
summary: Reverse a Cash Transaction- ScreenID=CA304000
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
In this endpoint, If-Match can also be checked against resource current version when calling with ''erp-api-background'' HTTP header.'
operationId: CashTransaction_ReverseByreferenceNbr
parameters:
- name: referenceNbr
in: path
description: Reference number of the cash transaction to be reversed.
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 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: The action dto use to condition the action
content:
application/json:
schema:
$ref: '#/components/schemas/ReverseCashTransactionActionDto'
text/json:
schema:
$ref: '#/components/schemas/ReverseCashTransactionActionDto'
application/xml:
schema:
$ref: '#/components/schemas/ReverseCashTransactionActionDto'
text/xml:
schema:
$ref: '#/components/schemas/ReverseCashTransactionActionDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/ReverseCashTransactionActionDto'
required: true
x-bodyName: reverseActionDto
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/ReverseCashTransactionActionResultDto'
text/json:
schema:
$ref: '#/components/schemas/ReverseCashTransactionActionResultDto'
'412':
description: Cash transaction document 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: []
/v1/cashTransaction/{referenceNbr}/attachment:
post:
tags:
- CashTransaction
summary: Creates an attachment and associates it with a cash transaction document.
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.
In this endpoint, If-Match can be checked against resource current version when calling with ''erp-api-background'' HTTP header.'
operationId: CashTransaction_CreateAttachmentByreferenceNbr
parameters:
- name: referenceNbr
in: path
description: Identifies the cash transaction 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
- 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
responses:
'201':
description: Created
content:
application/json:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
text/json:
schema:
$ref: '#/components/schemas/BackgroundApiAcceptedDto'
'412':
description: Cash transaction document 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: []
components:
schemas:
branchInFinancialsDetailDto:
properties:
number:
type: string
description: Click the magnifier. > The identifier.
name:
type: string
description: Click the magnifier. > The name.
description: "Link to general ledger section > Branch > \tThe branch that initiated the transaction."
BackgroundApiAcceptedDto:
type: object
properties:
id:
type: string
stateLocation:
type: string
CashTransactionUpdateDto:
type: object
properties:
referenceNumber:
$ref: '#/components/schemas/DtoValueOfString'
hold:
$ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
tranDate:
$ref: '#/components/schemas/DtoValueOfNullableOfDateTime'
finanacialPeriod:
$ref: '#/components/schemas/finanacialPeriodInCashTransactionUpdateDto'
financialPeriod:
$ref: '#/components/schemas/financialPeriodInCashTransactionUpdateDto'
description:
$ref: '#/components/schemas/DtoValueOfString'
cashAccount:
$ref: '#/components/schemas/DtoValueOfString'
entryType:
$ref: '#/components/schemas/DtoValueOfString'
documentRef:
$ref: '#/components/schemas/DtoValueOfString'
controlTotal:
$ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
vatAmount:
$ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
vatZone:
$ref: '#/components/schemas/DtoValueOfString'
taxCalculationMode:
$ref: '#/components/schemas/DtoValueOfNullableOfTaxCalcMode'
overrideNumberSeries:
$ref: '#/components/schemas/DtoValueOfBoolean'
cashTransactionDetails:
type: array
items:
$ref: '#/components/schemas/CashTransactionDetailUpdateDto'
cashTransactionTaxDetails:
type: array
items:
$ref: '#/components/schemas/CashTransactionTaxDetailUpdateDto'
ownerInCashTransactionDto:
properties:
internalId:
type: string
number:
type: string
description: The identifier of the particular destination of the selected type.
name:
type: string
description: The name of the particular destination of the selected type.
description: The top part > Owner > The user who created the cash transaction.
TaxCategoryNumberDescriptionDto:
type: object
properties:
number:
type: string
description: Number of item
description:
type: string
description: Name of item/description
SegmentUpdateDto:
type: object
properties:
segmentId:
type: integer
format: int32
segmentValue:
type: string
DtoValueOfNullableOfDateTime:
type: object
properties:
value:
type: string
format: date-time
DtoValueOfNullableOfBoolean:
type: object
properties:
value:
type: boolean
TransactionDetailDto:
type: object
properties:
lineNumber:
type: integer
description: The line number in the table.
format: int32
branch:
$ref: '#/components/schemas/branchInTransactionDetailDto'
item:
$ref: '#/components/schemas/itemInTransactionDetailDto'
description:
type: string
description: Description > The description provided for the item.
quantity:
type: number
description: Quantity > The quantity of the item.
format: double
uom:
type: string
description: UoM > The unit of measure of the item.
price:
type: number
description: Price > The unit price for the item.
format: double
amount:
type: number
description: Amount > The total amount for all units or items.
format: double
offsetCashAccount:
$ref: '#/components/schemas/offsetCashAccountInTransactionDetailDto'
offsetAccount:
$ref: '#/components/schemas/offsetAccountInTransactionDetailDto'
offsetSubAccount:
$ref: '#/components/schemas/offsetSubAccountInTransactionDetailDto'
taxCategory:
$ref: '#/components/schemas/taxCategoryInTransactionDetailDto'
nonBillable:
type: boolean
description: Non-invoiceable > A check box that indicates (if selected) that this transaction is non-invoiceable in the project.
project:
$ref: '#/components/schemas/projectInTransactionDetailDto'
projectTask:
$ref: '#/components/schemas/projectTaskInTransactionDetailDto'
offsetCashAccountInTransactionDetailDto:
properties:
type:
type: string
number:
type: string
description: Number of item
description:
type: string
description: Name of item/description
description: Offset cash account > The cash account to be used for the transaction.
CashTransactionTaxDetailUpdateDto:
type: object
properties:
vatId:
$ref: '#/components/schemas/DtoValueOfString'
taxableAmount:
$ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
vatAmount:
$ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
expenseAmount:
$ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
financialsDetailInCashTransactionDto:
properties:
batchNumber:
type: string
description: Link to general ledger section > Batch number > The number of the batch generated to implement the cash transaction.
branch:
$ref: '#/components/schemas/branchInFinancialsDetailDto'
cleared:
type: boolean
description: Link to general ledger section > Cleared > A check
# --- truncated at 32 KB (49 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/openapi/visma-cashtransaction-api-openapi.yml