Visma

Visma Kit Specifications API

The KitSpecifications API from Visma — 3 operation(s) for kitspecifications.

GitHub OpenAPI

Operations 5

GET /v1/KitSpecifications Get a range of Kit Specifications - ScreenId = IN209500 #
POST /v1/KitSpecifications Creates a KitSpecification #
GET /v1/KitSpecifications/{kitInventoryID}/{revisionID} Get a specific KitSpecification #
PUT /v1/KitSpecifications/{kitInventoryID}/{revisionID} Updates a specific KitSpecification #
GET /v1/KitSpecifications/{kitInventoryID} Get all revisions for a specific KitSpecification #

Documentation

📖
Documentation
https://docs.vismasoftware.no/vismanetapi/
📖
APIReference
https://docs.vismasoftware.no/vismanetapi/api-reference/
📖
GettingStarted
https://docs.vismasoftware.no/vismanetapi/introduction/getting-started-with-visma-net-api/
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/rate-limits/visma-rate-limits.yml
📖
Documentation
https://developer.vismaonline.com/docs/spiris-eaccounting-api-documentation
📖
APIReference
https://eaccountingapi.vismaonline.com/swagger/ui/index
📖
Documentation
https://developer.vismaonline.com/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/openapi/visma-kitspecifications-api-openapi.yml

Other Resources

🔗
Webhooks
https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/asyncapi/visma-net-erp-webhooks.yml
🔗
Support
https://docs.vismasoftware.no/vismanetapi/support/
🔗
Deprecation
https://docs.vismasoftware.no/vismanetapi/end-of-life-notices/
🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/conventions/visma-conventions.yml
🔗
LLMsTxt
https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/llms/visma-eaccounting-llms.txt
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/visma/refs/heads/main/errors/visma-problem-types.yml
🔗
ChangeLog
https://developer.vismaonline.com/changelog

Work with this as data

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-kitspecifications-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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

visma-kitspecifications-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Visma.net ERP Kit Specifications API
  version: v1
