@mojaloop/api-snippets 17.2.0 → 17.2.4

package/lib/fspiop/v1_0/openapi.d.ts

@@ -4,300 +4,288 @@
  */
 export interface paths {
     "/interface": {
-        /** Essential path to include schema components 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. */
+        /** @description Essential path to include schema components 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. */
         post: operations["Interface"];
     };
     "/participants/{Type}/{ID}": {
-        /** 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. */
+        /**
+         * Look up participant information
+         * @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.
+         */
         get: operations["ParticipantsByTypeAndID"];
-        /** 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. */
+        /**
+         * Return participant information
+         * @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.
+         */
         put: operations["ParticipantsByTypeAndID3"];
-        /** 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`). */
+        /**
+         * Create participant information
+         * @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`).
+         */
         post: operations["ParticipantsByIDAndType"];
         /**
-         * 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.
+         * Delete participant information
+         * @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.
          */
         delete: operations["ParticipantsByTypeAndID2"];
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+            };
         };
     };
     "/participants/{Type}/{ID}/error": {
-        /** 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. */
+        /**
+         * Return participant information error
+         * @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.
+         */
         put: operations["ParticipantsErrorByTypeAndID"];
     };
     "/participants/{Type}/{ID}/{SubId}": {
-        /** 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. */
+        /**
+         * Look up participant information
+         * @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.
+         */
         get: operations["ParticipantsSubIdByTypeAndID"];
-        /** 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. */
+        /**
+         * Return participant information
+         * @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.
+         */
         put: operations["ParticipantsSubIdByTypeAndID3"];
-        /** 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`). */
+        /**
+         * Create participant information
+         * @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`).
+         */
         post: operations["ParticipantsSubIdByTypeAndIDPost"];
         /**
-         * 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.
+         * Delete participant information
+         * @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.
          */
         delete: operations["ParticipantsSubIdByTypeAndID2"];
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-                /** A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
-                SubId: components["parameters"]["SubId"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+                SubId: components["parameters"]["SubId"];
+            };
         };
     };
     "/participants/{Type}/{ID}/{SubId}/error": {
-        /** 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. */
+        /**
+         * Return participant information error
+         * @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.
+         */
         put: operations["ParticipantsSubIdErrorByTypeAndID"];
     };
     "/participants": {
-        /** 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. */
+        /**
+         * Create bulk participant information
+         * @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.
+         */
         post: operations["Participants1"];
     };
     "/participants/{ID}": {
-        /** The callback `PUT /participants/{ID}` is used to inform the client of the result of the creation of the provided list of identities. */
+        /**
+         * Return bulk participant information
+         * @description The callback `PUT /participants/{ID}` is used to inform the client of the result of the creation of the provided list of identities.
+         */
         put: operations["putParticipantsByID"];
     };
     "/participants/{ID}/error": {
-        /** 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. */
+        /**
+         * Return bulk participant information error
+         * @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.
+         */
         put: operations["ParticipantsByIDAndError"];
     };
     "/parties/{Type}/{ID}": {
-        /** 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`). */
+        /**
+         * Look up party information
+         * @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`).
+         */
         get: operations["PartiesByTypeAndID"];
-        /** 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. */
+        /**
+         * Return party information
+         * @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.
+         */
         put: operations["PartiesByTypeAndID2"];
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+            };
         };
     };
     "/parties/{Type}/{ID}/error": {
-        /** 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. */
+        /**
+         * Return party information error
+         * @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.
+         */
         put: operations["PartiesErrorByTypeAndID"];
     };
     "/parties/{Type}/{ID}/{SubId}": {
-        /** 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`). */
+        /**
+         * Look up party information
+         * @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`).
+         */
         get: operations["PartiesSubIdByTypeAndID"];
-        /** 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. */
+        /**
+         * Return party information
+         * @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.
+         */
         put: operations["PartiesSubIdByTypeAndIDPut"];
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-                /** A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
-                SubId: components["parameters"]["SubId"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+                SubId: components["parameters"]["SubId"];
+            };
         };
     };
     "/parties/{Type}/{ID}/{SubId}/error": {
-        /** 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. */
+        /**
+         * Return party information error
+         * @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.
+         */
         put: operations["PartiesSubIdErrorByTypeAndID"];
     };
     "/transactionRequests": {
-        /** The HTTP request `POST /transactionRequests` is used to request the creation of a transaction request for the provided financial transaction in the server. */
+        /**
+         * Perform transaction request
+         * @description The HTTP request `POST /transactionRequests` is used to request the creation of a transaction request for the provided financial transaction in the server.
+         */
         post: operations["TransactionRequests"];
     };
     "/transactionRequests/{ID}": {
-        /** The HTTP request `GET /transactionRequests/{ID}` is used to get information regarding a transaction request created or requested earlier. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request. */
+        /**
+         * Retrieve transaction request information
+         * @description The HTTP request `GET /transactionRequests/{ID}` is used to get information regarding a transaction request created or requested earlier. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request.
+         */
         get: operations["TransactionRequestsByID"];
-        /** The callback `PUT /transactionRequests/{ID}` is used to inform the client of a requested or created transaction request. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request, or the `{ID}` that was used in the `GET /transactionRequests/{ID}`. */
+        /**
+         * Return transaction request information
+         * @description The callback `PUT /transactionRequests/{ID}` is used to inform the client of a requested or created transaction request. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request, or the `{ID}` that was used in the `GET /transactionRequests/{ID}`.
+         */
         put: operations["TransactionRequestsByIDPut"];
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
     };
     "/transactionRequests/{ID}/error": {
-        /** If the server is unable to find or create a transaction request, or another processing error occurs, the error callback `PUT /transactionRequests/{ID}/error` is used. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request, or the `{ID}` that was used in the `GET /transactionRequests/{ID}`. */
+        /**
+         * Return transaction request information error
+         * @description If the server is unable to find or create a transaction request, or another processing error occurs, the error callback `PUT /transactionRequests/{ID}/error` is used. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request, or the `{ID}` that was used in the `GET /transactionRequests/{ID}`.
+         */
         put: operations["TransactionRequestsErrorByID"];
     };
     "/quotes": {
-        /** The HTTP request `POST /quotes` is used to request the creation of a quote for the provided financial transaction in the server. */
+        /**
+         * Calculate quote
+         * @description The HTTP request `POST /quotes` is used to request the creation of a quote for the provided financial transaction in the server.
+         */
         post: operations["Quotes"];
     };
     "/quotes/{ID}": {
-        /** 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. */
+        /**
+         * Retrieve quote information
+         * @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.
+         */
         get: operations["QuotesByID"];
-        /** 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. */
+        /**
+         * Return quote information
+         * @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.
+         */
         put: operations["QuotesByID1"];
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
     };
     "/quotes/{ID}/error": {
-        /** If the server is unable to find or create a quote, or some other processing error occurs, the error callback `PUT /quotes/{ID}/error` is used. 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. */
+        /**
+         * Return quote information error
+         * @description If the server is unable to find or create a quote, or some other processing error occurs, the error callback `PUT /quotes/{ID}/error` is used. 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.
+         */
         put: operations["QuotesByIDAndError"];
     };
     "/authorizations/{ID}": {
         /**
-         * The HTTP request `GET /authorizations/{ID}` is used to request the Payer to enter the applicable credentials in the Payee FSP system. The `{ID}` in the URI should contain the `transactionRequestID`, received from the `POST /transactionRequests` service earlier in the process. This request requires a query string to be included in the URI, with the following key-value pairs*:*
+         * Perform authorization
+         * @description The HTTP request `GET /authorizations/{ID}` is used to request the Payer to enter the applicable credentials in the Payee FSP system. The `{ID}` in the URI should contain the `transactionRequestID`, received from the `POST /transactionRequests` service earlier in the process. This request requires a query string to be included in the URI, with the following key-value pairs*:*
          *
          * - `authenticationType={Type}`, where `{Type}` value is a valid authentication type from the enumeration `AuthenticationType`.
          *
@@ -312,216 +300,198 @@ export interface paths {
          * `GET /authorization/3d492671-b7af-4f3f-88de-76169b1bdf88?authenticationType=OTP&retriesLeft=2&amount=102&currency=USD`
          */
         get: operations["AuthorizationsByIDGet"];
-        /** The callback `PUT /authorizations/{ID}` is used to inform the client of the result of a previously-requested authorization. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /authorizations/{ID}` request. */
+        /**
+         * Return authorization result
+         * @description The callback `PUT /authorizations/{ID}` is used to inform the client of the result of a previously-requested authorization. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /authorizations/{ID}` request.
+         */
         put: operations["AuthorizationsByIDPut"];
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
     };
     "/authorizations/{ID}/error": {
-        /** If the server is unable to find the transaction request, or another processing error occurs, the error callback `PUT /authorizations/{ID}/error` is used. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /authorizations/{ID}`. */
+        /**
+         * Return authorization error
+         * @description If the server is unable to find the transaction request, or another processing error occurs, the error callback `PUT /authorizations/{ID}/error` is used. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /authorizations/{ID}`.
+         */
         put: operations["AuthorizationsByIDAndError"];
     };
     "/transfers": {
-        /** The HTTP request `POST /transfers` is used to request the creation of a transfer for the next ledger, and a financial transaction for the Payee FSP. */
+        /**
+         * Perform transfer
+         * @description The HTTP request `POST /transfers` is used to request the creation of a transfer for the next ledger, and a financial transaction for the Payee FSP.
+         */
         post: operations["transfers"];
     };
     "/transfers/{ID}": {
-        /** The HTTP request `GET /transfers/{ID}` is used to get information regarding a transfer created or requested earlier. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer. */
+        /**
+         * Retrieve transfer information
+         * @description The HTTP request `GET /transfers/{ID}` is used to get information regarding a transfer created or requested earlier. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer.
+         */
         get: operations["TransfersByIDGet"];
-        /** The callback `PUT /transfers/{ID}` is used to inform the client of a requested or created transfer. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer, or the `{ID}` that was used in the `GET /transfers/{ID}` request. */
+        /**
+         * Return transfer information
+         * @description The callback `PUT /transfers/{ID}` is used to inform the client of a requested or created transfer. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer, or the `{ID}` that was used in the `GET /transfers/{ID}` request.
+         */
         put: operations["TransfersByIDPut"];
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
     };
     "/transfers/{ID}/error": {
-        /** If the server is unable to find or create a transfer, or another processing error occurs, the error callback `PUT /transfers/{ID}/error` is used. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer, or the `{ID}` that was used in the `GET /transfers/{ID}`. */
+        /**
+         * Return transfer information error
+         * @description If the server is unable to find or create a transfer, or another processing error occurs, the error callback `PUT /transfers/{ID}/error` is used. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer, or the `{ID}` that was used in the `GET /transfers/{ID}`.
+         */
         put: operations["TransfersByIDAndError"];
     };
     "/transactions/{ID}": {
-        /** The HTTP request `GET /transactions/{ID}` is used to get transaction information regarding a financial transaction created earlier. The `{ID}` in the URI should contain the `transactionId` that was used for the creation of the quote, as the transaction is created as part of another process (the transfer process). */
+        /**
+         * Retrieve transaction information
+         * @description The HTTP request `GET /transactions/{ID}` is used to get transaction information regarding a financial transaction created earlier. The `{ID}` in the URI should contain the `transactionId` that was used for the creation of the quote, as the transaction is created as part of another process (the transfer process).
+         */
         get: operations["TransactionsByID"];
-        /** The callback `PUT /transactions/{ID}` is used to inform the client of a requested transaction. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /transactions/{ID}` request. */
+        /**
+         * Return transaction information
+         * @description The callback `PUT /transactions/{ID}` is used to inform the client of a requested transaction. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /transactions/{ID}` request.
+         */
         put: operations["TransactionsByID1"];
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
     };
     "/transactions/{ID}/error": {
-        /** If the server is unable to find or create a transaction, or another processing error occurs, the error callback `PUT /transactions/{ID}/error` is used. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /transactions/{ID}` request. */
+        /**
+         * Return transaction information error
+         * @description If the server is unable to find or create a transaction, or another processing error occurs, the error callback `PUT /transactions/{ID}/error` is used. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /transactions/{ID}` request.
+         */
         put: operations["TransactionsErrorByID"];
     };
     "/bulkQuotes": {
-        /** The HTTP request `POST /bulkQuotes` is used to request the creation of a bulk quote for the provided financial transactions in the server. */
+        /**
+         * Calculate bulk quote
+         * @description The HTTP request `POST /bulkQuotes` is used to request the creation of a bulk quote for the provided financial transactions in the server.
+         */
         post: operations["BulkQuotes"];
     };
     "/bulkQuotes/{ID}": {
-        /** The HTTP request `GET /bulkQuotes/{ID}` is used to get information regarding a bulk quote created or requested earlier. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote. */
+        /**
+         * Retrieve bulk quote information
+         * @description The HTTP request `GET /bulkQuotes/{ID}` is used to get information regarding a bulk quote created or requested earlier. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote.
+         */
         get: operations["BulkQuotesByID"];
-        /** The callback `PUT /bulkQuotes/{ID}` is used to inform the client of a requested or created bulk quote. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote, or the `{ID}` that was used in the `GET /bulkQuotes/{ID}` request. */
+        /**
+         * Return bulk quote information
+         * @description The callback `PUT /bulkQuotes/{ID}` is used to inform the client of a requested or created bulk quote. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote, or the `{ID}` that was used in the `GET /bulkQuotes/{ID}` request.
+         */
         put: operations["BulkQuotesByID1"];
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
     };
     "/bulkQuotes/{ID}/error": {
-        /** If the server is unable to find or create a bulk quote, or another processing error occurs, the error callback `PUT /bulkQuotes/{ID}/error` is used. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote, or the `{ID}` that was used in the `GET /bulkQuotes/{ID}` request. */
+        /**
+         * Return bulk quote information error
+         * @description If the server is unable to find or create a bulk quote, or another processing error occurs, the error callback `PUT /bulkQuotes/{ID}/error` is used. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote, or the `{ID}` that was used in the `GET /bulkQuotes/{ID}` request.
+         */
         put: operations["BulkQuotesErrorByID"];
     };
     "/bulkTransfers": {
-        /** The HTTP request `POST /bulkTransfers` is used to request the creation of a bulk transfer in the server. */
+        /**
+         * Perform bulk transfer
+         * @description The HTTP request `POST /bulkTransfers` is used to request the creation of a bulk transfer in the server.
+         */
         post: operations["BulkTransfers"];
     };
     "/bulkTransfers/{ID}": {
-        /** The HTTP request `GET /bulkTransfers/{ID}` is used to get information regarding a bulk transfer created or requested earlier. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer. */
+        /**
+         * Retrieve bulk transfer information
+         * @description The HTTP request `GET /bulkTransfers/{ID}` is used to get information regarding a bulk transfer created or requested earlier. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer.
+         */
         get: operations["BulkTransferByID"];
-        /** The callback `PUT /bulkTransfers/{ID}` is used to inform the client of a requested or created bulk transfer. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer (`POST /bulkTransfers`), or the `{ID}` that was used in the `GET /bulkTransfers/{ID}` request. */
+        /**
+         * Return bulk transfer information
+         * @description The callback `PUT /bulkTransfers/{ID}` is used to inform the client of a requested or created bulk transfer. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer (`POST /bulkTransfers`), or the `{ID}` that was used in the `GET /bulkTransfers/{ID}` request.
+         */
         put: operations["BulkTransfersByIDPut"];
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
     };
     "/bulkTransfers/{ID}/error": {
-        /** If the server is unable to find or create a bulk transfer, or another processing error occurs, the error callback `PUT /bulkTransfers/{ID}/error` is used. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer (`POST /bulkTransfers`), or the `{ID}` that was used in the `GET /bulkTransfers/{ID}` request. */
+        /**
+         * Return bulk transfer information error
+         * @description If the server is unable to find or create a bulk transfer, or another processing error occurs, the error callback `PUT /bulkTransfers/{ID}/error` is used. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer (`POST /bulkTransfers`), or the `{ID}` that was used in the `GET /bulkTransfers/{ID}` request.
+         */
         put: operations["BulkTransfersErrorByID"];
     };
 }
