Every API here is available over the APIs.io API and to AI agents over MCP.
openapi: 3.2.0
info:
title: Visma.net ERP Customer Overdue Charge API
version: v1
servers:
- url: https://api.finance.visma.net
tags:
- name: CustomerOverdueCharge
paths:
/v1/customerOverdueCharge/{overdueChargeNumber}:
get:
tags:
- CustomerOverdueCharge
summary: Get a specific Customer Overdue Charge
description: 'Data for Customer Overdue Charge
The response headers include an ETag after a successful GET operation.'
operationId: CustomerOverdueCharge_GetByoverdueChargeNumber
parameters:
- name: overdueChargeNumber
in: path
description: Identifies the Customer Overdue Charge
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/CustomerOverdueChargeDto'
text/json:
schema:
$ref: '#/components/schemas/CustomerOverdueChargeDto'
'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:
- CustomerOverdueCharge
summary: Update a specific Overdue Charge
description: 'Response Message has StatusCode NoContent if PUT operation succeed
Response Message has StatusCode BadRequest if PUT operation failed
In this endpoint, If-Match can be checked against resource current version when calling with ''erp-api-background'' HTTP header.'
operationId: CustomerOverdueCharge_UpdateByoverdueChargeNumber
parameters:
- name: overdueChargeNumber
in: path
description: Identifies the Overdue Charge 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 Overdue Charge to update
content:
application/json:
schema:
$ref: '#/components/schemas/CustomerOverdueChargeUpdateDto'
text/json:
schema:
$ref: '#/components/schemas/CustomerOverdueChargeUpdateDto'
application/xml:
schema:
$ref: '#/components/schemas/CustomerOverdueChargeUpdateDto'
text/xml:
schema:
$ref: '#/components/schemas/CustomerOverdueChargeUpdateDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/CustomerOverdueChargeUpdateDto'
required: true
x-bodyName: overdueCharge
responses:
'204':
description: NoContent
content:
application/json:
schema:
type: object
text/json:
schema:
type: object
'412':
description: Customer overdue charge 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/customerOverdueCharge:
get:
tags:
- CustomerOverdueCharge
summary: Get a range of Customer Overdue Charges - ScreenId=AR301000 Request page size…
description: Data for Customer Overdue Charge
operationId: CustomerOverdueCharge_GetAll
parameters:
- name: documentType
in: query
description: The field is deprecated for specific customer document endpoints. It will only be usable from customer document endpoint.
schema:
enum:
- Invoice
- DebitNote
- CreditNote
- Payment
- VoidPayment
- Prepayment
- Refund
- FinCharge
- SmallBalanceWo
- SmallCreditWo
- CashSale
- CashReturn
- Undefined
- NoUpdate
type: string
- name: released
in: query
description: Parameter for showing if invoice has been released or not.
schema:
type: integer
format: int32
- name: dunningLevel
in: query
description: The dunning level of the document.
schema:
type: integer
format: int32
- name: closedFinancialPeriod
in: query
description: The date of the closing of the financial period.
schema:
type: string
- name: dunningLetterDateTime
in: query
description: The date and time for when the document last released a dunning letter.
schema:
type: string
- name: dunningLetterDateTimeCondition
in: query
description: Set time/date as before (<), after (>), before and including (=<) OR after and including (=>) to filter on time frame.
schema:
type: string
- name: project
in: query
description: The project with which the document is associated.
schema:
type: string
- name: expandApplications
in: query
description: True if you want to see all dunning information regarding this document.
schema:
type: boolean
- name: expandDunningInformation
in: query
schema:
type: boolean
- name: expandAttachments
in: query
description: True if you want to see all attachments regarding this document.
schema:
type: boolean
- name: expandTaxDetails
in: query
description: True if you want to see all VAT details regarding this document.
schema:
type: boolean
- name: expandInvoiceAddress
in: query
description: True if you want to see all information regarding the invoice address for this document.
schema:
type: boolean
- name: financialPeriod
in: query
description: The financial period to which the transactions recorded in the document is posted. Format YYYYMM.
schema:
type: string
- name: documentDueDate
in: query
description: The date when payment for the document is due, in accordance with the credit terms.
schema:
type: string
format: date-time
- name: documentDueDateCondition
in: query
description: 'This value represents the condition to be applied to the Due Date 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'
schema:
type: string
- name: status
in: query
description: The status of the document. Use the dropdown to select status.
schema:
enum:
- Hold
- Balanced
- Voided
- Scheduled
- Open
- Closed
- PendingPrint
- PendingEmail
- CreditHold
- CcHold
- Reserved
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: externalReference
in: query
description: The top part > External reference > The external reference used in AutoInvoice.
schema:
type: string
- name: paymentReference
in: query
description: The top part > Payment ref. > The reference number of the document, as automatically generated by the system in accordance with the number series assigned to cash sales in the Customer ledger preferences window..
schema:
type: string
- name: customerRefNumber
in: query
description: The top part > External reference > The external reference used in AutoInvoice.
schema:
type: string
- name: customer
in: query
description: Filter by Customer
schema:
type: string
- name: branch
in: query
description: Filter by Branch
schema:
type: string
- name: documentDate
in: query
description: 'This value indicates the document date. Use it to retrieve all records that have the Document Date since that time, up to the future.
Accepted format:
* ```yyyy-MM-dd```
* ```yyyy-MM-dd```
* ```yyyy-MM-dd```
* ```yyyy-MM-dd```
* ```yyyy-MM-dd```
_Note:_ __DocumentDate__ and __DocumentDateCondition__ are __mutually inclusive__.'
schema:
type: string
format: date-time
- name: documentDateCondition
in: query
description: 'This value represents the condition to be applied to the Document Date 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:_ __DocumentDate__ and __DocumentDateCondition__ are __mutually inclusive__.'
schema:
type: string
- 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: 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/CustomerOverdueChargeDto'
text/json:
schema:
type: array
items:
$ref: '#/components/schemas/CustomerOverdueChargeDto'
'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/customerOverdueCharge/{overdueChargeNumber}/action/release:
post:
tags:
- CustomerOverdueCharge
summary: Release overdue charge operation
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: CustomerOverdueCharge_ReleaseDocumentByoverdueChargeNumber
parameters:
- name: overdueChargeNumber
in: path
description: Reference number of the overdue charge 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:
'412':
description: Customer overdue charge version does not match with If-Match header
content:
application/json: {}
text/json: {}
'200':
description: If invoked without header erp-api-background set, operation starts in the background and 200-OK is returned with a reference. No notification is sent when action is done.
content:
application/json:
schema:
$ref: '#/components/schemas/ReleaseCustomerOverdueChargeActionResultDto'
text/json:
schema:
$ref: '#/components/schemas/ReleaseCustomerOverdueChargeActionResultDto'
'202':
description: If invoked with header erp-api-background set, operation starts in the background, 202-Accepted will be returned and a webhook will be posted upon action done event.
content:
application/json: {}
text/json: {}
security:
- interactiveapi: []
/v1/customerOverdueCharge/{overdueChargeNumber}/attachment:
post:
tags:
- CustomerOverdueCharge
summary: Creates an attachment and associates it with an overdue charge.
description: 'Response Message has StatusCode Created if POST operation succeed
Response Message has StatusCode BadRequest 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: CustomerOverdueCharge_CreateHeaderAttachmentByoverdueChargeNumber
parameters:
- name: overdueChargeNumber
in: path
description: Identifies the overdue charge
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:
type: object
text/json:
schema:
type: object
'412':
description: Customer overdue charge 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/customerOverdueCharge/{overdueChargeNumber}/{lineNumber}/attachment:
post:
tags:
- CustomerOverdueCharge
summary: Creates an attachment and associates it with a certain overdue charge line.
description: 'Response Message has StatusCode Created if POST operation succeed
Response Message has StatusCode BadRequest 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: CustomerOverdueCharge_CreateLineAttachmentByoverdueChargeNumberlineNumber
parameters:
- name: overdueChargeNumber
in: path
description: Identifies the overdue charge
required: true
schema:
type: string
- name: lineNumber
in: path
description: Specifies line number
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
responses:
'201':
description: Created
content:
application/json:
schema:
type: object
text/json:
schema:
type: object
'412':
description: Customer overdue charge 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:
creditTermsInCustomerOverdueChargeDto:
properties:
id:
type: string
description: Click on the magnifier. > The identifier.
description:
type: string
description: Click on the magnifier. > The description.
description: 'Mandatory field: The top part > Terms* > The credit terms used in relations with the customer.'
paymentMethodInCustomerOverdueChargeDto:
properties:
id:
type: string
description: Click on the magnifier. > The identifier.
description:
type: string
description: Click on the magnifier. > The description.
description: The Financial details tab > The Payment information section > Payment method > The identifier for the payment method that the customer will use to pay the document.
salesPersonIDInCustomerOverdueChargeUpdateDto:
properties:
value:
type: integer
format: int32
description: The field is deprecated for customer document endpoints, please use Salesperson instead
BackgroundApiAcceptedDto:
type: object
properties:
id:
type: string
stateLocation:
type: string
financialPeriodInCustomerOverdueChargeUpdateDto:
properties:
value:
type: string
description: The financial period to which the transactions recorded in the document should be posted. Use the format YYYYMM.
TaxDetailDto:
type: object
properties:
taxId:
type: string
description: 'Mandatory field: VAT ID* > The ID of the VAT applied to the document.'
recordId:
type: integer
description: The id as stored in the database. It can be used when we want to update a VAT record.
format: int32
vatId:
$ref: '#/components/schemas/vatIdInTaxDetailDto'
vatRate:
type: number
description: VAT rate > The rate of the VAT.
format: double
taxableAmount:
type: number
description: Taxable amount > The taxable amount for the VAT, which is calculated at the document level.
format: double
vatAmount:
type: number
description: VAT > The VAT amount for the specific VAT, which is calculated at the document level.
format: double
expenseAmount:
type: number
description: Expense Amount for the VAT type that has been added.
format: double
description: This class represents a VAT Detail Line. Used for getting data.
DtoValueOfDecimal:
type: object
properties:
value:
type: number
format: double
SegmentUpdateDto:
type: object
proper
# --- truncated at 32 KB (70 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/openapi/visma-customeroverduecharge-api-openapi.yml