servers:
- url: https://api.finance.visma.net
tags:
- name: KitSpecifications
paths:
  /v1/KitSpecifications:
    get:
      tags:
      - KitSpecifications
      summary: Get a range of Kit Specifications - ScreenId = IN209500
      operationId: KitSpecifications_GetAll
      parameters:
      - name: lastModifiedDateTime
        in: query
        schema:
          type: string
      - name: lastModifiedDateTimeCondition
        in: query
        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: kitInventoryID
        in: query
        schema:
          type: string
      - name: revisionID
        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/BasePaginationDtoOfKitSpecificationDto'
            text/json:
              schema:
                $ref: '#/components/schemas/BasePaginationDtoOfKitSpecificationDto'
        '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:
      - KitSpecifications
      summary: Creates a KitSpecification
      description: Response Message has StatusCode Created if POST operation succeed
      operationId: KitSpecifications_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: Defines the data for the KitSpecification to create
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/KitSpecificationUpdateDto'
          text/json:
            schema:
              $ref: '#/components/schemas/KitSpecificationUpdateDto'
          application/xml:
            schema:
              $ref: '#/components/schemas/KitSpecificationUpdateDto'
          text/xml:
            schema:
              $ref: '#/components/schemas/KitSpecificationUpdateDto'
          application/x-www-form-urlencoded:
            schema:
              $ref: '#/components/schemas/KitSpecificationUpdateDto'
        required: true
        x-bodyName: kitSpecificationUpdateDto
      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/KitSpecifications/{kitInventoryID}/{revisionID}:
    get:
      tags:
      - KitSpecifications
      summary: Get a specific KitSpecification
      description: Data for the INKitSpecHdr
      operationId: KitSpecifications_GetBykitInventoryIDrevisionID
      parameters:
      - name: kitInventoryID
        in: path
        description: kitInventoryID
        required: true
        schema:
          type: string
      - name: revisionID
        in: path
        description: revisionID
        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/KitSpecificationDto'
            text/json:
              schema:
                $ref: '#/components/schemas/KitSpecificationDto'
        '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:
      - KitSpecifications
      summary: Updates a specific KitSpecification
      description: Response Message has StatusCode NoContent if PUT operation succeed
      operationId: KitSpecifications_PutBykitInventoryIDrevisionID
      parameters:
      - name: kitInventoryID
        in: path
        description: kitInventoryID
        required: true
        schema:
          type: string
      - name: revisionID
        in: path
        description: revisionID
        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 the KitSpecification
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/KitSpecificationUpdateDto'
          text/json:
            schema:
              $ref: '#/components/schemas/KitSpecificationUpdateDto'
          application/xml:
            schema:
              $ref: '#/components/schemas/KitSpecificationUpdateDto'
          text/xml:
            schema:
              $ref: '#/components/schemas/KitSpecificationUpdateDto'
          application/x-www-form-urlencoded:
            schema:
              $ref: '#/components/schemas/KitSpecificationUpdateDto'
        required: true
        x-bodyName: kitSpecificationUpdateDto
      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/KitSpecifications/{kitInventoryID}:
    get:
      tags:
      - KitSpecifications
      summary: Get all revisions for a specific KitSpecification
      description: Data for the INKitSpecHdr
      operationId: KitSpecifications_GetBykitInventoryID
      parameters:
      - name: kitInventoryID
        in: path
        description: kitInventoryID
        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/BasePaginationDtoOfKitSpecificationDto'
            text/json:
              schema:
                $ref: '#/components/schemas/BasePaginationDtoOfKitSpecificationDto'
        '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:
    DtoValueOfNullableOfInt32:
      type: object
      properties:
        value:
          type: integer
          format: int32
    MetadataDto:
      type: object
      properties:
        totalCount:
          type: integer
          format: int64
        maxPageSize:
          type: integer
          format: int64
    KitSpecificationUpdateDto:
      type: object
      properties:
        operation:
          enum:
          - Insert
          - Update
          - Delete
          type: string
        kitInventoryID:
          $ref: '#/components/schemas/DtoValueOfString'
        revisionID:
          $ref: '#/components/schemas/DtoValueOfString'
        descr:
          $ref: '#/components/schemas/DtoValueOfString'
        isActive:
          $ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
        allowCompAddition:
          $ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
        isNonStock:
          $ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
        stockComponentLines:
          type: array
          items:
            $ref: '#/components/schemas/KitSpecificationStockComponentsUpdateDto'
        nonStockComponentLines:
          type: array
          items:
            $ref: '#/components/schemas/KitSpecificationNonStockComponentsUpdateDto'
    KitSpecificationDto:
      type: object
      properties:
        kitInventoryID:
          type: string
        revision:
          type: string
        description:
          type: string
        isActive:
          type: boolean
        allowComponentAddition:
          type: boolean
        isNonStock:
          type: boolean
        createdDateTime:
          type: string
          format: date-time
        lastModifiedDateTime:
          type: string
          format: date-time
        stockComponentLines:
          type: array
          items:
            $ref: '#/components/schemas/KitSpecificationStockComponentsDto'
        nonStockComponentLines:
          type: array
          items:
            $ref: '#/components/schemas/KitSpecificationNonStockComponentDto'
        timestamp:
          type: string
          description: Timestamp of the kit specification record
        errorInfo:
          type: string
        metadata:
          $ref: '#/components/schemas/MetadataDto'
    KitSpecificationNonStockComponentDto:
      type: object
      properties:
        lineNbr:
          type: integer
          format: int32
        componentID:
          type: string
        componentQty:
          type: number
          format: double
        uom:
          type: string
        allowComponentQtyVariance:
          type: boolean
        minComponentQty:
          type: number
          format: double
        maxComponentQty:
          type: number
          format: double
        description:
          type: string
        errorInfo:
          type: string
        metadata:
          $ref: '#/components/schemas/MetadataDto'
    BackgroundApiAcceptedDto:
      type: object
      properties:
        id:
          type: string
        stateLocation:
          type: string
    DtoValueOfString:
      type: object
      properties:
        value:
          type: string
    BasePaginationDtoOfKitSpecificationDto:
      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/KitSpecificationDto'
    KitSpecificationStockComponentsDto:
      type: object
      properties:
        lineNbr:
          type: integer
          format: int32
        componentID:
          type: string
        componentQty:
          type: number
          format: double
        uom:
          type: string
        allowComponentQtyVariance:
          type: boolean
        minComponentQty:
          type: number
          format: double
        maxComponentQty:
          type: number
          format: double
        disassemblyCoeff:
          type: number
          format: double
        allowComponentSubstitution:
          type: boolean
        description:
          type: string
        errorInfo:
          type: string
        metadata:
          $ref: '#/components/schemas/MetadataDto'
    KitSpecificationStockComponentsUpdateDto:
      type: object
      properties:
        operation:
          enum:
          - Insert
          - Update
          - Delete
          type: string
        lineNbr:
          $ref: '#/components/schemas/DtoValueOfNullableOfInt32'
        compInventoryID:
          $ref: '#/components/schemas/DtoValueOfString'
        dfltCompQty:
          $ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
        uom:
          $ref: '#/components/schemas/DtoValueOfString'
        allowQtyVariation:
          $ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
        minCompQty:
          $ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
        maxCompQty:
          $ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
        disassemblyCoeff:
          $ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
        allowSubstitution:
          $ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
    DtoValueOfNullableOfDecimal:
      type: object
      properties:
        value:
          type: number
          format: double
    DtoValueOfNullableOfBoolean:
      type: object
      properties:
        value:
          type: boolean
    KitSpecificationNonStockComponentsUpdateDto:
      type: object
      properties:
        operation:
          enum:
          - Insert
          - Update
          - Delete
          type: string
        lineNbr:
          $ref: '#/components/schemas/DtoValueOfNullableOfInt32'
        compInventoryID:
          $ref: '#/components/schemas/DtoValueOfString'
        dfltCompQty:
          $ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
        uom:
          $ref: '#/components/schemas/DtoValueOfString'
        allowQtyVariation:
          $ref: '#/components/schemas/DtoValueOfNullableOfBoolean'
        minCompQty:
          $ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
        maxCompQty:
          $ref: '#/components/schemas/DtoValueOfNullableOfDecimal'
  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
            vismanet_erp_interactive_api:delete: vismanet_erp_interactive_api:delete
            vismanet_erp_interactive_api:ui-extension: vismanet_erp_interactive_api:ui-extension