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-discount-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 Discount API
version: v1
servers:
- url: https://api.finance.visma.net
tags:
- name: Discount
paths:
/v1/discount:
get:
tags:
- Discount
summary: Get a range of discounts - ScreenId=AR209500
operationId: Discount_GetDiscounts
parameters:
- name: lastModifiedDateTime
in: query
schema:
type: string
- name: lastModifiedDateTimeCondition
in: query
description: System retrieved information for state/condition.
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: discountCode
in: query
schema:
type: string
- name: series
in: query
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:
$ref: '#/components/schemas/BasePaginationDtoOfDiscountDto'
text/json:
schema:
$ref: '#/components/schemas/BasePaginationDtoOfDiscountDto'
'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:
- Discount
summary: Creates a new discount
description: The response headers include an ETag after a successful POST operation.
operationId: Discount_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: ''
content:
application/json:
schema:
$ref: '#/components/schemas/DiscountUpdateDto'
text/json:
schema:
$ref: '#/components/schemas/DiscountUpdateDto'
application/xml:
schema:
$ref: '#/components/schemas/DiscountUpdateDto'
text/xml:
schema:
$ref: '#/components/schemas/DiscountUpdateDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/DiscountUpdateDto'
required: true
x-bodyName: discountUpdateDto
responses:
'200':
description: OK
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/discount/{discountCode}/{series}:
put:
tags:
- Discount
summary: Update a discount
description: In this endpoint, If-Match can be checked against resource current version when calling with 'erp-api-background' HTTP header.
operationId: Discount_PutBydiscountCodeseries
parameters:
- name: discountCode
in: path
description: ''
required: true
schema:
type: string
- name: series
in: path
description: ''
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: ''
content:
application/json:
schema:
$ref: '#/components/schemas/DiscountUpdateDto'
text/json:
schema:
$ref: '#/components/schemas/DiscountUpdateDto'
application/xml:
schema:
$ref: '#/components/schemas/DiscountUpdateDto'
text/xml:
schema:
$ref: '#/components/schemas/DiscountUpdateDto'
application/x-www-form-urlencoded:
schema:
$ref: '#/components/schemas/DiscountUpdateDto'
required: true
x-bodyName: discountUpdateDto
responses:
'412':
description: Discount sequence 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: []
delete:
tags:
- Discount
operationId: Discount_DeleteBydiscountCodeseries
parameters:
- name: discountCode
in: path
required: true
schema:
type: string
- name: series
in: path
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:
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: []
summary: Discount delete bydiscount codeseries
x-summary-source: derived
/v1/discount/{discountCode}/{series}/{filerDate}/action/updateDiscounts:
post:
tags:
- Discount
summary: Update discounts using a filter date
description: In this endpoint, If-Match can be checked against resource current version when calling with 'erp-api-background' HTTP header.
operationId: Discount_UpdateDiscountsBydiscountCodeseriesfilerDate
parameters:
- name: discountCode
in: path
description: ''
required: true
schema:
type: string
- name: series
in: path
description: ''
required: true
schema:
type: string
- name: filterDate
in: query
description: ''
required: true
schema:
type: string
format: date-time
- name: filerDate
in: path
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: Discount sequence 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/discount/{discountCode}/{series}/action/updateDiscounts:
post:
tags:
- Discount
summary: Update discounts
description: In this endpoint, If-Match can be checked against resource current version when calling with 'erp-api-background' HTTP header.
operationId: Discount_UpdateDiscountsBydiscountCodeseries
parameters:
- name: discountCode
in: path
description: ''
required: true
schema:
type: string
- name: series
in: path
description: ''
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: Discount sequence 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: []
components:
schemas:
DiscountCustomerPriceClassDto:
type: object
properties:
priceClassId:
type: string
BackgroundApiAcceptedDto:
type: object
properties:
id:
type: string
stateLocation:
type: string
DtoValueOfNullableOfDateTime:
type: object
properties:
value:
type: string
format: date-time
DtoValueOfNullableOfBoolean:
type: object
properties:
value:
type: boolean
DiscountCustomer2Dto:
type: object
properties:
customer:
type: string
BasePaginationDtoOfDiscountDto:
type: object
properties:
pageNumber:
type: integer
format: int32
pageSize:
type: integer
format: int32
totalCount:
type: integer
format: int64
records:
type: array
items:
$ref: '#/components/schemas/DiscountDto'
DiscountBreakpointDto:
type: object
properties:
lineNbr:
type: integer
format: int32
active:
type: boolean
description: The top part > Active > A check box that indicates (if selected) that the series is active.
breakAmount:
type: number
description: Discount breakpoints tab > Break amount > The line amount (break point) that starts the new range for the currently effective series.
format: double
amountTo:
type: number
format: double
lastBreakAmount:
type: number
description: Discount breakpoints tab > Last break amount > The amount (break point) that started the new range for the previously effective series (the one that was used before the effective date).
format: double
lastAmountTo:
type: number
format: double
pendingBreakAmount:
type: number
description: Discount breakpoints tab > Pending break amount > The amount (break point) that starts the new range for the pending series (one that is not yet in effect).
format: double
breakQuantity:
type: number
description: Discount breakpoints tab > Break quantity > The quantity of items (break quantity) that starts the new range for a discount level for the currently effective series. Any break quantity should be specified in the base units.
format: double
quantityTo:
type: number
format: double
lastBreakQuantity:
type: number
description: Discount breakpoints tab > Last break quantity > The quantity of item (break point) that started the range for the discount series used before the effective date.
format: double
lastQuantityTo:
type: number
format: double
pendingBreakQuantity:
type: number
description: Discount breakpoints tab > Pending break quantity > The quantity of items (break point) that starts the new range for the pending (not yet effective) series.
format: double
discountAmount:
type: number
description: Discount breakpoints tab > Discount amount > The discount amount to be used for the quantities that exceed this break quantity if the Amount option is selected as Discount by.
format: double
discountPercent:
type: number
description: Discount breakpoints tab > Discount percent > The discount percent to be currently used for the quantities that exceed this break quantity if the Percent option is selected as Discount by.
format: double
lastDiscountAmount:
type: number
description: Discount breakpoints tab > Last discount amount > The amount used as the discount for the discount series that was in effect before the effective date.
format: double
lastDiscountPercent:
type: number
description: Discount breakpoints tab > Last discount percent > The percentage used for the break point in the previously effective series.
format: double
lastDiscount:
type: number
description: Discount breakpoints tab > Last discount amount > The amount used as the discount for the discount series that was in effect before the effective date.
format: double
pendingDiscountAmount:
type: number
description: Discount breakpoints tab > Pending discount amount > The amount to be used as the discount for the pending series if the Amount option is selected as Discount by.
format: double
pendingDiscountPercent:
type: number
description: Discount breakpoints tab > Pending discount percent > The discount percent to be used for the break point in the pending series.
format: double
freeItemQty:
type: number
description: Discount breakpoints tab > Free item qty. > The quantity of the free item to be added as the discount to orders for this discount series.
format: double
lastFreeItemQty:
type: number
description: Discount breakpoints tab > Last free item qty. > The quantity of the free item that was used as the discount for the previously effective series.
format: double
pendingFreeItemQty:
type: number
description: Discount breakpoints tab > Pending free item qty. > The quantity of the free item to be added as the discount to orders for the pending discount series.
format: double
pendingDate:
type: string
format: date-time
effectiveDate:
type: string
format: date-time
DiscountItemPriceClassDto:
type: object
properties:
priceClassId:
type: string
DtoValueOfInt32:
type: object
properties:
value:
type: integer
format: int32
DtoValueOfBoolean:
type: object
properties:
value:
type: boolean
DiscountDto:
type: object
properties:
discountCode:
type: string
description: 'Mandatory field: The top part > Discount code > The code of the discount for which you want to create a new series or view an existing one.'
series:
type: string
description: 'Mandatory field: The top part > Series > The ID of the series defined for the discount.'
description:
type: string
description: The top part > Description > A brief description of the series.
discountBy:
type: string
description: The top part > Discount by > The way the discount for the series is specified. Percent, Amount, Free item.
breakBy:
type: string
description: The top part > Break by > The way the breakpoints for this discount series are specified. Quantity, Amount.
promotional:
type: boolean
description: The top part > Promotional > A check box that indicates (if selected) that the series is a promotional discount.
active:
type: boolean
description: The top part > Active > A check box that indicates (if selected) that the series is active.
prorateDiscount:
type: boolean
description: The top part > Prorate discount > A check box that indicates (if selected) that the discount can be prorated.
effectiveDate:
type: string
description: The top part > Effective date > The date when the series becomes effective; this field appears for promotional discount series only.
format: date-time
expirationDate:
type: string
description: The top part > Expiration date > The date when the promotional discount expires. This field appears for the series if the Promotional check box is selected.
format: date-time
lastUpdateDate:
type: string
description: The top part > Last update date > A read-only field that shows the date when the discount series was last updated.
format: date-time
freeItem:
type: integer
description: Free item tab > Free item > The free item (by its item ID) that is added to orders as the discount for this series.
format: int32
pendingFreeItem:
type: integer
description: Free item tab > Pending free item > The free item (by its item ID) that will be added to orders as the discount for this series, starting on the date specified in the Pending date column on the Discount breakpoints tab.
format: int32
lastFreeItem:
type: integer
description: Free item tab > Last free item > The free item (by its item ID) that had been added to orders as the discount for this series before the date shown in the Last date column on the Discount breakpoints tab.
format: int32
lineCntr:
type: integer
description: Free item tab > A line counter for the table.
format: int32
createdDateTime:
type: string
format: date-time
lastModifiedDateTime:
type: string
description: Free item tab > Last update date > A read-only field that shows the date when this discount series has been updated last.
format: date-time
timeStamp:
type: string
description: 'Identifier that represents a specific version of the resource.
It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers)'
format: byte
discountBreakpoints:
type: array
items:
$ref: '#/components/schemas/DiscountBreakpointDto'
customers:
type: array
items:
$ref: '#/components/schemas/DiscountCustomer2Dto'
description: Customers tab > Customer > The customer to which the series is applicable.
items:
type: array
items:
$ref: '#/components/schemas/DiscountItemDto'
description: Items tab > Items ID > The stock or non-stock item, by its item ID, to which the series can be applied.
warehouses:
type: array
items:
$ref: '#/components/schemas/DiscountWarehouseDto'
description: Warehouses tab > Warehouse ID > The warehouse to which the series can be applied.
customerPriceClasses:
type: array
items:
$ref: '#/components/schemas/DiscountCustomerPriceClassDto'
description: Customer price classes tab > Customer price class ID > The customer price class to which the series is applicable.
itemPriceClasses:
type: array
items:
$ref: '#/components/schemas/DiscountItemPriceClassDto'
description: Item price classes tab > Price class ID > The item price class to which the series is applicable.
branches:
type: array
items:
$ref: '#/components/schemas/DiscountBranchDto'
description: Branches tab > Branch > The branch to which the series can be applied.
errorInfo:
type: string
metadata:
$ref: '#/components/schemas/MetadataDto'
MetadataDto:
type: object
properties:
totalCount:
type: integer
format: int64
maxPageSize:
type: integer
format: int64
DiscountWarehouseDto:
type: object
properties:
warehouse:
type: string
DtoValueOfString:
type: object
properties:
value:
type: string
DiscountBreakpointUpdateDto:
type: object
properties:
operation:
enum:
- Insert
# --- truncated at 32 KB (34 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/openapi/visma-discount-api-openapi.yml