+export type webhooks = Record<string, never>;
 export interface components {
     schemas: {
         /**
@@ -1866,62 +1836,90 @@ export interface components {
         };
     };
     responses: {
-        /** OK */
-        200: unknown;
-        /** Accepted */
-        202: unknown;
-        /** Bad Request */
+        /** @description OK */
+        200: {
+            content: never;
+        };
+        /** @description Accepted */
+        202: {
+            content: never;
+        };
+        /** @description Bad Request */
         400: {
-            headers: {};
+            headers: {
+                "Content-Length": components["headers"]["Content-Length"];
+                "Content-Type": components["headers"]["Content-Type"];
+            };
             content: {
                 "application/json": components["schemas"]["ErrorInformationResponse"];
             };
         };
-        /** Unauthorized */
+        /** @description Unauthorized */
         401: {
-            headers: {};
+            headers: {
+                "Content-Length": components["headers"]["Content-Length"];
+                "Content-Type": components["headers"]["Content-Type"];
+            };
             content: {
                 "application/json": components["schemas"]["ErrorInformationResponse"];
             };
         };
-        /** Forbidden */
+        /** @description Forbidden */
         403: {
-            headers: {};
+            headers: {
+                "Content-Length": components["headers"]["Content-Length"];
+                "Content-Type": components["headers"]["Content-Type"];
+            };
             content: {
                 "application/json": components["schemas"]["ErrorInformationResponse"];
             };
         };
-        /** Not Found */
+        /** @description Not Found */
         404: {
-            headers: {};
+            headers: {
+                "Content-Length": components["headers"]["Content-Length"];
+                "Content-Type": components["headers"]["Content-Type"];
+            };
             content: {
                 "application/json": components["schemas"]["ErrorInformationResponse"];
             };
         };
-        /** Method Not Allowed */
+        /** @description Method Not Allowed */
         405: {
-            headers: {};
+            headers: {
+                "Content-Length": components["headers"]["Content-Length"];
+                "Content-Type": components["headers"]["Content-Type"];
+            };
             content: {
                 "application/json": components["schemas"]["ErrorInformationResponse"];
             };
         };
-        /** Not Acceptable */
+        /** @description Not Acceptable */
         406: {
-            headers: {};
+            headers: {
+                "Content-Length": components["headers"]["Content-Length"];
+                "Content-Type": components["headers"]["Content-Type"];
+            };
             content: {
                 "application/json": components["schemas"]["ErrorInformationResponse"];
             };
         };
-        /** Not Implemented */
+        /** @description Not Implemented */
         501: {
-            headers: {};
+            headers: {
+                "Content-Length": components["headers"]["Content-Length"];
+                "Content-Type": components["headers"]["Content-Type"];
+            };
             content: {
                 "application/json": components["schemas"]["ErrorInformationResponse"];
             };
         };
-        /** Service Unavailable */
+        /** @description Service Unavailable */
         503: {
-            headers: {};
+            headers: {
+                "Content-Length": components["headers"]["Content-Length"];
+                "Content-Type": components["headers"]["Content-Type"];
+            };
             content: {
                 "application/json": components["schemas"]["ErrorInformationResponse"];
             };
@@ -1941,19 +1939,19 @@ export interface components {
          *
          * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
          */
-        "X-Forwarded-For": string;
+        "X-Forwarded-For"?: string;
         /** @description The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
         "FSPIOP-Source": string;
         /** @description The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
-        "FSPIOP-Destination": string;
+        "FSPIOP-Destination"?: string;
         /** @description The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
-        "FSPIOP-Encryption": string;
+        "FSPIOP-Encryption"?: string;
         /** @description The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
-        "FSPIOP-Signature": string;
+        "FSPIOP-Signature"?: string;
         /** @description The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
-        "FSPIOP-URI": string;
+        "FSPIOP-URI"?: string;
         /** @description The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
-        "FSPIOP-HTTP-Method": string;
+        "FSPIOP-HTTP-Method"?: string;
         /** @description The `Accept` header field indicates the version of the API the client would like the server to use. */
         Accept: string;
         /**
@@ -1961,69 +1959,62 @@ export interface components {
          *
          * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
          */
-        "Content-Length": number;
+        "Content-Length"?: number;
         /** @description A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
         SubId: string;
     };
+    requestBodies: never;
     headers: {
         /**
-         * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
+         * @description The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
          *
          * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
          */
-        "Content-Length"?: number;
-        /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
+        "Content-Length": number;
+        /** @description The `Content-Type` header indicates the specific version of the API used to send the payload body. */
         "Content-Type": string;
     };
+    pathItems: never;
 }
+export type $defs = Record<string, never>;
+export type external = Record<string, never>;
 export interface operations {
-    /** Essential path to include schema components 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. */
+    /** @description Essential path to include schema components 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. */
     Interface: {
-        responses: {
-            /** Ok */
-            200: unknown;
-        };
-        requestBody: {
+        requestBody?: {
             content: {
                 "application/json": components["schemas"]["Amount"] | components["schemas"]["AmountType"] | components["schemas"]["AuthenticationInfo"] | components["schemas"]["AuthenticationType"] | components["schemas"]["AuthenticationValue"] | components["schemas"]["AuthorizationResponse"] | components["schemas"]["BalanceOfPayments"] | components["schemas"]["BinaryString"] | components["schemas"]["BinaryString32"] | components["schemas"]["BulkTransferState"] | components["schemas"]["Code"] | components["schemas"]["CorrelationId"] | components["schemas"]["Currency"] | components["schemas"]["Date"] | components["schemas"]["DateOfBirth"] | components["schemas"]["DateTime"] | components["schemas"]["ErrorCode"] | components["schemas"]["ErrorDescription"] | components["schemas"]["ExtensionKey"] | components["schemas"]["ExtensionValue"] | components["schemas"]["FirstName"] | components["schemas"]["FspId"] | components["schemas"]["IlpCondition"] | components["schemas"]["IlpFulfilment"] | components["schemas"]["IlpPacket"] | components["schemas"]["IndividualQuote"] | components["schemas"]["Integer"] | components["schemas"]["LastName"] | components["schemas"]["Latitude"] | components["schemas"]["Longitude"] | components["schemas"]["MerchantClassificationCode"] | components["schemas"]["MiddleName"] | components["schemas"]["Name"] | components["schemas"]["Note"] | components["schemas"]["OtpValue"] | components["schemas"]["PartyIdentifier"] | components["schemas"]["PartyIdType"] | components["schemas"]["PartyName"] | components["schemas"]["PartySubIdOrType"] | components["schemas"]["PersonalIdentifierType"] | components["schemas"]["RefundReason"] | components["schemas"]["QRCODE"] | components["schemas"]["TokenCode"] | components["schemas"]["Transaction"] | components["schemas"]["TransactionInitiator"] | components["schemas"]["TransactionInitiatorType"] | components["schemas"]["TransactionRequestState"] | components["schemas"]["TransactionScenario"] | components["schemas"]["TransactionState"] | components["schemas"]["TransactionSubScenario"] | components["schemas"]["TransferState"] | components["schemas"]["UndefinedEnum"];
             };
         };
+        responses: {
+            /** @description Ok */
+            200: {
+                content: never;
+            };
+        };
     };
-    /** 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. */
+    /**
+     * Look up participant information
+     * @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.
+     */
     ParticipantsByTypeAndID: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -2037,45 +2028,34 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** 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. */
+    /**
+     * Return participant information
+     * @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.
+     */
     ParticipantsByTypeAndID3: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Participant information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ParticipantsTypeIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2088,54 +2068,36 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Participant information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ParticipantsTypeIDPutResponse"];
-            };
-        };
     };
-    /** 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`). */
+    /**
+     * Create participant information
+     * @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`).
+     */
     ParticipantsByIDAndType: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Participant information to be created. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ParticipantsTypeIDSubIDPostRequest"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -2148,52 +2110,31 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Participant information to be created. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ParticipantsTypeIDSubIDPostRequest"];
