openapi: 3.0.2
info:
  title: Qvalia Transaction API
  version: 1.0.0
  description: This is Qvalias Transaction API documentation
  contact:
    name: Qvalia Helpdesk
    url: https://qvalia.com/help/
servers:
  - url: https://api-qa.qvalia.com
  - url: https://api.qvalia.com
tags:
  - name: Invoice APIs
    description: Operations related to Invoices
  - name: CreditNote APIs
    description: Operations related to CreditNotes
  - name: Order APIs
    description: Operations related to Orders
  - name: OrderResponse APIs
    description: Operations related to OrderResponses
  - name: OrderAgreement APIs
    description: Operations related to OrderAgreements
  - name: OrderChange APIs
    description: Operations related to OrderChanges
  - name: OrderCancellation APIs
    description: Operations related to OrderCancellations
  - name: Catalogue APIs
    description: Operations related to Catalogues
  - name: DespatchAdvice APIs
    description: Operations related to DespatchAdvices
  - name: MessageLevelResponse APIs
    description: Operations related to MessageLevelResponses
  - name: MessageLevelStatus APIs
    description: Operations related to MessageLevelStatus

paths:
  /transaction/{accountRegNo}/invoices/incoming:
    get:
      tags:
        - Invoice APIs
      summary: 'Get incoming invoices [transaction-type: Invoice]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-invoices-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Invoice APIs
      summary: 'Create incoming invoices [transaction-type: Invoice]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: invoice-apis/post-invoices-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostInvoice'
  /transaction/{accountRegNo}/invoices/incoming/readinvoices:
    get:
      tags:
        - Invoice APIs
      summary: 'Read incoming invoices [transaction-type: Invoice]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-invoices-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/invoices/outgoing:
    get:
      tags:
        - Invoice APIs
      summary: 'Get outgoing invoices [transaction-type: Invoice]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-invoices-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Invoice APIs
      summary: 'Create outgoing invoices [transaction-type: Invoice]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/post-invoices-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostInvoice'
  /transaction/{accountRegNo}/invoices/outgoing/readinvoices:
    get:
      tags:
        - Invoice APIs
      summary: 'Read outgoing invoices [transaction-type: Invoice]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-invoices-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

  /transaction/{accountRegNo}/invoiceresponses/incoming:
    get:
      tags:
        - Invoice APIs
      summary: 'Get incoming invoice responses [transaction-type: InvoiceResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoiceresponses-apis/get-invoiceresponses-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Invoice APIs
      summary: 'Create incoming invoice responses [transaction-type: InvoiceResponse]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: invoiceresponses-apis/post-invoiceresponses-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostApplicationResponse'
  /transaction/{accountRegNo}/invoiceresponses/incoming/readinvoice responses:
    get:
      tags:
        - Invoice APIs
      summary: 'Read incoming invoice responses [transaction-type: InvoiceResponse]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoiceresponses-apis/get-invoiceresponses-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/invoiceresponses/outgoing:
    get:
      tags:
        - Invoice APIs
      summary: 'Get outgoing invoice responses [transaction-type: InvoiceResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoiceresponses-apis/get-invoiceresponses-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Invoice APIs
      summary: 'Create outgoing invoice responses [transaction-type: InvoiceResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoiceresponses-apis/post-invoiceresponses-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostApplicationResponse'
  /transaction/{accountRegNo}/invoiceresponses/outgoing/readinvoice responses:
    get:
      tags:
        - Invoice APIs
      summary: 'Read outgoing invoice responses [transaction-type: InvoiceResponse]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoiceresponses-apis/get-invoiceresponses-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

  /transaction/{accountRegNo}/selfbillinginvoices/incoming:
    get:
      tags:
        - Invoice APIs
      summary: 'Get incoming self billing invoices [transaction-type: Invoice]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: selfbillinginvoice-apis/get-invoices-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Invoice APIs
      summary: 'Create incoming self billing invoices [transaction-type: Invoice]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: selfbillinginvoice-apis/post-invoices-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostInvoice'
  /transaction/{accountRegNo}/selfbillinginvoices/incoming/readselfbillinginvoices:
    get:
      tags:
        - Invoice APIs
      summary: 'Read incoming self billing invoices [transaction-type: Invoice]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: selfbillinginvoice-apis/get-invoices-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/selfbillinginvoices/outgoing:
    get:
      tags:
        - Invoice APIs
      summary: 'Get outgoing self billing invoices [transaction-type: Invoice]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: selfbillinginvoice-apis/get-invoices-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Invoice APIs
      summary: 'Create outgoing self billing invoices [transaction-type: Invoice]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: selfbillinginvoice-apis/post-invoices-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostInvoice'
  /transaction/{accountRegNo}/selfbillinginvoices/outgoing/readselfbillinginvoices:
    get:
      tags:
        - Invoice APIs
      summary: 'Read outgoing self billing invoices [transaction-type: Invoice]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: selfbillinginvoice-apis/get-invoices-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

  /transaction/{accountRegNo}/creditnotes/incoming:
    get:
      tags:
        - CreditNote APIs
      summary: 'Get incoming credit notes [transaction-type: CreditNote]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: creditnote-apis/get-creditnotes-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - CreditNote APIs
      summary: 'Create incoming credit notes [transaction-type: CreditNote]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: creditnote-apis/post-creditnotes-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostCreditNote'
  /transaction/{accountRegNo}/creditnotes/incoming/readcreditnotes:
    get:
      tags:
        - CreditNote APIs
      summary: 'Read incoming credit notes [transaction-type: CreditNote]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: creditnote-apis/get-creditnotes-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/creditnotes/outgoing:
    get:
      tags:
        - CreditNote APIs
      summary: 'Get outgoing credit notes [transaction-type: CreditNote]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: creditnote-apis/get-creditnotes-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - CreditNote APIs
      summary: 'Create outgoing credit notes [transaction-type: CreditNote]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: creditnote-apis/post-creditnotes-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostCreditNote'
  /transaction/{accountRegNo}/creditnotes/outgoing/readcreditnotes:
    get:
      tags:
        - CreditNote APIs
      summary: 'Read outgoing credit notes [transaction-type: CreditNote]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: creditnote-apis/get-creditnotes-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

  /transaction/{accountRegNo}/selfbillingcreditnotes/incoming:
    get:
      tags:
        - CreditNote APIs
      summary: 'Get incoming self billing credit notes [transaction-type: CreditNote]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: selfbillingcreditnote-apis/get-creditnotes-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - CreditNote APIs
      summary: 'Create incoming self billing credit notes [transaction-type: CreditNote]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: selfbillingcreditnote-apis/post-creditnotes-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostCreditNote'
  /transaction/{accountRegNo}/selfbillingcreditnotes/incoming/readselfbillingcreditnotes:
    get:
      tags:
        - CreditNote APIs
      summary: 'Read incoming self billing credit notes [transaction-type: CreditNote]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: selfbillingcreditnote-apis/get-creditnotes-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/selfbillingcreditnotes/outgoing:
    get:
      tags:
        - CreditNote APIs
      summary: 'Get outgoing self billing credit notes [transaction-type: CreditNote]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: selfbillingcreditnote-apis/get-creditnotes-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - CreditNote APIs
      summary: 'Create outgoing self billing credit notes [transaction-type: CreditNote]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: selfbillingcreditnote-apis/post-creditnotes-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostCreditNote'
  /transaction/{accountRegNo}/selfbillingcreditnotes/outgoing/readselfbillingcreditnotes:
    get:
      tags:
        - CreditNote APIs
      summary: 'Read outgoing self billing credit notes [transaction-type: CreditNote]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: selfbillingcreditnote-apis/get-creditnotes-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

  /transaction/{accountRegNo}/orders/incoming:
    get:
      tags:
        - Order APIs
      summary: 'Get incoming orders [transaction-type: Order]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-orders-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Order APIs
      summary: 'Create incoming orders [transaction-type: Order]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: invoice-apis/post-orders-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostOrder'
  /transaction/{accountRegNo}/orders/incoming/readorders:
    get:
      tags:
        - Order APIs
      summary: 'Read incoming orders [transaction-type: Order]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-orders-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/orders/outgoing:
    get:
      tags:
        - Order APIs
      summary: 'Get outgoing orders [transaction-type: Order]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-orders-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Order APIs
      summary: 'Create outgoing orders [transaction-type: Order]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/post-orders-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostOrder'
  /transaction/{accountRegNo}/orders/outgoing/readorders:
    get:
      tags:
        - Order APIs
      summary: 'Read outgoing orders [transaction-type: Order]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-orders-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

  /transaction/{accountRegNo}/orderagreements/incoming:
    get:
      tags:
        - OrderAgreement APIs
      summary: 'Get incoming order agreements [transaction-type: OrderAgreement]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: orderagreement-apis/get-orderagreement-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - OrderAgreement APIs
      summary: 'Create incoming order agreements [transaction-type: OrderAgreement]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: orderagreement-apis/post-orderagreement-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostOrderResponse'
  /transaction/{accountRegNo}/orderagreements/incoming/readorderagreement:
    get:
      tags:
        - OrderAgreement APIs
      summary: 'Read incoming order agreements [transaction-type: OrderAgreement]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: orderagreement-apis/get-orderagreement-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/orderagreements/outgoing:
    get:
      tags:
        - OrderAgreement APIs
      summary: 'Get outgoing order agreements [transaction-type: OrderAgreement]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: orderagreement-apis/get-orderagreement-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - OrderAgreement APIs
      summary: 'Create order agreements [transaction-type: OrderAgreement]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: orderagreement-apis/post-orderagreement-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostOrderResponse'
  /transaction/{accountRegNo}/orderagreements/outgoing/readorderagreement:
    get:
      tags:
        - OrderAgreement APIs
      summary: 'Read order agreements [transaction-type: OrderAgreement]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: orderagreement-apis/get-orderagreement-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

  /transaction/{accountRegNo}/orderresponses/incoming:
    get:
      tags:
        - OrderResponse APIs
      summary: 'Get incoming OrderResponses [transaction-type: OrderResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-orderresponses-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - OrderResponse APIs
      summary: 'Create incoming OrderResponse [transaction-type: OrderResponse]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: invoice-apis/post-orderresponses-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostOrderResponse'
  /transaction/{accountRegNo}/orderresponses/incoming/readorderresponses:
    get:
      tags:
        - OrderResponse APIs
      summary: 'Read incoming OrderResponses [transaction-type: OrderResponse]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-orderresponses-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/orderresponses/outgoing:
    get:
      tags:
        - OrderResponse APIs
      summary: 'Get outgoing OrderResponses [transaction-type: OrderResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-orderresponses-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - OrderResponse APIs
      summary: 'Create outgoing OrderResponse [transaction-type: OrderResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/post-orderresponses-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostOrderResponse'
  /transaction/{accountRegNo}/orderresponses/outgoing/readorderresponses:
    get:
      tags:
        - OrderResponse APIs
      summary: 'Read outgoing OrderResponses [transaction-type: OrderResponse]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-orderresponses-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  
  /transaction/{accountRegNo}/order-changes/incoming:
    get:
      tags:
        - OrderChange APIs
      summary: 'Get incoming OrderChanges [transaction-type: OrderChange]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-order-changes-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - OrderChange APIs
      summary: 'Create incoming OrderChanges [transaction-type: OrderChange]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: invoice-apis/post-order-changes-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostOrderChange'
  /transaction/{accountRegNo}/order-changes/incoming/readorderchanges:
    get:
      tags:
        - OrderChange APIs
      summary: 'Read incoming OrderChanges [transaction-type: OrderChange]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-order-changes-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/order-changes/outgoing:
    get:
      tags:
        - OrderChange APIs
      summary: 'Get outgoing OrderChanges [transaction-type: OrderChange]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-order-changes-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - OrderChange APIs
      summary: 'Create outgoing OrderChanges [transaction-type: OrderChange]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/post-order-changes-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostOrderChange'
  /transaction/{accountRegNo}/order-changes/outgoing/readorderchanges:
    get:
      tags:
        - OrderChange APIs
      summary: 'Read outgoing OrderChanges [transaction-type: OrderChange]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-order-changes-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  
  /transaction/{accountRegNo}/order-cancellations/incoming:
    get:
      tags:
        - OrderCancellation APIs
      summary: 'Get incoming OrderCancellations [transaction-type: OrderCancellation]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-order-cancellations-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - OrderCancellation APIs
      summary: 'Create incoming OrderCancellations [transaction-type: OrderCancellation]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: invoice-apis/post-order-cancellations-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostOrderCancellation'
  /transaction/{accountRegNo}/order-cancellations/incoming/readordercancellations:
    get:
      tags:
        - OrderCancellation APIs
      summary: 'Read incoming OrderCancellations [transaction-type: OrderCancellation]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-order-cancellations-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/order-cancellations/outgoing:
    get:
      tags:
        - OrderCancellation APIs
      summary: 'Get outgoing OrderCancellations [transaction-type: OrderCancellation]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-order-cancellations-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - OrderCancellation APIs
      summary: 'Create outgoing OrderCancellations [transaction-type: OrderCancellation]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/post-order-cancellations-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostOrderCancellation'
  /transaction/{accountRegNo}/order-cancellations/outgoing/readordercancellations:
    get:
      tags:
        - OrderCancellation APIs
      summary: 'Read outgoing OrderCancellations [transaction-type: OrderCancellation]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-order-cancellations-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  
  /transaction/{accountRegNo}/catalogues/incoming:
    get:
      tags:
        - Catalogue APIs
      summary: 'Get incoming Catalogues [transaction-type: Catalogue]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-catalogues-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Catalogue APIs
      summary: 'Create incoming Catalogues [transaction-type: Catalogue]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: invoice-apis/post-catalogues-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostCatalogue'
  /transaction/{accountRegNo}/catalogues/incoming/readcatalogues:
    get:
      tags:
        - Catalogue APIs
      summary: 'Read incoming Catalogues [transaction-type: Catalogue]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-catalogues-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/catalogues/outgoing:
    get:
      tags:
        - Catalogue APIs
      summary: 'Get outgoing Catalogues [transaction-type: Catalogue]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-catalogues-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Catalogue APIs
      summary: 'Create outgoing Catalogues [transaction-type: Catalogue]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/post-catalogues-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostCatalogue'
  /transaction/{accountRegNo}/catalogues/outgoing/readcatalogues:
    get:
      tags:
        - Catalogue APIs
      summary: 'Read outgoing Catalogues [transaction-type: Catalogue]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-catalogues-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

  /transaction/{accountRegNo}/catalogueresponses/incoming:
    get:
      tags:
        - Catalogue APIs
      summary: 'Get incoming catalogue responses [transaction-type: CatalogueResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: catalogueresponses-apis/get-catalogueresponses-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Catalogue APIs
      summary: 'Create incoming catalogue responses [transaction-type: CatalogueResponse]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: catalogueresponses-apis/post-catalogueresponses-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostApplicationResponse'
  /transaction/{accountRegNo}/catalogueresponses/incoming/readcatalogueresponses:
    get:
      tags:
        - Catalogue APIs
      summary: 'Read incoming catalogue responses [transaction-type: CatalogueResponse]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: catalogueresponses-apis/get-catalogueresponses-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/catalogueresponses/outgoing:
    get:
      tags:
        - Catalogue APIs
      summary: 'Get outgoing catalogue responses [transaction-type: CatalogueResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: catalogueresponses-apis/get-catalogueresponses-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - Catalogue APIs
      summary: 'Create outgoing catalogue responses [transaction-type: CatalogueResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: catalogueresponses-apis/post-catalogueresponses-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostApplicationResponse'
  /transaction/{accountRegNo}/catalogueresponses/outgoing/readcatalogueresponses:
    get:
      tags:
        - Catalogue APIs
      summary: 'Read outgoing catalogue responses [transaction-type: CatalogueResponse]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: catalogueresponses-apis/get-catalogueresponses-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  
  /transaction/{accountRegNo}/despatch-advices/incoming:
    get:
      tags:
        - DespatchAdvice APIs
      summary: 'Get incoming DespatchAdvices [transaction-type: DespatchAdvice]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-despatch-advices-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - DespatchAdvice APIs
      summary: 'Create incoming DespatchAdvices [transaction-type: DespatchAdvice]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: invoice-apis/post-despatch-advices-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostDespatchAdvice'
  /transaction/{accountRegNo}/despatch-advices/incoming/readdespatchadvices:
    get:
      tags:
        - DespatchAdvice APIs
      summary: 'Read incoming DespatchAdvices [transaction-type: DespatchAdvice]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-despatch-advices-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/despatch-advices/outgoing:
    get:
      tags:
        - DespatchAdvice APIs
      summary: 'Get outgoing DespatchAdvices [transaction-type: DespatchAdvice]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/get-despatch-advices-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - DespatchAdvice APIs
      summary: 'Create outgoing DespatchAdvices [transaction-type: DespatchAdvice]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: invoice-apis/post-despatch-advices-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostDespatchAdvice'
  /transaction/{accountRegNo}/despatch-advices/outgoing/readdespatchadvices:
    get:
      tags:
        - DespatchAdvice APIs
      summary: 'Read outgoing DespatchAdvices [transaction-type: DespatchAdvice]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: invoice-apis/get-despatch-advices-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

  /transaction/{accountRegNo}/messagelevelresponses/incoming:
    get:
      tags:
        - MessageLevelResponse APIs
      summary: 'Get incoming message level responses [transaction-type: MessageLevelResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: messagelevelresponses-apis/get-messagelevelresponses-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - MessageLevelResponse APIs
      summary: 'Create incoming message level responses [transaction-type: MessageLevelResponse]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: messagelevelresponses-apis/post-messagelevelresponses-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostApplicationResponse'
  /transaction/{accountRegNo}/messagelevelresponses/incoming/readmessagelevelresponses:
    get:
      tags:
        - MessageLevelResponse APIs
      summary: 'Read incoming message level responses [transaction-type: MessageLevelResponse]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: messagelevelresponses-apis/get-messagelevelresponses-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/messagelevelresponses/outgoing:
    get:
      tags:
        - MessageLevelResponse APIs
      summary: 'Get outgoing message level responses [transaction-type: MessageLevelResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: messagelevelresponses-apis/get-messagelevelresponses-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - MessageLevelResponse APIs
      summary: 'Create message level responses [transaction-type: MessageLevelResponse]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: messagelevelresponses-apis/post-messagelevelresponses-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostApplicationResponse'
  /transaction/{accountRegNo}/messagelevelresponses/outgoing/readmessagelevelresponses:
    get:
      tags:
        - MessageLevelResponse APIs
      summary: 'Read message level responses [transaction-type: MessageLevelResponse]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: messagelevelresponses-apis/get-messagelevelresponses-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

  /transaction/{accountRegNo}/messagelevelstatus/incoming:
    get:
      tags:
        - MessageLevelStatus APIs
      summary: 'Get incoming message level status [transaction-type: MessageLevelStatus]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: messagelevelstatus-apis/get-messagelevelstatus-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - MessageLevelStatus APIs
      summary: 'Create incoming message level status [transaction-type: MessageLevelStatus]'
      description: |-
        The request can be either JSON or XML. Each individual message must be POST'ed as an object, JSON Array is not suported!
      operationId: messagelevelstatus-apis/post-messagelevelstatus-incoming
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostApplicationResponse'
  /transaction/{accountRegNo}/messagelevelstatus/incoming/readmessagelevelstatus:
    get:
      tags:
        - MessageLevelStatus APIs
      summary: 'Read incoming message level status [transaction-type: MessageLevelStatus]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: messagelevelstatus-apis/get-messagelevelstatus-incoming-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
  /transaction/{accountRegNo}/messagelevelstatus/outgoing:
    get:
      tags:
        - MessageLevelStatus APIs
      summary: 'Get outgoing message level status [transaction-type: MessageLevelStatus]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: messagelevelstatus-apis/get-messagelevelstatus-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/integrationId'
        - $ref: '#/components/parameters/documentId'
        - $ref: '#/components/parameters/from'
        - $ref: '#/components/parameters/to'
        - $ref: '#/components/parameters/updatedAtFrom'
        - $ref: '#/components/parameters/updatedAtTo'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
        - MessageLevelStatus APIs
      summary: 'Create message level status [transaction-type: MessageLevelStatus]'
      description: |-
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
        
        To get new messages only, use the  `"Read"` endpoint instead!
      operationId: messagelevelstatus-apis/post-messagelevelstatus-outgoing
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/overWrite'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/ContentType'
      responses:
        '200':
          $ref: '#/components/responses/200-post'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'
      requestBody:
        $ref: '#/components/requestBodies/transactionPostApplicationResponse'
  /transaction/{accountRegNo}/messagelevelstatus/outgoing/readmessagelevelstatus:
    get:
      tags:
        - MessageLevelStatus APIs
      summary: 'Read message level statuss [transaction-type: MessageLevelStatus]'
      description: |-
        Through this endpoint you will get any unread (=previously fetched) message(s). After you have fetched through this request the message will be automatically marked as `read`
        
        The response, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
        
        With JSON, use the `limit` parameter to change the number of returned messages and combine it with `offset` to traverse through your available messages.
      operationId: messagelevelstatus-apis/get-messagelevelstatus-outgoing-read
      security:
        - api_key: []
      parameters:
        - $ref: '#/components/parameters/accountRegNo'
        - $ref: '#/components/parameters/limit'
        - $ref: '#/components/parameters/offset'
        - $ref: '#/components/parameters/includeRead'
        - $ref: '#/components/parameters/Authorization'
        - $ref: '#/components/parameters/Accept'
      responses:
        '200':
          $ref: '#/components/responses/200'
        '204':
          $ref: '#/components/responses/204'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '409':
          $ref: '#/components/responses/409'
        '422':
          $ref: '#/components/responses/422'
        '500':
          $ref: '#/components/responses/500'

