@mojaloop/api-snippets 18.3.1 → 18.4.0

package/thirdparty/v2_0/openapi3/openapi-admin.yaml

@@ -0,0 +1,99 @@
+openapi: 3.0.2
+info:
+  version: '0.1'
+  title: Thirdparty Snippets
+  description: |
+    Based on sequence diagrams
+    (https://github.com/mojaloop/tpp/tree/main/docs/out).
+    This is a work in progress.
+  license:
+    name: TBD
+servers:
+  - url: '{protocol}://hostname:<port>/switch/'
+    variables:
+      protocol:
+        enum:
+          - http
+          - https
+        default: https
+paths:
+  /interface:
+    post:
+      description: >-
+        Essential path to include schema definitions that are not used so that
+        these definitions get included into the openapi-cli bundle api
+        definition so that they get converted into typescript definitions.
+      operationId: test
+      requestBody:
+        content:
+          application/json:
+            schema:
+              oneOf:
+                - $ref: './components/schemas/ParticipantsIDPutResponse.yaml'
+                - $ref: './components/schemas/PartiesTypeIDPutResponse.yaml'
+                - $ref: './components/schemas/QuotesIDPutResponse.yaml'
+                - $ref: './components/schemas/AuthorizationResponseType.yaml'
+                - $ref: './components/schemas/ConsentStatusIssued.yaml'
+                - $ref: './components/schemas/IlpFulfilment.yaml'
+                - $ref: './components/schemas/Integer.yaml'
+                - $ref: './components/schemas/Note.yaml'
+                - $ref: './components/schemas/PartyIdInfoTPLink.yaml'
+                - $ref: './components/schemas/PartyResult.yaml'
+                - $ref: './components/schemas/ServiceType.yaml'
+                - $ref: './components/schemas/ParticipantsPostRequest.yaml'
+                - $ref: './components/schemas/QuotesPostRequest.yaml'
+      responses:
+        200:
+          description: Ok
+  /tppAccountRequest:
+    $ref: paths/tppAccountRequest.yaml
+  /tppAccountRequest/{ID}:
+    $ref: paths/tppAccountRequest_ID.yaml
+  /tppAccountRequest/{ID}/error:
+    $ref: paths/tppAccountRequest_ID_error.yaml
+  /tppAccounts/{ID}:
+    $ref: paths/tppAccounts_ID.yaml
+  /tppAccounts/{ID}/error:
+    $ref: paths/tppAccounts_ID_error.yaml
+  /health:
+    $ref: paths/health.yaml
+  /metrics:
+    $ref: paths/metrics.yaml
+  /tppConsentRequests:
+    $ref: paths/tppConsentRequests.yaml
+  /tppConsentRequests/{ID}:
+    $ref: paths/tppConsentRequests_ID.yaml
+  /tppConsentRequests/{ID}/error:
+    $ref: paths/tppConsentRequests_ID_error.yaml
+  /tppConsents:
+    $ref: paths/tppConsents.yaml
+  /tppConsents/{ID}:
+    $ref: paths/tppConsents_ID.yaml
+  /tppConsents/{ID}/error:
+    $ref: paths/tppConsents_ID_error.yaml
+  /participants:
+    $ref: paths/participants.yaml
+  /participants/{ID}:
+    $ref: paths/participants_ID.yaml
+  /participants/{ID}/error:
+    $ref: paths/participants_ID_error.yaml
+  /participants/{Type}/{ID}:
+    $ref: paths/participants_Type_ID.yaml
+  /participants/{Type}/{ID}/error:
+    $ref: paths/participants_Type_ID_error.yaml
+  /services/{ServiceType}:
+    $ref: paths/services_ServiceType.yaml
+  /services/{ServiceType}/error:
+    $ref: paths/services_ServiceType_error.yaml
+  /tppAuthorizations:
+    $ref: paths/tppAuthorizations.yaml
+  /tppAuthorizations/{ID}:
+    $ref: paths/tppAuthorizations_ID.yaml
+  /tppAuthorizations/{ID}/error:
+    $ref: paths/tppAuthorizations_ID_error.yaml
+  /tppVerifications:
+    $ref: paths/tppVerifications.yaml
+  /tppVerifications/{ID}:
+    $ref: paths/tppVerifications_ID.yaml
+  /tppVerifications/{ID}/error:
+    $ref: paths/tppVerifications_ID_error.yaml

package/thirdparty/v2_0/openapi3/openapi.yaml

@@ -0,0 +1,64 @@
+openapi: 3.0.2
+info:
+  version: '2.0'
+  title: Thirdparty Snippets
+  description: |
+    Based on sequence diagrams
+    (https://github.com/mojaloop/tpp/tree/main/docs/out).
+    This is a work in progress.
+  license:
+    name: TBD
+servers:
+  - url: '{protocol}://hostname:<port>/switch/'
+    variables:
+      protocol:
+        enum:
+          - http
+          - https
+        default: https
+paths:
+  /interface:
+    post:
+      description: >-
+        Essential path to include schema definitions that are not used so that
+        these definitions get included into the openapi-cli bundle api
+        definition so that they get converted into typescript definitions.
+      operationId: test
+      requestBody:
+        content:
+          application/json:
+            schema:
+              oneOf:
+                - $ref: './components/schemas/ParticipantsIDPutResponse.yaml'
+                - $ref: './components/schemas/PartiesTypeIDPutResponse.yaml'
+                - $ref: './components/schemas/QuotesIDPutResponse.yaml'
+                - $ref: './components/schemas/AuthorizationResponseType.yaml'
+                - $ref: './components/schemas/ConsentStatusIssued.yaml'
+                - $ref: './components/schemas/IlpFulfilment.yaml'
+                - $ref: './components/schemas/Integer.yaml'
+                - $ref: './components/schemas/Note.yaml'
+                - $ref: './components/schemas/PartyIdInfoTPLink.yaml'
+                - $ref: './components/schemas/PartyResult.yaml'
+                - $ref: './components/schemas/ServiceType.yaml'
+                - $ref: './components/schemas/ParticipantsPostRequest.yaml'
+                - $ref: './components/schemas/QuotesPostRequest.yaml'
+      responses:
+        200:
+          description: Ok
+  /health:
+    $ref: paths/health.yaml
+  /metrics:
+    $ref: paths/metrics.yaml
+  /tppTransactionRequests:
+    $ref: paths/tppTransactionRequests.yaml
+  /tppTransactionRequests/{ID}:
+    $ref: paths/tppTransactionRequests_ID.yaml
+  /tppTransactionRequests/{ID}/error:
+    $ref: paths/tppTransactionRequests_ID_error.yaml
+  /tppTransfers:
+    $ref: paths/tppTransfers.yaml
+  /tppTransfers/{ID}:
+    $ref: paths/tppTransfers_ID.yaml
+  /tppTransfers/{ID}/error:
+    $ref: paths/tppTransfers_ID_error.yaml
+  

package/thirdparty/v2_0/openapi3/paths/health.yaml

@@ -0,0 +1,25 @@
+get:
+  tags:
+    - health
+  responses:
+    200:
+      $ref: ../components/responses/200.yaml
+    400:
+      $ref: ../components/responses/400.yaml
+    401:
+      $ref: ../components/responses/401.yaml
+    403:
+      $ref: ../components/responses/403.yaml
+    404:
+      $ref: ../components/responses/404.yaml
+    405:
+      $ref: ../components/responses/405.yaml
+    406:
+      $ref: ../components/responses/406.yaml
+    501:
+      $ref: ../components/responses/501.yaml
+    503:
+      $ref: ../components/responses/503.yaml
+  operationId: HealthGet
+  summary: Health check endpoint
+  description: The HTTP request GET /health is used to return the current status of the API.

package/thirdparty/v2_0/openapi3/paths/metrics.yaml

@@ -0,0 +1,25 @@
+get:
+  tags:
+    - health
+  responses:
+    200:
+      $ref: ../components/responses/200.yaml
+    400:
+      $ref: ../components/responses/400.yaml
+    401:
+      $ref: ../components/responses/401.yaml
+    403:
+      $ref: ../components/responses/403.yaml
+    404:
+      $ref: ../components/responses/404.yaml
+    405:
+      $ref: ../components/responses/405.yaml
+    406:
+      $ref: ../components/responses/406.yaml
+    501:
+      $ref: ../components/responses/501.yaml
+    503:
+      $ref: ../components/responses/503.yaml
+  operationId: MetricsGet
+  summary: Prometheus metrics endpoint
+  description: The HTTP request GET /metrics is used to return metrics for the API.

package/thirdparty/v2_0/openapi3/paths/participants.yaml

@@ -0,0 +1,50 @@
+parameters:
+  - $ref: ../components/parameters/Content-Type.yaml
+  - $ref: ../components/parameters/Date.yaml
+  - $ref: ../components/parameters/X-Forwarded-For.yaml
+  - $ref: ../components/parameters/FSPIOP-Source.yaml
+  - $ref: ../components/parameters/FSPIOP-Destination.yaml
+  - $ref: ../components/parameters/FSPIOP-Encryption.yaml
+  - $ref: ../components/parameters/FSPIOP-Signature.yaml
+  - $ref: ../components/parameters/FSPIOP-URI.yaml
+  - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
+post:
+  description: >-
+    The HTTP request `POST /participants` is used to create information in the
+    server regarding the provided list of identities. This request should be
+    used for bulk creation of FSP information for more than one Party. The
+    optional currency parameter should indicate that each provided Party
+    supports the currency.
+  summary: Create bulk participant information
+  tags:
+    - participants
+  operationId: Participants1
+  parameters:
+    - $ref: ../components/parameters/Accept.yaml
+    - $ref: ../components/parameters/Content-Length.yaml
+  requestBody:
+    description: Participant information to be created.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../components/schemas/ParticipantsPostRequest.yaml
+  responses:
+    '202':
+      $ref: ../components/responses/202.yaml
+    '400':
+      $ref: ../components/responses/400.yaml
+    '401':
+      $ref: ../components/responses/401.yaml
+    '403':
+      $ref: ../components/responses/403.yaml
+    '404':
+      $ref: ../components/responses/404.yaml
+    '405':
+      $ref: ../components/responses/405.yaml
+    '406':
+      $ref: ../components/responses/406.yaml
+    '501':
+      $ref: ../components/responses/501.yaml
+    '503':
+      $ref: ../components/responses/503.yaml

package/thirdparty/v2_0/openapi3/paths/participants_ID.yaml

@@ -0,0 +1,49 @@
+parameters:
+  #Path
+  - $ref: ../components/parameters/ID.yaml
+  #Headers
+  - $ref: ../components/parameters/Content-Type.yaml
+  - $ref: ../components/parameters/Date.yaml
+  - $ref: ../components/parameters/X-Forwarded-For.yaml
+  - $ref: ../components/parameters/FSPIOP-Source.yaml
+  - $ref: ../components/parameters/FSPIOP-Destination.yaml
+  - $ref: ../components/parameters/FSPIOP-Encryption.yaml
+  - $ref: ../components/parameters/FSPIOP-Signature.yaml
+  - $ref: ../components/parameters/FSPIOP-URI.yaml
+  - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
+put:
+  description: >-
+    The callback `PUT /participants/{ID}` is used to inform the client of the
+    result of the creation of the provided list of identities.
+  summary: Return bulk participant information
+  tags:
+    - participants
+  operationId: PutParticipantsByID
+  parameters:
+    - $ref: ../components/parameters/Content-Length.yaml
+  requestBody:
+    description: Participant information returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../components/schemas/ParticipantsIDPutResponse.yaml
+  responses:
+    '200':
+      $ref: ../components/responses/200.yaml
+    '400':
+      $ref: ../components/responses/400.yaml
+    '401':
+      $ref: ../components/responses/401.yaml
+    '403':
+      $ref: ../components/responses/403.yaml
+    '404':
+      $ref: ../components/responses/404.yaml
+    '405':
+      $ref: ../components/responses/405.yaml
+    '406':
+      $ref: ../components/responses/406.yaml
+    '501':
+      $ref: ../components/responses/501.yaml
+    '503':
+      $ref: ../components/responses/503.yaml

package/thirdparty/v2_0/openapi3/paths/participants_ID_error.yaml

@@ -0,0 +1,51 @@
+parameters:
+  #Path
+  - $ref: ../components/parameters/ID.yaml
+  #Headers
+  - $ref: ../components/parameters/Content-Type.yaml
+  - $ref: ../components/parameters/Date.yaml
+  - $ref: ../components/parameters/X-Forwarded-For.yaml
+  - $ref: ../components/parameters/FSPIOP-Source.yaml
+  - $ref: ../components/parameters/FSPIOP-Destination.yaml
+  - $ref: ../components/parameters/FSPIOP-Encryption.yaml
+  - $ref: ../components/parameters/FSPIOP-Signature.yaml
+  - $ref: ../components/parameters/FSPIOP-URI.yaml
+  - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
+put:
+  description: >-
+    If there is an error during FSP information creation in the server, the
+    error callback `PUT /participants/{ID}/error` is used. The `{ID}` in the URI
+    should contain the requestId that was used for the creation of the
+    participant information.
+  summary: Return bulk participant information error
+  tags:
+    - participants
+  operationId: PutParticipantsByIDAndError
+  parameters:
+    - $ref: ../components/parameters/Content-Length.yaml
+  requestBody:
+    description: Details of the error returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../../../../fspiop/v2_0/openapi3/components/schemas/ErrorInformationObject.yaml
+  responses:
+    '200':
+      $ref: ../components/responses/200.yaml
+    '400':
+      $ref: ../components/responses/400.yaml
+    '401':
+      $ref: ../components/responses/401.yaml
+    '403':
+      $ref: ../components/responses/403.yaml
+    '404':
+      $ref: ../components/responses/404.yaml
+    '405':
+      $ref: ../components/responses/405.yaml
+    '406':
+      $ref: ../components/responses/406.yaml
+    '501':
+      $ref: ../components/responses/501.yaml
+    '503':
+      $ref: ../components/responses/503.yaml

package/thirdparty/v2_0/openapi3/paths/participants_Type_ID.yaml

@@ -0,0 +1,169 @@
+parameters:
+  #Path
+  - $ref: ../components/parameters/Type.yaml
+  - $ref: ../components/parameters/ID.yaml
+  #Headers
+  - $ref: ../components/parameters/Content-Type.yaml
+  - $ref: ../components/parameters/Date.yaml
+  - $ref: ../components/parameters/X-Forwarded-For.yaml
+  - $ref: ../components/parameters/FSPIOP-Source.yaml
+  - $ref: ../components/parameters/FSPIOP-Destination.yaml
+  - $ref: ../components/parameters/FSPIOP-Encryption.yaml
+  - $ref: ../components/parameters/FSPIOP-Signature.yaml
+  - $ref: ../components/parameters/FSPIOP-URI.yaml
+  - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
+post:
+  description: >-
+    The HTTP request `POST /participants/{Type}/{ID}` (or `POST
+    /participants/{Type}/{ID}/{SubId}`) is used to create information in the
+    server regarding the provided identity, defined by `{Type}`, `{ID}`, and
+    optionally `{SubId}` (for example, `POST /participants/MSISDN/123456789` or
+    `POST /participants/BUSINESS/shoecompany/employee1`). An ExtensionList
+    element has been added to this reqeust in version v1.1
+  summary: Create participant information
+  tags:
+    - participants
+  operationId: ParticipantsByIDAndType
+  parameters:
+    - $ref: ../components/parameters/Accept.yaml
+    - $ref: ../components/parameters/Content-Length.yaml
+  requestBody:
+    description: Participant information to be created.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../components/schemas/ParticipantsTypeIDSubIDPostRequest.yaml
+  responses:
+    '202':
+      $ref: ../components/responses/202.yaml
+    '400':
+      $ref: ../components/responses/400.yaml
+    '401':
+      $ref: ../components/responses/401.yaml
+    '403':
+      $ref: ../components/responses/403.yaml
+    '404':
+      $ref: ../components/responses/404.yaml
+    '405':
+      $ref: ../components/responses/405.yaml
+    '406':
+      $ref: ../components/responses/406.yaml
+    '501':
+      $ref: ../components/responses/501.yaml
+    '503':
+      $ref: ../components/responses/503.yaml
+get:
+  description: >-
+    The HTTP request `GET /participants/{Type}/{ID}` (or `GET
+    /participants/{Type}/{ID}/{SubId}`) is used to find out in which FSP the
+    requested Party, defined by `{Type}`, `{ID}` and optionally `{SubId}`, is
+    located (for example, `GET /participants/MSISDN/123456789`, or `GET
+    /participants/BUSINESS/shoecompany/employee1`). This HTTP request should
+    support a query string for filtering of currency. To use filtering of
+    currency, the HTTP request `GET /participants/{Type}/{ID}?currency=XYZ`
+    should be used, where `XYZ` is the requested currency.
+  summary: Look up participant information
+  tags:
+    - participants
+  operationId: ParticipantsByTypeAndID
+  parameters:
+    - $ref: ../components/parameters/Accept.yaml
+  responses:
+    '202':
+      $ref: ../components/responses/202.yaml
+    '400':
+      $ref: ../components/responses/400.yaml
+    '401':
+      $ref: ../components/responses/401.yaml
+    '403':
+      $ref: ../components/responses/403.yaml
+    '404':
+      $ref: ../components/responses/404.yaml
+    '405':
+      $ref: ../components/responses/405.yaml
+    '406':
+      $ref: ../components/responses/406.yaml
+    '501':
+      $ref: ../components/responses/501.yaml
+    '503':
+      $ref: ../components/responses/503.yaml
+put:
+  description: >-
+    The callback `PUT /participants/{Type}/{ID}` (or `PUT
+    /participants/{Type}/{ID}/{SubId}`) is used to inform the client of a
+    successful result of the lookup, creation, or deletion of the FSP
+    information related to the Party. If the FSP information is deleted, the
+    fspId element should be empty; otherwise the element should include the FSP
+    information for the Party.
+  summary: Return participant information
+  tags:
+    - participants
+  operationId: ParticipantsByTypeAndID3
+  parameters:
+    - $ref: ../components/parameters/Content-Length.yaml
+  requestBody:
+    description: Participant information returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../components/schemas/ParticipantsTypeIDPutResponse.yaml
+  responses:
+    '200':
+      $ref: ../components/responses/200.yaml
+    '400':
+      $ref: ../components/responses/400.yaml
+    '401':
+      $ref: ../components/responses/401.yaml
+    '403':
+      $ref: ../components/responses/403.yaml
+    '404':
+      $ref: ../components/responses/404.yaml
+    '405':
+      $ref: ../components/responses/405.yaml
+    '406':
+      $ref: ../components/responses/406.yaml
+    '501':
+      $ref: ../components/responses/501.yaml
+    '503':
+      $ref: ../components/responses/503.yaml
+delete:
+  description: >-
+    The HTTP request `DELETE /participants/{Type}/{ID}` (or `DELETE
+    /participants/{Type}/{ID}/{SubId}`) is used to delete information in the
+    server regarding the provided identity, defined by `{Type}` and `{ID}`) (for
+    example, `DELETE /participants/MSISDN/123456789`), and optionally `{SubId}`.
+    This HTTP request should support a query string to delete FSP information
+    regarding a specific currency only. To delete a specific currency only, the
+    HTTP request `DELETE /participants/{Type}/{ID}?currency=XYZ` should be used,
+    where `XYZ` is the requested currency.
+
+
+    **Note:** The Account Lookup System should verify that it is the Party’s
+    current FSP that is deleting the FSP information.
+  summary: Delete participant information
+  tags:
+    - participants
+  operationId: ParticipantsByTypeAndID2
+  parameters:
+    - $ref: ../components/parameters/Accept.yaml
+  responses:
+    '202':
+      $ref: ../components/responses/202.yaml
+    '400':
+      $ref: ../components/responses/400.yaml
+    '401':
+      $ref: ../components/responses/401.yaml
+    '403':
+      $ref: ../components/responses/403.yaml
+    '404':
+      $ref: ../components/responses/404.yaml
+    '405':
+      $ref: ../components/responses/405.yaml
+    '406':
+      $ref: ../components/responses/406.yaml
+    '501':
+      $ref: ../components/responses/501.yaml
+    '503':
+      $ref: ../components/responses/503.yaml

package/thirdparty/v2_0/openapi3/paths/participants_Type_ID_error.yaml

@@ -0,0 +1,52 @@
+parameters:
+  #Path
+  - $ref: ../components/parameters/Type.yaml
+  - $ref: ../components/parameters/ID.yaml
+  #Headers
+  - $ref: ../components/parameters/Content-Type.yaml
+  - $ref: ../components/parameters/Date.yaml
+  - $ref: ../components/parameters/X-Forwarded-For.yaml
+  - $ref: ../components/parameters/FSPIOP-Source.yaml
+  - $ref: ../components/parameters/FSPIOP-Destination.yaml
+  - $ref: ../components/parameters/FSPIOP-Encryption.yaml
+  - $ref: ../components/parameters/FSPIOP-Signature.yaml
+  - $ref: ../components/parameters/FSPIOP-URI.yaml
+  - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
+put:
+  description: >-
+    If the server is unable to find, create or delete the associated FSP of the
+    provided identity, or another processing error occurred, the error callback
+    `PUT /participants/{Type}/{ID}/error` (or `PUT
+    /participants/{Type}/{ID}/{SubId}/error`) is used.
+  summary: Return participant information error
+  tags:
+    - participants
+  operationId: ParticipantsErrorByTypeAndID
+  parameters:
+    - $ref: ../components/parameters/Content-Length.yaml
+  requestBody:
+    description: Details of the error returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../../../../fspiop/v2_0/openapi3/components/schemas/ErrorInformationObject.yaml
+  responses:
+    '200':
+      $ref: ../components/responses/200.yaml
+    '400':
+      $ref: ../components/responses/400.yaml
+    '401':
+      $ref: ../components/responses/401.yaml
+    '403':
+      $ref: ../components/responses/403.yaml
+    '404':
+      $ref: ../components/responses/404.yaml
+    '405':
+      $ref: ../components/responses/405.yaml
+    '406':
+      $ref: ../components/responses/406.yaml
+    '501':
+      $ref: ../components/responses/501.yaml
+    '503':
+      $ref: ../components/responses/503.yaml

package/thirdparty/v2_0/openapi3/paths/services_ServiceType.yaml

@@ -0,0 +1,77 @@
+parameters:
+  #Path
+  - $ref: ../components/parameters/ServiceType.yaml
+  #Headers
+  - $ref: ../components/parameters/Content-Type.yaml
+  - $ref: ../components/parameters/Date.yaml
+  - $ref: ../components/parameters/X-Forwarded-For.yaml
+  - $ref: ../components/parameters/FSPIOP-Source.yaml
+  - $ref: ../components/parameters/FSPIOP-Destination.yaml
+  - $ref: ../components/parameters/FSPIOP-Encryption.yaml
+  - $ref: ../components/parameters/FSPIOP-Signature.yaml
+  - $ref: ../components/parameters/FSPIOP-URI.yaml
+  - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
+get:
+  operationId: GetServicesByServiceType
+  summary: GetServicesByServiceType
+  description: |
+    The HTTP request `GET /services/{ServiceType}` is used to retrieve the list of participants
+    that support a specified service.
+  parameters:
+    - $ref: ../components/parameters/Accept.yaml
+  tags:
+    - services
+  responses:
+    202:
+      $ref: ../components/responses/202.yaml
+    400:
+      $ref: ../components/responses/400.yaml
+    401:
+      $ref: ../components/responses/401.yaml
+    403:
+      $ref: ../components/responses/403.yaml
+    404:
+      $ref: ../components/responses/404.yaml
+    405:
+      $ref: ../components/responses/405.yaml
+    406:
+      $ref: ../components/responses/406.yaml
+    501:
+      $ref: ../components/responses/501.yaml
+    503:
+      $ref: ../components/responses/503.yaml
+put:
+  description: |
+    The HTTP request `PUT /services/{ServiceType}` is used to return list of participants
+    that support a specified service.
+  operationId: PutServicesByServiceType
+  summary: PutServicesByServiceType
+  tags:
+    - services
+  parameters:
+    - $ref: ../components/parameters/Content-Length.yaml
+  requestBody:
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../components/schemas/ServicesServiceTypePutResponse.yaml
+  responses:
+    200:
+      $ref: ../components/responses/200.yaml
+    400:
+      $ref: ../components/responses/400.yaml
+    401:
+      $ref: ../components/responses/401.yaml
+    403:
+      $ref: ../components/responses/403.yaml
+    404:
+      $ref: ../components/responses/404.yaml
+    405:
+      $ref: ../components/responses/405.yaml
+    406:
+      $ref: ../components/responses/406.yaml
+    501:
+      $ref: ../components/responses/501.yaml
+    503:
+      $ref: ../components/responses/503.yaml