NSDManagementNotification.yaml 40 KB
Newer Older
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/405"
        406:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/406"
        500:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/500"
        503:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/503"

    get:
      summary: Test the notification endpoint
      description: >
        This resource represents a notification endpoint. The server can use
        this resource to send notifications to a subscribed
        client, which has provided the URI of this resource during the subscription process.

        The GET method allows the server to test the notification endpoint
        that is provided by the client, e.g. during subscription.
        This method shall follow the provisions specified in the Table 5.4.10.3.2-2 for URI query parameters,
        request and response data structures, and response codes.
      parameters:
        - name: Accept
          description: >
            Content-Types that are acceptable for the response.
            Reference: IETF RFC 7231.
          in: header
          required: true
          type: string
      responses:
        204:
          description: >
            204 NO CONTENT

            The notification endpoint was tested successfully.
            The response body shall be empty.
          headers:
            WWW-Authenticate:
              type: string
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP request
                has provided an invalid authorization token.
              maximum: 1
              minimum: 0
            Version:
              description: >
                Version of the API used in the response.
              type: string
              maximum: 1
              minimum: 1
        400:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/400"
        401:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/401"
        403:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/403"
        404:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/404"
        405:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/405"
        406:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/406"
        500:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/500"
        503:
          $ref: "../NSDManagement/responses/SOL005_resp.yaml#/responses/503"
For faster browsing, not all history is shown. View entire blame