-            };
-        };
     };
     /**
-     * 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.
+     * Delete participant information
+     * @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.
      */
     ParticipantsByTypeAndID2: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -2207,45 +2148,34 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** 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. */
+    /**
+     * Return participant information error
+     * @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.
+     */
     ParticipantsErrorByTypeAndID: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2258,50 +2188,30 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** 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. */
+    /**
+     * Look up participant information
+     * @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.
+     */
     ParticipantsSubIdByTypeAndID: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-                /** A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
-                SubId: components["parameters"]["SubId"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+                SubId: components["parameters"]["SubId"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -2315,47 +2225,35 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** 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. */
+    /**
+     * Return participant information
+     * @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.
+     */
     ParticipantsSubIdByTypeAndID3: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-                /** A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
-                SubId: components["parameters"]["SubId"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+                SubId: components["parameters"]["SubId"];
+            };
+        };
+        /** @description Participant information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ParticipantsTypeIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2368,56 +2266,37 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Participant information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ParticipantsTypeIDPutResponse"];
-            };
-        };
     };
-    /** 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`). */
+    /**
+     * Create participant information
+     * @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`).
+     */
     ParticipantsSubIdByTypeAndIDPost: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-                /** A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
-                SubId: components["parameters"]["SubId"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+                SubId: components["parameters"]["SubId"];
+            };
+        };
+        /** @description Participant information to be created. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ParticipantsTypeIDSubIDPostRequest"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -2430,54 +2309,32 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Participant information to be created. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ParticipantsTypeIDSubIDPostRequest"];
-            };
-        };
     };
     /**
-     * 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.
+     * Delete participant information
+     * @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.
      */
     ParticipantsSubIdByTypeAndID2: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-                /** A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
-                SubId: components["parameters"]["SubId"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+                SubId: components["parameters"]["SubId"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -2491,47 +2348,35 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** 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. */
+    /**
+     * Return participant information error
+     * @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.
+     */
     ParticipantsSubIdErrorByTypeAndID: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-                /** A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
-                SubId: components["parameters"]["SubId"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+                SubId: components["parameters"]["SubId"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2544,49 +2389,33 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** 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. */
+    /**
+     * Create bulk participant information
+     * @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.
+     */
     Participants1: {
         parameters: {
             header: {
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
         };
+        /** @description Participant information to be created. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ParticipantsPostRequest"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -2598,50 +2427,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Participant information to be created. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ParticipantsPostRequest"];
-            };
-        };
     };
-    /** The callback `PUT /participants/{ID}` is used to inform the client of the result of the creation of the provided list of identities. */
+    /**
+     * Return bulk participant information
+     * @description The callback `PUT /participants/{ID}` is used to inform the client of the result of the creation of the provided list of identities.
+     */
     putParticipantsByID: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Participant information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ParticipantsIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2654,50 +2467,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Participant information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ParticipantsIDPutResponse"];
-            };
-        };
     };