components:
  parameters:
    accountRegNo:
      name: accountRegNo
      in: path
      required: true
      schema:
        type: string
        example: ''
        description: ''
        default: ''
      description: Account registration number issued by Qvalia
    limit:
      name: limit
      in: query
      required: false
      schema:
        type: number
        example: 5
        description: How many messages to return in Array (XML is always one!)
        default: 3
      description: How many messages to return in Array (XML is always one!)
    includeRead:
      name: includeRead
      in: query
      required: false
      schema:
        type: boolean
        example: false
        description: If you are using the "read" enpoints, make it include previously read messages
        default: false
      description: If you are using the "read" enpoints, make it include previously read messages
    offset:
      name: offset
      in: query
      required: false
      schema:
        type: number
        example: 0
        description: Where to start index for using limit/offset listing
        default: 0
      description: Where to start index for using limit/offset listing
    documentId:
      name: documentId
      in: query
      required: false
      schema:
        type: string
        example: ''
        description: ''
        default: ''
      description: The document identifier of teh message, e.g. Invoice number
    from:
      name: from
      in: query
      required: false
      schema:
        type: string
        example: ''
        description: YYYY-MM-DD, e.g. 2024-01-01
        default: ''
      description: Date created from YYYY-MM-DD, e.g. 2024-01-01
    to:
      name: to
      in: query
      required: false
      schema:
        type: string
        example: ''
        description: YYYY-MM-DD, e.g. 2024-01-01
        default: ''
      description: Date created to YYYY-MM-DD, e.g. 2024-01-01
    updatedAtFrom:
      name: updatedAtFrom
      in: query
      required: false
      schema:
        type: string
        example: ''
        description: YYYY-MM-DD, e.g. 2024-01-01
        default: ''
      description: Date updated from YYYY-MM-DD, e.g. 2024-01-01
    updatedAtTo:
      name: updatedAtTo
      in: query
      required: false
      schema:
        type: string
        example: ''
        description: YYYY-MM-DD, e.g. 2024-01-01
        default: ''
      description: Date updated to YYYY-MM-DD, e.g. 2024-01-01
    integrationId:
      name: integrationId
      in: query
      required: false
      schema:
        type: string
        example: ''
        description: ''
        default: ''
      description: Qvalia unique identifier for the transaction/message
    overWrite:
      name: overWrite
      in: query
      required: false
      schema:
        type: boolean
        example: false
        default: false
      description: For POST requests, chose to overwrite upon a `409 Conflict` response to reprocess the message with the same document ID and receiver (i.e. send the same message again)
    Authorization:
      name: Authorization
      in: header
      required: true
      schema:
        type: string
        example: ''
        description: ''
        default: ''
      description: API key
    Accept:
      name: Accept
      in: header
      required: false
      schema:
        type: string
        example: ''
        default: 'application/json'
      description: Either "application/json" (default) or "application/xml"
    ContentType:
      name: Content-Type
      in: header
      required: false
      schema:
        type: string
        example: ''
        default: 'application/json'
      description: Either "application/json" (default) or "application/xml"

  responses:
    '200':
      description: 'OK'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/transactionResponse'
        application/xml:
          schema:
            $ref: '#/components/schemas/transactionResponseXML'
      headers:
        integrationid:
          schema:
            type: string
          description: Only included as header in XML!
    200-post:
      description: 'OK'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/transactionPostResponse'
        application/xml:
          schema:
            $ref: '#/components/schemas/transactionPostResponseXML'

    '204':
      description: 'No content'
      content:
        application/json:
          schema:
            type: object
            properties: {}
    '400':
      description: 'Bad Request'
      content:
        application/json:
          schema:
            type: object
            properties:
              statusCode:
                type: integer
                description: ''
                example: 400
              error:
                type: string
                description: ''
                example: E_INVALID_PARAMETER
              message:
                type: string
                description: ''
                example: Invalid parameters from client
    '401':
      description: 'Unauthorized'
      content:
        application/json:
          schema:
            type: object
            properties:
              statusCode:
                type: integer
                description: ''
                example: 401
              error:
                type: string
                description: ''
                example: Unauthorized
              message:
                type: string
                description: ''
                example: Unauthorized
    '403':
      description: 'Forbidden'
      content:
        application/json:
          schema:
            type: object
            properties:
              statusCode:
                type: integer
                description: ''
                example: 403
              error:
                type: string
                description: ''
                example: E_MISSING_PERMISSION
              message:
                type: string
                description: ''
                example: Permission denied
    '404':
      description: 'Not Found'
      content:
        application/json:
          schema:
            type: object
            properties:
              statusCode:
                type: integer
                description: ''
                example: 404
              error:
                type: string
                description: ''
                example: E_MISSING
              message:
                type: string
                description: ''
                example: Requested resource missing or unavailable
    '409':
      description: 'Conflict'
      content:
        application/json:
          schema:
            type: object
            properties:
              status:
                type: string
                description: ''
                example: error
              type:
                type: string
                description: ''
                example: E_CONFLICT
              data:
                type: string
                description: ''
                example: Conflicting payload
              metadata:
                type: object
                description: ''
                properties:
                  debug_error_message:
                    type: string
                    description: ''
                    example: Conflicting payload
                  debug_error_code:
                    type: integer
                    description: ''
                    example: 409
                required: ['']
    '422':
      description: 'Unprocessable Entity'
      content:
        application/json:
          schema:
            type: object
            properties:
              status:
                type: string
                description: ''
                example: error
              type:
                type: string
                description: ''
                example: E_VALIDATION
              data:
                type: string
                description: ''
                example: Invalid payload
              metadata:
                type: object
                description: ''
                example:
                  description: Invoice does not conform to UBL 2.1
                  details: {}
                properties:
                  description:
                    type: string
                    description: ''
                    example: Invoice does not conform to UBL 2.1
                  details:
                    type: object
                    description: ''
                    example: {}
                    properties: {}
                    required: ['']
                required: ['']
    '500':
      description: 'Internal Server Error'
      content:
        application/json:
          schema:
            type: object
            properties:
              status:
                type: string
                description: ''
                example: error
              type:
                type: string
                description: ''
                example: E_INTERNAL_SERVER_ERROR
              data:
                type: string
                description: ''
                example: Internal Server Error (It's not you, it's us)
              metadata:
                type: object
                description: ''
                properties:
                  description:
                    type: string
                    description: ''
                    example: 'Try again, if problem persists contact us at help@qvalia.com'
                  details:
                    type: object
                    description: ''
                    properties: {}
                    required: ['']
                required: ['']

  requestBodies:
    transactionPostInvoice:
      description: 'Request body'
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/InvoiceJSON'
        application/xml:
          schema:
            $ref: '#/components/schemas/Invoice'
    transactionPostCreditNote:
      description: 'Request body'
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/CreditNoteJSON'
        application/xml:
          schema:
            $ref: '#/components/schemas/CreditNote'
    transactionPostOrder:
      description: 'Request body'
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/OrderJSON'
        application/xml:
          schema:
            $ref: '#/components/schemas/Order'
    transactionPostOrderResponse:
      description: 'Request body'
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/OrderResponseJSON'
        application/xml:
          schema:
            $ref: '#/components/schemas/OrderResponse'
    transactionPostOrderChange:
      description: 'Request body'
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/OrderChangeJSON'
        application/xml:
          schema:
            $ref: '#/components/schemas/OrderChange'
    transactionPostOrderCancellation:
      description: 'Request body'
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/OrderCancellationJSON'
        application/xml:
          schema:
            $ref: '#/components/schemas/OrderCancellation'
    transactionPostCatalogue:
      description: 'Request body'
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/CatalogueJSON'
        application/xml:
          schema:
            $ref: '#/components/schemas/Catalogue'
    transactionPostDespatchAdvice:
      description: 'Request body'
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/DespatchAdviceJSON'
        application/xml:
          schema:
            $ref: '#/components/schemas/DespatchAdvice'
    transactionPostApplicationResponse:
      description: 'Request body'
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApplicationResponseJSON'
        application/xml:
          schema:
            $ref: '#/components/schemas/ApplicationResponse'

  schemas:
    InvoiceJSON:
      type: object
      properties:
        Invoice: # This will be the root of JSON
          type: object
          description: ''
          properties: {}
          required: ['']
    Invoice: # XML Must have XML Root element name here to parse sample properly
      type: object
      description: ''
      properties: {}
      required: ['']

    ApplicationResponseJSON:
      type: object
      properties:
        ApplicationResponse: # This will be the root of JSON
          type: object
          description: ''
          properties: {}
          required: ['']
    ApplicationResponse: # XML Must have XML Root element name here to parse sample properly
      type: object
      description: ''
      properties: {}
      required: ['']

    CreditNoteJSON:
      type: object
      properties:
        CreditNote: # This will be the root of JSON
          type: object
          description: ''
          properties: {}
          required: ['']
    CreditNote: # XML Must have XML Root element name here to parse sample properly
      type: object
      description: ''
      properties: {}
      required: ['']

    OrderJSON:
      type: object
      properties:
        Order: # This will be the root of JSON
          type: object
          description: ''
          properties: {}
          required: ['']
    Order: # XML Must have XML Root element name here to parse sample properly
      type: object
      description: ''
      properties: {}
      required: ['']

    OrderResponseJSON:
      type: object
      properties:
        OrderResponse: # This will be the root of JSON
          type: object
          description: ''
          properties: {}
          required: ['']
    OrderResponse: # XML Must have XML Root element name here to parse sample properly
      type: object
      description: ''
      properties: {}
      required: ['']

    OrderChangeJSON:
      type: object
      properties:
        OrderChange: # This will be the root of JSON
          type: object
          description: ''
          properties: {}
          required: ['']
    OrderChange: # XML Must have XML Root element name here to parse sample properly
      type: object
      description: ''
      properties: {}
      required: ['']

    OrderCancellationJSON:
      type: object
      properties:
        OrderCancellation: # This will be the root of JSON
          type: object
          description: ''
          properties: {}
          required: ['']
    OrderCancellation: # XML Must have XML Root element name here to parse sample properly
      type: object
      description: ''
      properties: {}
      required: ['']

    CatalogueJSON:
      type: object
      properties:
        Catalogue: # This will be the root of JSON
          type: object
          description: ''
          properties: {}
          required: ['']
    Catalogue: # XML Must have XML Root element name here to parse sample properly
      type: object
      description: ''
      properties: {}
      required: ['']

    DespatchAdviceJSON:
      type: object
      properties:
        DespatchAdvice: # This will be the root of JSON
          type: object
          description: ''
          properties: {}
          required: ['']
    DespatchAdvice: # XML Must have XML Root element name here to parse sample properly
      type: object
      description: ''
      properties: {}
      required: ['']
    
    transactionResponse:
      type: object
      properties:
        status:
          type: string
          example: success
        data:
          type: array
          items:
            type: object
            properties:
              '{transaction-type}':
                type: object
              integrationId:
                type: string
      xml:
        name: '{transaction-type}'
    transactionResponseXML:
      type: object
      properties:
        'message-data-elements':
          type: object
      xml:
        name: '{transaction-type}'
    transactionPostResponse:
      type: object
      properties:
        status:
          type: string
          example: success
        data:
          type: object
          properties:
            message:
              type: string
              example: '{transaction-type} 100-1000 sent'
            '{transaction-type}_id':
              type: string
              example: '100-1000'
            integrationId:
              type: string
              example: '4725a033-e501-4e2f-afa5-3a5c24eb5e28'
      xml:
        name: 'success'
    transactionPostResponseXML:
      type: object
      properties:
        message:
          type: string
          example: '{transaction-type} 100-1000 sent'
        '{transaction-type}_id':
          type: string
          example: '100-1000'
        integrationId:
          type: string
          example: '4725a033-e501-4e2f-afa5-3a5c24eb5e28'
      xml:
        name: 'success'

  securitySchemes:
      api_key:
        type: apiKey
        name: Authorization
        in: header
