Skip to content
VNFIndicatorNotification.yaml 3.95 KiB
Newer Older
  title: "DRAFT VNF Indicator Notification Endpoint interface"
  description: >
    DRAFT VNF Indicator Notification Endpoint interface of ETSI NFV SOL002
    IMPORTANT: Please note that this file might be not aligned to the current
    version of the ETSI Group Specification it refers to and has not been
    approved by the ETSI NFV ISG. In case of discrepancies the published ETSI
    Group Specification takes precedence.
    Please report bugs to https://forge.etsi.org/bugzilla/buglist.cgi?component=Nfv-Openapis&list_id=61&product=NFV&resolution=---
  termsOfService: "http://etsi.org"
  contact: 
    name: "NFV-SOL WG"
  license:
    name: "ETSI Forge copyright notice"
    url: https://forge.etsi.org/etsi-forge-copyright-notice.txt


basePath: /callback/v1

schemes: 
  - http
  - https

consumes: 
  - application/json

produces: 
  - application/json


paths:



    /notificationendpoint:
      post:
        summary: Notification endpoint
        description: >
          The API producer can use this resource to send notifications related to VNF indicator
          value changes to a subscribed API consumer, which has provided the URI of this resource
          during the subscription process.
          The POST method delivers a notification from the server to the client.
        parameters:
         - name: vnfIndicatorValueChangeNotification
           in: body
           description: >
             A notification about VNF indicator value changes.
           required: true
           schema: 
             $ref: 'definitions/VnfIndicatorValueChangeNotification_def.yaml#/definitions/VnfIndicatorValueChangeNotification'                  
        responses:
          204:
            description: >
              The notification was delivered successfully. The response body shall be empty.
          400: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/400' }
          401: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/401' }
          403: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/403' }
          404: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/404' }
          405: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/405' }
          406: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/406' }
          409: { $ref: 'responses/VNFIndicatorNotification_resp.yaml#/responses/409' }
          416: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/416' }
          422: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/422' }
          500: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/500' }
          503: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/503' }
      get:
        summary: Test notification endpoint.
        description: >
          The GET method allows the server to test the notification endpoint that is provided
          by the client, e.g. during subscription.
        responses:
          204:
            description: >
              The notification endpoint was tested successfully. The response body shall be empty.
          400: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/400' }
          401: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/401' }
          403: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/403' }
          404: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/404' }
          405: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/405' }
          406: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/406' }
          409: { $ref: 'responses/VNFIndicatorNotification_resp.yaml#/responses/409' }
          416: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/416' }
          422: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/422' }
          500: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/500' }
          503: { $ref: '../../responses/SOL002SOL003_resp.yaml#/responses/503' }