-    /** 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. */
+    /**
+     * Return bulk participant information error
+     * @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.
+     */
     ParticipantsByIDAndError: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2710,48 +2507,29 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** 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`). */
+    /**
+     * Look up party information
+     * @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`).
+     */
     PartiesByTypeAndID: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -2765,45 +2543,34 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** 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. */
+    /**
+     * Return party information
+     * @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.
+     */
     PartiesByTypeAndID2: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Party information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["PartiesTypeIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2816,52 +2583,35 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Party information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["PartiesTypeIDPutResponse"];
-            };
-        };
     };
-    /** 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. */
+    /**
+     * Return party information error
+     * @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.
+     */
     PartiesErrorByTypeAndID: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2874,50 +2624,30 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** 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`). */
+    /**
+     * Look up party information
+     * @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`).
+     */
     PartiesSubIdByTypeAndID: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-                /** A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
-                SubId: components["parameters"]["SubId"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+                SubId: components["parameters"]["SubId"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -2931,47 +2661,35 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** 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. */
+    /**
+     * Return party information
+     * @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.
+     */
     PartiesSubIdByTypeAndIDPut: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-                /** A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
-                SubId: components["parameters"]["SubId"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+                SubId: components["parameters"]["SubId"];
+            };
+        };
+        /** @description Party information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["PartiesTypeIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2984,54 +2702,36 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Party information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["PartiesTypeIDPutResponse"];
-            };
-        };
     };
-    /** 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. */
+    /**
+     * Return party information error
+     * @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.
+     */
     PartiesSubIdErrorByTypeAndID: {
         parameters: {
-            path: {
-                /** The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
-                Type: components["parameters"]["Type"];
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-                /** A sub-identifier of the party identifier, or a sub-type of the party identifier's type. For example, `PASSPORT`, `DRIVING_LICENSE`. */
-                SubId: components["parameters"]["SubId"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                Type: components["parameters"]["Type"];
+                ID: components["parameters"]["ID"];
+                SubId: components["parameters"]["SubId"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3044,49 +2744,33 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** The HTTP request `POST /transactionRequests` is used to request the creation of a transaction request for the provided financial transaction in the server. */
+    /**
+     * Perform transaction request
+     * @description The HTTP request `POST /transactionRequests` is used to request the creation of a transaction request for the provided financial transaction in the server.
+     */
     TransactionRequests: {
         parameters: {
             header: {
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
         };
+        /** @description Transaction request to be created. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["TransactionRequestsPostRequest"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -3098,46 +2782,28 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Transaction request to be created. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["TransactionRequestsPostRequest"];
-            };
-        };
     };
-    /** The HTTP request `GET /transactionRequests/{ID}` is used to get information regarding a transaction request created or requested earlier. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request. */
+    /**
+     * Retrieve transaction request information
+     * @description The HTTP request `GET /transactionRequests/{ID}` is used to get information regarding a transaction request created or requested earlier. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request.
+     */
     TransactionRequestsByID: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -3151,43 +2817,33 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** The callback `PUT /transactionRequests/{ID}` is used to inform the client of a requested or created transaction request. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request, or the `{ID}` that was used in the `GET /transactionRequests/{ID}`. */
+    /**
+     * Return transaction request information
+     * @description The callback `PUT /transactionRequests/{ID}` is used to inform the client of a requested or created transaction request. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request, or the `{ID}` that was used in the `GET /transactionRequests/{ID}`.
+     */
     TransactionRequestsByIDPut: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Transaction request information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["TransactionRequestsIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3200,50 +2856,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Transaction request information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["TransactionRequestsIDPutResponse"];
-            };
-        };
     };
-    /** If the server is unable to find or create a transaction request, or another processing error occurs, the error callback `PUT /transactionRequests/{ID}/error` is used. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request, or the `{ID}` that was used in the `GET /transactionRequests/{ID}`. */
+    /**
+     * Return transaction request information error
+     * @description If the server is unable to find or create a transaction request, or another processing error occurs, the error callback `PUT /transactionRequests/{ID}/error` is used. The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of the transaction request, or the `{ID}` that was used in the `GET /transactionRequests/{ID}`.
+     */
     TransactionRequestsErrorByID: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3256,49 +2896,33 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** The HTTP request `POST /quotes` is used to request the creation of a quote for the provided financial transaction in the server. */
+    /**
+     * Calculate quote
+     * @description The HTTP request `POST /quotes` is used to request the creation of a quote for the provided financial transaction in the server.
+     */
     Quotes: {
         parameters: {
             header: {
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
         };
+        /** @description Details of the quote to be created. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["QuotesPostRequest"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -3310,46 +2934,28 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the quote to be created. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["QuotesPostRequest"];
-            };
-        };
     };
-    /** 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. */
+    /**
+     * Retrieve quote information
+     * @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.
+     */
     QuotesByID: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -3363,43 +2969,33 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** 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. */
+    /**
+     * Return quote information
+     * @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.
+     */
     QuotesByID1: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Quote information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["QuotesIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3412,50 +3008,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Quote information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["QuotesIDPutResponse"];
-            };
-        };
     };
-    /** If the server is unable to find or create a quote, or some other processing error occurs, the error callback `PUT /quotes/{ID}/error` is used. 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. */
+    /**
+     * Return quote information error
+     * @description If the server is unable to find or create a quote, or some other processing error occurs, the error callback `PUT /quotes/{ID}/error` is used. 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.
+     */
     QuotesByIDAndError: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3468,15 +3048,10 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
     /**
-     * The HTTP request `GET /authorizations/{ID}` is used to request the Payer to enter the applicable credentials in the Payee FSP system. The `{ID}` in the URI should contain the `transactionRequestID`, received from the `POST /transactionRequests` service earlier in the process. This request requires a query string to be included in the URI, with the following key-value pairs*:*
+     * Perform authorization
+     * @description The HTTP request `GET /authorizations/{ID}` is used to request the Payer to enter the applicable credentials in the Payee FSP system. The `{ID}` in the URI should contain the `transactionRequestID`, received from the `POST /transactionRequests` service earlier in the process. This request requires a query string to be included in the URI, with the following key-value pairs*:*
      *
      * - `authenticationType={Type}`, where `{Type}` value is a valid authentication type from the enumeration `AuthenticationType`.
      *
@@ -3492,36 +3067,21 @@ export interface operations {
      */
     AuthorizationsByIDGet: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -3535,43 +3095,33 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** The callback `PUT /authorizations/{ID}` is used to inform the client of the result of a previously-requested authorization. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /authorizations/{ID}` request. */
+    /**
+     * Return authorization result
+     * @description The callback `PUT /authorizations/{ID}` is used to inform the client of the result of a previously-requested authorization. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /authorizations/{ID}` request.
+     */
     AuthorizationsByIDPut: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Authorization result returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["AuthorizationsIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3584,50 +3134,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Authorization result returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["AuthorizationsIDPutResponse"];
-            };
-        };
     };
-    /** If the server is unable to find the transaction request, or another processing error occurs, the error callback `PUT /authorizations/{ID}/error` is used. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /authorizations/{ID}`. */
+    /**
+     * Return authorization error
+     * @description If the server is unable to find the transaction request, or another processing error occurs, the error callback `PUT /authorizations/{ID}/error` is used. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /authorizations/{ID}`.
+     */
     AuthorizationsByIDAndError: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3640,49 +3174,33 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** The HTTP request `POST /transfers` is used to request the creation of a transfer for the next ledger, and a financial transaction for the Payee FSP. */
+    /**
+     * Perform transfer
+     * @description The HTTP request `POST /transfers` is used to request the creation of a transfer for the next ledger, and a financial transaction for the Payee FSP.
+     */
     transfers: {
         parameters: {
             header: {
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
         };
+        /** @description Details of the transfer to be created. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["TransfersPostRequest"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -3694,46 +3212,28 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the transfer to be created. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["TransfersPostRequest"];
-            };
-        };
     };
-    /** The HTTP request `GET /transfers/{ID}` is used to get information regarding a transfer created or requested earlier. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer. */
+    /**
+     * Retrieve transfer information
+     * @description The HTTP request `GET /transfers/{ID}` is used to get information regarding a transfer created or requested earlier. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer.
+     */
     TransfersByIDGet: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -3747,43 +3247,33 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** The callback `PUT /transfers/{ID}` is used to inform the client of a requested or created transfer. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer, or the `{ID}` that was used in the `GET /transfers/{ID}` request. */
+    /**
+     * Return transfer information
+     * @description The callback `PUT /transfers/{ID}` is used to inform the client of a requested or created transfer. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer, or the `{ID}` that was used in the `GET /transfers/{ID}` request.
+     */
     TransfersByIDPut: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Transfer information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["TransfersIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3796,50 +3286,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Transfer information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["TransfersIDPutResponse"];
-            };
-        };
     };
-    /** If the server is unable to find or create a transfer, or another processing error occurs, the error callback `PUT /transfers/{ID}/error` is used. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer, or the `{ID}` that was used in the `GET /transfers/{ID}`. */
+    /**
+     * Return transfer information error
+     * @description If the server is unable to find or create a transfer, or another processing error occurs, the error callback `PUT /transfers/{ID}/error` is used. The `{ID}` in the URI should contain the `transferId` that was used for the creation of the transfer, or the `{ID}` that was used in the `GET /transfers/{ID}`.
+     */
     TransfersByIDAndError: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3852,46 +3326,28 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** The HTTP request `GET /transactions/{ID}` is used to get transaction information regarding a financial transaction created earlier. The `{ID}` in the URI should contain the `transactionId` that was used for the creation of the quote, as the transaction is created as part of another process (the transfer process). */
+    /**
+     * Retrieve transaction information
+     * @description The HTTP request `GET /transactions/{ID}` is used to get transaction information regarding a financial transaction created earlier. The `{ID}` in the URI should contain the `transactionId` that was used for the creation of the quote, as the transaction is created as part of another process (the transfer process).
+     */
     TransactionsByID: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -3905,43 +3361,33 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** The callback `PUT /transactions/{ID}` is used to inform the client of a requested transaction. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /transactions/{ID}` request. */
+    /**
+     * Return transaction information
+     * @description The callback `PUT /transactions/{ID}` is used to inform the client of a requested transaction. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /transactions/{ID}` request.
+     */
     TransactionsByID1: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Transaction information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["TransactionsIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3954,50 +3400,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Transaction information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["TransactionsIDPutResponse"];
-            };
-        };
     };
-    /** If the server is unable to find or create a transaction, or another processing error occurs, the error callback `PUT /transactions/{ID}/error` is used. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /transactions/{ID}` request. */
+    /**
+     * Return transaction information error
+     * @description If the server is unable to find or create a transaction, or another processing error occurs, the error callback `PUT /transactions/{ID}/error` is used. The `{ID}` in the URI should contain the `{ID}` that was used in the `GET /transactions/{ID}` request.
+     */
     TransactionsErrorByID: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -4010,49 +3440,33 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** The HTTP request `POST /bulkQuotes` is used to request the creation of a bulk quote for the provided financial transactions in the server. */
+    /**
+     * Calculate bulk quote
+     * @description The HTTP request `POST /bulkQuotes` is used to request the creation of a bulk quote for the provided financial transactions in the server.
+     */
     BulkQuotes: {
         parameters: {
             header: {
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
         };
+        /** @description Details of the bulk quote to be created. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["BulkQuotesPostRequest"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -4064,46 +3478,28 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the bulk quote to be created. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["BulkQuotesPostRequest"];
-            };
-        };
     };
-    /** The HTTP request `GET /bulkQuotes/{ID}` is used to get information regarding a bulk quote created or requested earlier. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote. */
+    /**
+     * Retrieve bulk quote information
+     * @description The HTTP request `GET /bulkQuotes/{ID}` is used to get information regarding a bulk quote created or requested earlier. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote.
+     */
     BulkQuotesByID: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -4117,43 +3513,33 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** The callback `PUT /bulkQuotes/{ID}` is used to inform the client of a requested or created bulk quote. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote, or the `{ID}` that was used in the `GET /bulkQuotes/{ID}` request. */
+    /**
+     * Return bulk quote information
+     * @description The callback `PUT /bulkQuotes/{ID}` is used to inform the client of a requested or created bulk quote. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote, or the `{ID}` that was used in the `GET /bulkQuotes/{ID}` request.
+     */
     BulkQuotesByID1: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Bulk quote information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["BulkQuotesIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -4166,50 +3552,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Bulk quote information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["BulkQuotesIDPutResponse"];
-            };
-        };
     };
-    /** If the server is unable to find or create a bulk quote, or another processing error occurs, the error callback `PUT /bulkQuotes/{ID}/error` is used. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote, or the `{ID}` that was used in the `GET /bulkQuotes/{ID}` request. */
+    /**
+     * Return bulk quote information error
+     * @description If the server is unable to find or create a bulk quote, or another processing error occurs, the error callback `PUT /bulkQuotes/{ID}/error` is used. The `{ID}` in the URI should contain the `bulkQuoteId` that was used for the creation of the bulk quote, or the `{ID}` that was used in the `GET /bulkQuotes/{ID}` request.
+     */
     BulkQuotesErrorByID: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -4222,49 +3592,33 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** The HTTP request `POST /bulkTransfers` is used to request the creation of a bulk transfer in the server. */
+    /**
+     * Perform bulk transfer
+     * @description The HTTP request `POST /bulkTransfers` is used to request the creation of a bulk transfer in the server.
+     */
     BulkTransfers: {
         parameters: {
             header: {
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
         };
+        /** @description Details of the bulk transfer to be created. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["BulkTransfersPostRequest"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -4276,46 +3630,28 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the bulk transfer to be created. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["BulkTransfersPostRequest"];
-            };
-        };
     };
-    /** The HTTP request `GET /bulkTransfers/{ID}` is used to get information regarding a bulk transfer created or requested earlier. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer. */
+    /**
+     * Retrieve bulk transfer information
+     * @description The HTTP request `GET /bulkTransfers/{ID}` is used to get information regarding a bulk transfer created or requested earlier. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer.
+     */
     BulkTransferByID: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /** The `Accept` header field indicates the version of the API the client would like the server to use. */
                 Accept: components["parameters"]["Accept"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -4329,43 +3665,33 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** The callback `PUT /bulkTransfers/{ID}` is used to inform the client of a requested or created bulk transfer. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer (`POST /bulkTransfers`), or the `{ID}` that was used in the `GET /bulkTransfers/{ID}` request. */
+    /**
+     * Return bulk transfer information
+     * @description The callback `PUT /bulkTransfers/{ID}` is used to inform the client of a requested or created bulk transfer. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer (`POST /bulkTransfers`), or the `{ID}` that was used in the `GET /bulkTransfers/{ID}` request.
+     */
     BulkTransfersByIDPut: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Bulk transfer information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["BulkTransfersIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -4378,50 +3704,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Bulk transfer information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["BulkTransfersIDPutResponse"];
-            };
-        };
     };
-    /** If the server is unable to find or create a bulk transfer, or another processing error occurs, the error callback `PUT /bulkTransfers/{ID}/error` is used. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer (`POST /bulkTransfers`), or the `{ID}` that was used in the `GET /bulkTransfers/{ID}` request. */
+    /**
+     * Return bulk transfer information error
+     * @description If the server is unable to find or create a bulk transfer, or another processing error occurs, the error callback `PUT /bulkTransfers/{ID}/error` is used. The `{ID}` in the URI should contain the `bulkTransferId` that was used for the creation of the bulk transfer (`POST /bulkTransfers`), or the `{ID}` that was used in the `GET /bulkTransfers/{ID}` request.
+     */
     BulkTransfersErrorByID: {
         parameters: {
-            path: {
-                /** The identifier value. */
-                ID: components["parameters"]["ID"];
-            };
             header: {
-                /**
-                 * The `Content-Length` header field indicates the anticipated size of the payload body. Only sent if there is a body.
-                 *
-                 * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
-                 */
                 "Content-Length"?: components["parameters"]["Content-Length"];
-                /** The `Content-Type` header indicates the specific version of the API used to send the payload body. */
                 "Content-Type": components["parameters"]["Content-Type"];
-                /** The `Date` header field indicates the date when the request was sent. */
                 Date: components["parameters"]["Date"];
-                /**
-                 * The `X-Forwarded-For` header field is an unofficially accepted standard used for informational purposes of the originating client IP address, as a request might pass multiple proxies, firewalls, and so on. Multiple `X-Forwarded-For` values should be expected and supported by implementers of the API.
-                 *
-                 * **Note:** An alternative to `X-Forwarded-For` is defined in [RFC 7239](https://tools.ietf.org/html/rfc7239). However, to this point RFC 7239 is less-used and supported than `X-Forwarded-For`.
-                 */
                 "X-Forwarded-For"?: components["parameters"]["X-Forwarded-For"];
-                /** The `FSPIOP-Source` header field is a non-HTTP standard field used by the API for identifying the sender of the HTTP request. The field should be set by the original sender of the request. Required for routing and signature verification (see header field `FSPIOP-Signature`). */
                 "FSPIOP-Source": components["parameters"]["FSPIOP-Source"];
-                /** The `FSPIOP-Destination` header field is a non-HTTP standard field used by the API for HTTP header based routing of requests and responses to the destination. The field should be set by the original sender of the request (if known), so that any entities between the client and the server do not need to parse the payload for routing purposes. */
                 "FSPIOP-Destination"?: components["parameters"]["FSPIOP-Destination"];
-                /** The `FSPIOP-Encryption` header field is a non-HTTP standard field used by the API for applying end-to-end encryption of the request. */
                 "FSPIOP-Encryption"?: components["parameters"]["FSPIOP-Encryption"];
-                /** The `FSPIOP-Signature` header field is a non-HTTP standard field used by the API for applying an end-to-end request signature. */
                 "FSPIOP-Signature"?: components["parameters"]["FSPIOP-Signature"];
-                /** The `FSPIOP-URI` header field is a non-HTTP standard field used by the API for signature verification, should contain the service URI. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-URI"?: components["parameters"]["FSPIOP-URI"];
-                /** The `FSPIOP-HTTP-Method` header field is a non-HTTP standard field used by the API for signature verification, should contain the service HTTP method. Required if signature verification is used, for more information, see [the API Signature document](https://github.com/mojaloop/docs/tree/master/Specification%20Document%20Set). */
                 "FSPIOP-HTTP-Method"?: components["parameters"]["FSPIOP-HTTP-Method"];
             };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -4434,13 +3744,5 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Details of the error returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
 }
-export interface external {
-}