@mojaloop/api-snippets 17.2.4 → 17.3.0-snapshot.0

package/fspiop/v2_0/openapi3/paths/participants_Type_ID_SubId.yaml

@@ -0,0 +1,168 @@
+parameters:
+  - $ref: ../components/parameters/Type.yaml
+  - $ref: ../components/parameters/ID.yaml
+  - $ref: ../components/parameters/SubId.yaml
+  - $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: ParticipantsSubIdByTypeAndIDPost
+  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: ParticipantsSubIdByTypeAndID
+  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: ParticipantsSubIdByTypeAndID3
+  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: ParticipantsSubIdByTypeAndID2
+  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/fspiop/v2_0/openapi3/paths/participants_Type_ID_SubId_error.yaml

@@ -0,0 +1,50 @@
+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: ParticipantsSubIdErrorByTypeAndID
+  parameters:
+    - $ref: ../components/parameters/Type.yaml
+    - $ref: ../components/parameters/ID.yaml
+    - $ref: ../components/parameters/SubId.yaml
+    - $ref: ../components/parameters/Content-Length.yaml
+    - $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
+  requestBody:
+    description: Details of the error returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../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/fspiop/v2_0/openapi3/paths/participants_Type_ID_error.yaml

@@ -0,0 +1,49 @@
+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/Type.yaml
+    - $ref: ../components/parameters/ID.yaml
+    - $ref: ../components/parameters/Content-Length.yaml
+    - $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
+  requestBody:
+    description: Details of the error returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../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/fspiop/v2_0/openapi3/paths/parties_Type_ID.yaml

@@ -0,0 +1,81 @@
+parameters:
+  - $ref: ../components/parameters/Type.yaml
+  - $ref: ../components/parameters/ID.yaml
+  - $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:
+  description: >-
+    The HTTP request `GET /parties/{Type}/{ID}` (or `GET
+    /parties/{Type}/{ID}/{SubId}`) is used to look up information regarding the
+    requested Party, defined by `{Type}`, `{ID}` and optionally `{SubId}` (for
+    example, `GET /parties/MSISDN/123456789`, or `GET
+    /parties/BUSINESS/shoecompany/employee1`).
+  summary: Look up party information
+  tags:
+    - parties
+  operationId: PartiesByTypeAndID
+  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 /parties/{Type}/{ID}` (or `PUT
+    /parties/{Type}/{ID}/{SubId}`) is used to inform the client of a successful
+    result of the Party information lookup.
+  summary: Return party information
+  tags:
+    - parties
+  operationId: PartiesByTypeAndID2
+  parameters:
+    - $ref: ../components/parameters/Content-Length.yaml
+  requestBody:
+    description: Party information returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../components/schemas/PartiesTypeIDPutResponse.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/fspiop/v2_0/openapi3/paths/parties_Type_ID_SubId.yaml

@@ -0,0 +1,82 @@
+parameters:
+  - $ref: ../components/parameters/Type.yaml
+  - $ref: ../components/parameters/ID.yaml
+  - $ref: ../components/parameters/SubId.yaml
+  - $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:
+  description: >-
+    The HTTP request `GET /parties/{Type}/{ID}` (or `GET
+    /parties/{Type}/{ID}/{SubId}`) is used to look up information regarding the
+    requested Party, defined by `{Type}`, `{ID}` and optionally `{SubId}` (for
+    example, `GET /parties/MSISDN/123456789`, or `GET
+    /parties/BUSINESS/shoecompany/employee1`).
+  summary: Look up party information
+  tags:
+    - parties
+  operationId: PartiesSubIdByTypeAndID
+  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 /parties/{Type}/{ID}` (or `PUT
+    /parties/{Type}/{ID}/{SubId}`) is used to inform the client of a successful
+    result of the Party information lookup.
+  summary: Return party information
+  tags:
+    - parties
+  operationId: PartiesSubIdByTypeAndIDPut
+  parameters:
+    - $ref: ../components/parameters/Content-Length.yaml
+  requestBody:
+    description: Party information returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../components/schemas/PartiesTypeIDPutResponse.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/fspiop/v2_0/openapi3/paths/parties_Type_ID_SubId_error.yaml

@@ -0,0 +1,50 @@
+put:
+  description: >-
+    If the server is unable to find Party information of the provided identity,
+    or another processing error occurred, the error callback `PUT
+    /parties/{Type}/{ID}/error` (or `PUT /parties/{Type}/{ID}/{SubId}/error`) is
+    used.
+  summary: Return party information error
+  tags:
+    - parties
+  operationId: PartiesSubIdErrorByTypeAndID
+  parameters:
+    - $ref: ../components/parameters/Type.yaml
+    - $ref: ../components/parameters/ID.yaml
+    - $ref: ../components/parameters/SubId.yaml
+    - $ref: ../components/parameters/Content-Length.yaml
+    - $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
+  requestBody:
+    description: Details of the error returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../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/fspiop/v2_0/openapi3/paths/parties_Type_ID_error.yaml

@@ -0,0 +1,49 @@
+put:
+  description: >-
+    If the server is unable to find Party information of the provided identity,
+    or another processing error occurred, the error callback `PUT
+    /parties/{Type}/{ID}/error` (or `PUT /parties/{Type}/{ID}/{SubI}/error`) is
+    used.
+  summary: Return party information error
+  tags:
+    - parties
+  operationId: PartiesErrorByTypeAndID
+  parameters:
+    - $ref: ../components/parameters/Type.yaml
+    - $ref: ../components/parameters/ID.yaml
+    - $ref: ../components/parameters/Content-Length.yaml
+    - $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
+  requestBody:
+    description: Details of the error returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../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/fspiop/v2_0/openapi3/paths/quotes.yaml

@@ -0,0 +1,46 @@
+post:
+  description: >-
+    The HTTP request `POST /quotes` is used to request the creation of a quote
+    for the provided financial transaction in the server.
+  summary: Calculate quote
+  tags:
+    - quotes
+  operationId: Quotes
+  parameters:
+    - $ref: ../components/parameters/Accept.yaml
+    - $ref: ../components/parameters/Content-Length.yaml
+    - $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
+  requestBody:
+    description: Details of the quote to be created.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../components/schemas/QuotesPostRequest.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/fspiop/v2_0/openapi3/paths/quotes_ID.yaml

@@ -0,0 +1,79 @@
+parameters:
+  - $ref: ../components/parameters/ID.yaml
+  - $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:
+  description: >-
+    The HTTP request `GET /quotes/{ID}` is used to get information regarding a
+    quote created or requested earlier. The `{ID}` in the URI should contain the
+    `quoteId` that was used for the creation of the quote.
+  summary: Retrieve quote information
+  tags:
+    - quotes
+  operationId: QuotesByID
+  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 /quotes/{ID}` is used to inform the client of a requested
+    or created quote. The `{ID}` in the URI should contain the `quoteId` that
+    was used for the creation of the quote, or the `{ID}` that was used in the
+    `GET /quotes/{ID}` request.
+  summary: Return quote information
+  tags:
+    - quotes
+  operationId: QuotesByID1
+  parameters:
+    - $ref: ../components/parameters/Content-Length.yaml
+  requestBody:
+    description: Quote information returned.
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: ../components/schemas/QuotesIDPutResponse.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