@mojaloop/api-snippets 17.2.0 → 17.2.3

package/lib/thirdparty/openapi.d.ts

@@ -4,129 +4,106 @@
  */
 export interface paths {
     "/interface": {
-        /** Essential path to include schema definitions that are not used so that these definitions get included into the openapi-cli bundle api definition so that they get converted into typescript definitions. */
+        /** @description Essential path to include schema definitions that are not used so that these definitions get included into the openapi-cli bundle api definition so that they get converted into typescript definitions. */
         post: operations["test"];
     };
     "/accounts/{ID}": {
-        /** The HTTP request `GET /accounts/{ID}` is used to retrieve the list of potential accounts available for linking. */
+        /**
+         * GetAccountsByUserId
+         * @description The HTTP request `GET /accounts/{ID}` is used to retrieve the list of potential accounts available for linking.
+         */
         get: operations["GetAccountsByUserId"];
-        /** The HTTP request `PUT /accounts/{ID}` is used to return the list of potential accounts available for linking */
+        /**
+         * UpdateAccountsByUserId
+         * @description The HTTP request `PUT /accounts/{ID}` is used to return the list of potential accounts available for linking
+         */
         put: operations["UpdateAccountsByUserId"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/accounts/{ID}/error": {
-        /** The HTTP request `PUT /accounts/{ID}/error` is used to return error information */
+        /**
+         * UpdateAccountsByUserIdError
+         * @description The HTTP request `PUT /accounts/{ID}/error` is used to return error information
+         */
         put: operations["UpdateAccountsByUserIdError"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/health": {
-        /** The HTTP request GET /health is used to return the current status of the API. */
+        /**
+         * Health check endpoint
+         * @description The HTTP request GET /health is used to return the current status of the API.
+         */
         get: operations["HealthGet"];
     };
     "/metrics": {
-        /** The HTTP request GET /metrics is used to return metrics for the API. */
+        /**
+         * Prometheus metrics endpoint
+         * @description The HTTP request GET /metrics is used to return metrics for the API.
+         */
         get: operations["MetricsGet"];
     };
     "/consentRequests": {
         /**
-         * The HTTP request **POST /consentRequests** is used to request a DFSP to grant access to one or more
+         * CreateConsentRequest
+         * @description The HTTP request **POST /consentRequests** is used to request a DFSP to grant access to one or more
          * accounts owned by a customer of the DFSP for the PISP who sends the request.
          */
         post: operations["CreateConsentRequest"];
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
     };
     "/consentRequests/{ID}": {
         /**
-         * The HTTP request `GET /consentRequests/{ID}` is used to get information about a previously
+         * GetConsentRequestsById
+         * @description The HTTP request `GET /consentRequests/{ID}` is used to get information about a previously
          * requested consent. The *{ID}* in the URI should contain the consentRequestId that was assigned to the
          * request by the PISP when the PISP originated the request.
          */
         get: operations["GetConsentRequestsById"];
         /**
-         * A DFSP uses this callback to (1) inform the PISP that the consentRequest has been accepted,
+         * UpdateConsentRequest
+         * @description A DFSP uses this callback to (1) inform the PISP that the consentRequest has been accepted,
          * and (2) communicate to the PISP which `authChannel` it should use to authenticate their user
          * with.
          *
@@ -137,115 +114,87 @@ export interface paths {
          * particular authorization request.
          */
         put: operations["UpdateConsentRequest"];
-        /** After the user completes an out-of-band authorization with the DFSP, the PISP will receive a token which they can use to prove to the DFSP that the user trusts this PISP. */
+        /**
+         * PatchConsentRequest
+         * @description After the user completes an out-of-band authorization with the DFSP, the PISP will receive a token which they can use to prove to the DFSP that the user trusts this PISP.
+         */
         patch: operations["PatchConsentRequest"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/consentRequests/{ID}/error": {
-        /** DFSP responds to the PISP if something went wrong with validating an OTP or secret. */
+        /**
+         * NotifyErrorConsentRequests
+         * @description DFSP responds to the PISP if something went wrong with validating an OTP or secret.
+         */
         put: operations["NotifyErrorConsentRequests"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/consents": {
-        /** The **POST /consents** request is used to request the creation of a consent for interactions between a PISP and the DFSP who owns the account which a PISP’s customer wants to allow the PISP access to. */
+        /**
+         * PostConsents
+         * @description The **POST /consents** request is used to request the creation of a consent for interactions between a PISP and the DFSP who owns the account which a PISP’s customer wants to allow the PISP access to.
+         */
         post: operations["PostConsents"];
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
     };
     "/consents/{ID}": {
-        /** The **GET /consents/**_{ID}_ resource allows a party to enquire after the status of a consent. The *{ID}* used in the URI of the request should be the consent request ID which was used to identify the consent when it was created. */
+        /**
+         * GetConsent
+         * @description The **GET /consents/**_{ID}_ resource allows a party to enquire after the status of a consent. The *{ID}* used in the URI of the request should be the consent request ID which was used to identify the consent when it was created.
+         */
         get: operations["GetConsent"];
         /**
-         * The HTTP request `PUT /consents/{ID}` is used by the PISP and Auth Service.
+         * PutConsentByID
+         * @description The HTTP request `PUT /consents/{ID}` is used by the PISP and Auth Service.
          *
          * - Called by a `PISP` to after signing a challenge. Sent to an DFSP for verification.
          * - Called by a `auth-service` to notify a DFSP that a credential has been verified and registered.
          */
         put: operations["PutConsentByID"];
         /**
-         * Used by PISP, DFSP
+         * @description Used by PISP, DFSP
          *
          * The **DELETE /consents/**_{ID}_ request is used to request the revocation of a previously agreed consent.
          * For tracing and auditing purposes, the switch should be sure not to delete the consent physically;
@@ -254,7 +203,8 @@ export interface paths {
          */
         delete: operations["DeleteConsentByID"];
         /**
-         * The HTTP request `PATCH /consents/{ID}` is used
+         * PatchConsentByID
+         * @description The HTTP request `PATCH /consents/{ID}` is used
          *
          * - In account linking in the Credential Registration phase. Used by a DFSP
          *   to notify a PISP a credential has been verified and registered with an
@@ -268,485 +218,346 @@ export interface paths {
          */
         patch: operations["PatchConsentByID"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/consents/{ID}/error": {
-        /** DFSP responds to the PISP if something went wrong with validating or storing consent. */
+        /**
+         * NotifyErrorConsents
+         * @description DFSP responds to the PISP if something went wrong with validating or storing consent.
+         */
         put: operations["NotifyErrorConsents"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/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"];
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
     };
     "/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"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/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["PutParticipantsByIDAndError"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/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`). An ExtensionList element has been added to this reqeust in version v1.1 */
+        /**
+         * 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`). An ExtensionList element has been added to this reqeust in version v1.1
+         */
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/services/{ServiceType}": {
         /**
-         * The HTTP request `GET /services/{ServiceType}` is used to retrieve the list of participants
+         * GetServicesByServiceType
+         * @description The HTTP request `GET /services/{ServiceType}` is used to retrieve the list of participants
          * that support a specified service.
          */
         get: operations["GetServicesByServiceType"];
         /**
-         * The HTTP request `PUT /services/{ServiceType}` is used to return list of participants
+         * PutServicesByServiceType
+         * @description The HTTP request `PUT /services/{ServiceType}` is used to return list of participants
          * that support a specified service.
          */
         put: operations["PutServicesByServiceType"];
         parameters: {
-            path: {
-                /** The type of the service identifier. For example, `THIRD_PARTY_DFSP` */
-                ServiceType: components["parameters"]["ServiceType"];
-            };
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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: {
+                ServiceType: components["parameters"]["ServiceType"];
+            };
         };
     };
     "/services/{ServiceType}/error": {
-        /** The HTTP request `PUT /services/{ServiceType}/error` is used to return error information */
+        /**
+         * PutServicesByServiceTypeAndError
+         * @description The HTTP request `PUT /services/{ServiceType}/error` is used to return error information
+         */
         put: operations["PutServicesByServiceTypeAndError"];
         parameters: {
-            path: {
-                /** The type of the service identifier. For example, `THIRD_PARTY_DFSP` */
-                ServiceType: components["parameters"]["ServiceType"];
-            };
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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: {
+                ServiceType: components["parameters"]["ServiceType"];
+            };
         };
     };
     "/thirdpartyRequests/transactions": {
-        /** The HTTP request POST `/thirdpartyRequests/transactions` is used by a PISP to initiate a 3rd party Transaction request with a DFSP */
+        /**
+         * ThirdpartyRequestsTransactionsPost
+         * @description The HTTP request POST `/thirdpartyRequests/transactions` is used by a PISP to initiate a 3rd party Transaction request with a DFSP
+         */
         post: operations["ThirdpartyRequestsTransactionsPost"];
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
     };
     "/thirdpartyRequests/transactions/{ID}": {
         /**
-         * The HTTP request `GET /thirdpartyRequests/transactions/{ID}` is used to request the
+         * GetThirdpartyTransactionRequests
+         * @description The HTTP request `GET /thirdpartyRequests/transactions/{ID}` is used to request the
          * retrieval of a third party transaction request.
          */
         get: operations["GetThirdpartyTransactionRequests"];
         /**
-         * The HTTP request `PUT /thirdpartyRequests/transactions/{ID}` is used by the DFSP to inform the client about
+         * UpdateThirdPartyTransactionRequests
+         * @description The HTTP request `PUT /thirdpartyRequests/transactions/{ID}` is used by the DFSP to inform the client about
          * the status of a previously requested thirdparty transaction request.
          *
          * Switch(Thirdparty API Adapter) -> PISP
          */
         put: operations["UpdateThirdPartyTransactionRequests"];
         /**
-         * The HTTP request `PATCH /thirdpartyRequests/transactions/{ID}` is used to
+         * NotifyThirdpartyTransactionRequests
+         * @description The HTTP request `PATCH /thirdpartyRequests/transactions/{ID}` is used to
          * notify a thirdparty of the outcome of a transaction request.
          *
          * Switch(Thirdparty API Adapter) -> PISP
          */
         patch: operations["NotifyThirdpartyTransactionRequests"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/thirdpartyRequests/transactions/{ID}/error": {
         /**
-         * If the server is unable to find the transaction request, or another processing error occurs,
+         * ThirdpartyTransactionRequestsError
+         * @description If the server is unable to find the transaction request, or another processing error occurs,
          * the error callback `PUT /thirdpartyRequests/transactions/{ID}/error` is used.
          * The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of
          * the thirdparty transaction request.
          */
         put: operations["ThirdpartyTransactionRequestsError"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/thirdpartyRequests/authorizations": {
-        /** The HTTP request **POST /thirdpartyRequests/authorizations** is used to request the validation by a customer for the transfer described in the request. */
+        /**
+         * PostThirdpartyRequestsAuthorizations
+         * @description The HTTP request **POST /thirdpartyRequests/authorizations** is used to request the validation by a customer for the transfer described in the request.
+         */
         post: operations["PostThirdpartyRequestsAuthorizations"];
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
     };
     "/thirdpartyRequests/authorizations/{ID}": {
         /**
-         * The HTTP request **GET /thirdpartyRequests/authorizations/**_{ID}_ is used to get information relating
+         * GetThirdpartyRequestsAuthorizationsById
+         * @description The HTTP request **GET /thirdpartyRequests/authorizations/**_{ID}_ is used to get information relating
          * to a previously issued authorization request. The *{ID}* in the request should match the
          * `authorizationRequestId` which was given when the authorization request was created.
          */
         get: operations["GetThirdpartyRequestsAuthorizationsById"];
         /**
-         * After receiving the **POST /thirdpartyRequests/authorizations**, the PISP will present the details of the
+         * PutThirdpartyRequestsAuthorizationsById
+         * @description After receiving the **POST /thirdpartyRequests/authorizations**, the PISP will present the details of the
          * transaction to their user, and request that the client sign the `challenge` field using the credential
          * they previously registered.
          *
@@ -754,39 +565,26 @@ export interface paths {
          */
         put: operations["PutThirdpartyRequestsAuthorizationsById"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/thirdpartyRequests/authorizations/{ID}/error": {
         /**
-         * The HTTP request `PUT /thirdpartyRequests/authorizations/{ID}/error` is used by the DFSP or PISP to inform
+         * PutThirdpartyRequestsAuthorizationsByIdAndError
+         * @description The HTTP request `PUT /thirdpartyRequests/authorizations/{ID}/error` is used by the DFSP or PISP to inform
          * the other party that something went wrong with a Thirdparty Transaction Authorization Request.
          *
          * The PISP may use this to tell the DFSP that the Thirdparty Transaction Authorization Request is invalid or doesn't
@@ -797,148 +595,100 @@ export interface paths {
          */
         put: operations["PutThirdpartyRequestsAuthorizationsByIdAndError"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/thirdpartyRequests/verifications": {
-        /** The HTTP request `POST /thirdpartyRequests/verifications` is used by the DFSP to verify a third party authorization. */
+        /**
+         * PostThirdpartyRequestsVerifications
+         * @description The HTTP request `POST /thirdpartyRequests/verifications` is used by the DFSP to verify a third party authorization.
+         */
         post: operations["PostThirdpartyRequestsVerifications"];
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
     };
     "/thirdpartyRequests/verifications/{ID}": {
         /**
-         * The HTTP request `/thirdpartyRequests/verifications/{ID}` is used to get
+         * GetThirdpartyRequestsVerificationsById
+         * @description The HTTP request `/thirdpartyRequests/verifications/{ID}` is used to get
          * information regarding a previously created or requested authorization. The *{ID}*
          * in the URI should contain the verification request ID
          */
         get: operations["GetThirdpartyRequestsVerificationsById"];
         /**
-         * The HTTP request `PUT /thirdpartyRequests/verifications/{ID}` is used by the Auth-Service to inform the DFSP of a successful result in validating the verification of a Thirdparty Transaction Request.
+         * PutThirdpartyRequestsVerificationsById
+         * @description The HTTP request `PUT /thirdpartyRequests/verifications/{ID}` is used by the Auth-Service to inform the DFSP of a successful result in validating the verification of a Thirdparty Transaction Request.
          * If the validation fails, the auth-service will send back `PUT /thirdpartyRequests/verifications/{ID}` with `authenticationResponse: 'REJECTED'`.
          * In unplanned error cases the Auth-Service MUST use `PUT /thirdpartyRequests/verifications/{ID}/error`.
          */
         put: operations["PutThirdpartyRequestsVerificationsById"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
     "/thirdpartyRequests/verifications/{ID}/error": {
         /**
-         * The HTTP request `PUT /thirdpartyRequests/verifications/{ID}/error` is used by the Auth-Service to inform
+         * PutThirdpartyRequestsVerificationsByIdAndError
+         * @description The HTTP request `PUT /thirdpartyRequests/verifications/{ID}/error` is used by the Auth-Service to inform
          * the DFSP of a failure in validating or looking up the verification of a Thirdparty Transaction Request.
          */
         put: operations["PutThirdpartyRequestsVerificationsByIdAndError"];
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
         };
     };
 }
+export type webhooks = Record<string, never>;
 export interface components {
     schemas: {
         /**
@@ -2074,62 +1824,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"];
             };
@@ -2147,19 +1925,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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
-        "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;
         /**
@@ -2167,69 +1945,62 @@ export interface components {
          *
          * **Note:** The API supports a maximum size of 5242880 bytes (5 Megabytes).
          */
-        "Content-Length": number;
+        "Content-Length"?: number;
         /** @description The type of the party identifier. For example, `MSISDN`, `PERSONAL_ID`. */
         Type: string;
         /** @description The type of the service identifier. For example, `THIRD_PARTY_DFSP` */
         ServiceType: 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 external = Record<string, never>;
 export interface operations {
-    /** Essential path to include schema definitions that are not used so that these definitions get included into the openapi-cli bundle api definition so that they get converted into typescript definitions. */
+    /** @description Essential path to include schema definitions that are not used so that these definitions get included into the openapi-cli bundle api definition so that they get converted into typescript definitions. */
     test: {
-        responses: {
-            /** Ok */
-            200: unknown;
-        };
-        requestBody: {
+        requestBody?: {
             content: {
                 "application/json": components["schemas"]["ParticipantsIDPutResponse"] | components["schemas"]["PartiesTypeIDPutResponse"] | components["schemas"]["QuotesIDPutResponse"] | components["schemas"]["ThirdpartyRequestsTransactionsIDPatchResponse"] | components["schemas"]["AuthorizationResponseType"] | components["schemas"]["ConsentStatusIssued"] | components["schemas"]["IlpFulfilment"] | components["schemas"]["Integer"] | components["schemas"]["Note"] | components["schemas"]["PartyIdInfoTPLink"] | components["schemas"]["PartyResult"] | components["schemas"]["ServiceType"] | components["schemas"]["ParticipantsPostRequest"] | components["schemas"]["QuotesPostRequest"];
             };
         };
+        responses: {
+            /** @description Ok */
+            200: {
+                content: never;
+            };
+        };
     };
-    /** The HTTP request `GET /accounts/{ID}` is used to retrieve the list of potential accounts available for linking. */
+    /**
+     * GetAccountsByUserId
+     * @description The HTTP request `GET /accounts/{ID}` is used to retrieve the list of potential accounts available for linking.
+     */
     GetAccountsByUserId: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -2243,42 +2014,45 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** The HTTP request `PUT /accounts/{ID}` is used to return the list of potential accounts available for linking */
+    /**
+     * UpdateAccountsByUserId
+     * @description The HTTP request `PUT /accounts/{ID}` is used to return the list of potential accounts available for linking
+     */
     UpdateAccountsByUserId: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+                "Content-Length"?: components["parameters"]["Content-Length"];
+            };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        requestBody: {
+            content: {
                 /**
-                 * 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).
+                 * @example [
+                 *   {
+                 *     "accountNickname": "dfspa.user.nickname1",
+                 *     "id": "dfspa.username.1234",
+                 *     "currency": "ZAR"
+                 *   },
+                 *   {
+                 *     "accountNickname": "dfspa.user.nickname2",
+                 *     "id": "dfspa.username.5678",
+                 *     "currency": "USD"
+                 *   }
+                 * ]
                  */
-                "Content-Length"?: components["parameters"]["Content-Length"];
+                "application/json": components["schemas"]["AccountsIDPutResponse"];
             };
         };
         responses: {
@@ -2292,49 +2066,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["AccountsIDPutResponse"];
-            };
-        };
     };
-    /** The HTTP request `PUT /accounts/{ID}/error` is used to return error information */
+    /**
+     * UpdateAccountsByUserIdError
+     * @description The HTTP request `PUT /accounts/{ID}/error` is used to return error information
+     */
     UpdateAccountsByUserIdError: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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 Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2347,14 +2106,11 @@ 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 /health is used to return the current status of the API. */
+    /**
+     * Health check endpoint
+     * @description The HTTP request GET /health is used to return the current status of the API.
+     */
     HealthGet: {
         responses: {
             200: components["responses"]["200"];
@@ -2368,7 +2124,10 @@ export interface operations {
             503: components["responses"]["503"];
         };
     };
-    /** The HTTP request GET /metrics is used to return metrics for the API. */
+    /**
+     * Prometheus metrics endpoint
+     * @description The HTTP request GET /metrics is used to return metrics for the API.
+     */
     MetricsGet: {
         responses: {
             200: components["responses"]["200"];
@@ -2383,44 +2142,32 @@ export interface operations {
         };
     };
     /**
-     * The HTTP request **POST /consentRequests** is used to request a DFSP to grant access to one or more
+     * CreateConsentRequest
+     * @description The HTTP request **POST /consentRequests** is used to request a DFSP to grant access to one or more
      * accounts owned by a customer of the DFSP for the PISP who sends the request.
      */
     CreateConsentRequest: {
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
+        /** @description The consentRequest to create */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ConsentRequestsPostRequest"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -2432,50 +2179,30 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** The consentRequest to create */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ConsentRequestsPostRequest"];
-            };
-        };
     };
     /**
-     * The HTTP request `GET /consentRequests/{ID}` is used to get information about a previously
+     * GetConsentRequestsById
+     * @description The HTTP request `GET /consentRequests/{ID}` is used to get information about a previously
      * requested consent. The *{ID}* in the URI should contain the consentRequestId that was assigned to the
      * request by the PISP when the PISP originated the request.
      */
     GetConsentRequestsById: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -2490,7 +2217,8 @@ export interface operations {
         };
     };
     /**
-     * A DFSP uses this callback to (1) inform the PISP that the consentRequest has been accepted,
+     * UpdateConsentRequest
+     * @description A DFSP uses this callback to (1) inform the PISP that the consentRequest has been accepted,
      * and (2) communicate to the PISP which `authChannel` it should use to authenticate their user
      * with.
      *
@@ -2502,40 +2230,26 @@ export interface operations {
      */
     UpdateConsentRequest: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
+        };
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ConsentRequestsIDPutResponseWeb"] | components["schemas"]["ConsentRequestsIDPutResponseOTP"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -2548,51 +2262,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ConsentRequestsIDPutResponseWeb"] | components["schemas"]["ConsentRequestsIDPutResponseOTP"];
-            };
-        };
     };
-    /** After the user completes an out-of-band authorization with the DFSP, the PISP will receive a token which they can use to prove to the DFSP that the user trusts this PISP. */
+    /**
+     * PatchConsentRequest
+     * @description After the user completes an out-of-band authorization with the DFSP, the PISP will receive a token which they can use to prove to the DFSP that the user trusts this PISP.
+     */
     PatchConsentRequest: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ConsentRequestsIDPatchRequest"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -2605,49 +2302,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ConsentRequestsIDPatchRequest"];
-            };
-        };
     };
-    /** DFSP responds to the PISP if something went wrong with validating an OTP or secret. */
+    /**
+     * NotifyErrorConsentRequests
+     * @description DFSP responds to the PISP if something went wrong with validating an OTP or secret.
+     */
     NotifyErrorConsentRequests: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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 Error information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2660,49 +2342,32 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Error information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** The **POST /consents** request is used to request the creation of a consent for interactions between a PISP and the DFSP who owns the account which a PISP’s customer wants to allow the PISP access to. */
+    /**
+     * PostConsents
+     * @description The **POST /consents** request is used to request the creation of a consent for interactions between a PISP and the DFSP who owns the account which a PISP’s customer wants to allow the PISP access to.
+     */
     PostConsents: {
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ConsentsPostRequestAUTH"] | components["schemas"]["ConsentsPostRequestPISP"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -2714,45 +2379,28 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ConsentsPostRequestAUTH"] | components["schemas"]["ConsentsPostRequestPISP"];
-            };
-        };
     };
-    /** The **GET /consents/**_{ID}_ resource allows a party to enquire after the status of a consent. The *{ID}* used in the URI of the request should be the consent request ID which was used to identify the consent when it was created. */
+    /**
+     * GetConsent
+     * @description The **GET /consents/**_{ID}_ resource allows a party to enquire after the status of a consent. The *{ID}* used in the URI of the request should be the consent request ID which was used to identify the consent when it was created.
+     */
     GetConsent: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -2767,47 +2415,34 @@ export interface operations {
         };
     };
     /**
-     * The HTTP request `PUT /consents/{ID}` is used by the PISP and Auth Service.
+     * PutConsentByID
+     * @description The HTTP request `PUT /consents/{ID}` is used by the PISP and Auth Service.
      *
      * - Called by a `PISP` to after signing a challenge. Sent to an DFSP for verification.
      * - Called by a `auth-service` to notify a DFSP that a credential has been verified and registered.
      */
     PutConsentByID: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+            };
+        };
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ConsentsIDPutResponseSigned"] | components["schemas"]["ConsentsIDPutResponseVerified"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2821,14 +2456,9 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ConsentsIDPutResponseSigned"] | components["schemas"]["ConsentsIDPutResponseVerified"];
-            };
-        };
     };
     /**
-     * Used by PISP, DFSP
+     * @description Used by PISP, DFSP
      *
      * The **DELETE /consents/**_{ID}_ request is used to request the revocation of a previously agreed consent.
      * For tracing and auditing purposes, the switch should be sure not to delete the consent physically;
@@ -2837,36 +2467,21 @@ export interface operations {
      */
     DeleteConsentByID: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -2881,7 +2496,8 @@ export interface operations {
         };
     };
     /**
-     * The HTTP request `PATCH /consents/{ID}` is used
+     * PatchConsentByID
+     * @description The HTTP request `PATCH /consents/{ID}` is used
      *
      * - In account linking in the Credential Registration phase. Used by a DFSP
      *   to notify a PISP a credential has been verified and registered with an
@@ -2895,42 +2511,27 @@ export interface operations {
      */
     PatchConsentByID: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ConsentsIDPatchResponseVerified"] | components["schemas"]["ConsentsIDPatchResponseRevoked"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2943,49 +2544,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ConsentsIDPatchResponseVerified"] | components["schemas"]["ConsentsIDPatchResponseRevoked"];
-            };
-        };
     };
-    /** DFSP responds to the PISP if something went wrong with validating or storing consent. */
+    /**
+     * NotifyErrorConsents
+     * @description DFSP responds to the PISP if something went wrong with validating or storing consent.
+     */
     NotifyErrorConsents: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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 Error information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -2998,49 +2584,33 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Error information 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 `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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
+        /** @description Participant information to be created. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ParticipantsPostRequest"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -3052,50 +2622,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-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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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 Participant information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ParticipantsIDPutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3108,50 +2662,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.
+     */
     PutParticipantsByIDAndError: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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 Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3164,48 +2702,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 /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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -3219,45 +2738,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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -3270,54 +2778,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`). An ExtensionList element has been added to this reqeust in version v1.1 */
+    /**
+     * 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`). An ExtensionList element has been added to this reqeust in version v1.1
+     */
     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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -3330,52 +2820,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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -3389,45 +2858,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-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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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 Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3440,49 +2898,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 /services/{ServiceType}` is used to retrieve the list of participants
+     * GetServicesByServiceType
+     * @description The HTTP request `GET /services/{ServiceType}` is used to retrieve the list of participants
      * that support a specified service.
      */
     GetServicesByServiceType: {
         parameters: {
-            path: {
-                /** The type of the service identifier. For example, `THIRD_PARTY_DFSP` */
-                ServiceType: components["parameters"]["ServiceType"];
-            };
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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: {
+                ServiceType: components["parameters"]["ServiceType"];
+            };
         };
         responses: {
             202: components["responses"]["202"];
@@ -3497,45 +2935,32 @@ export interface operations {
         };
     };
     /**
-     * The HTTP request `PUT /services/{ServiceType}` is used to return list of participants
+     * PutServicesByServiceType
+     * @description The HTTP request `PUT /services/{ServiceType}` is used to return list of participants
      * that support a specified service.
      */
     PutServicesByServiceType: {
         parameters: {
-            path: {
-                /** The type of the service identifier. For example, `THIRD_PARTY_DFSP` */
-                ServiceType: components["parameters"]["ServiceType"];
-            };
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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: {
+                ServiceType: components["parameters"]["ServiceType"];
+            };
+        };
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ServicesServiceTypePutResponse"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3548,49 +2973,34 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ServicesServiceTypePutResponse"];
-            };
-        };
     };
-    /** The HTTP request `PUT /services/{ServiceType}/error` is used to return error information */
+    /**
+     * PutServicesByServiceTypeAndError
+     * @description The HTTP request `PUT /services/{ServiceType}/error` is used to return error information
+     */
     PutServicesByServiceTypeAndError: {
         parameters: {
-            path: {
-                /** The type of the service identifier. For example, `THIRD_PARTY_DFSP` */
-                ServiceType: components["parameters"]["ServiceType"];
-            };
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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: {
+                ServiceType: components["parameters"]["ServiceType"];
+            };
+        };
+        /** @description Details of the error returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3603,49 +3013,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 `/thirdpartyRequests/transactions` is used by a PISP to initiate a 3rd party Transaction request with a DFSP */
+    /**
+     * ThirdpartyRequestsTransactionsPost
+     * @description The HTTP request POST `/thirdpartyRequests/transactions` is used by a PISP to initiate a 3rd party Transaction request with a DFSP
+     */
     ThirdpartyRequestsTransactionsPost: {
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
+        /** @description Transaction request to be created. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ThirdpartyRequestsTransactionsPostRequest"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -3657,49 +3051,29 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Transaction request to be created. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ThirdpartyRequestsTransactionsPostRequest"];
-            };
-        };
     };
     /**
-     * The HTTP request `GET /thirdpartyRequests/transactions/{ID}` is used to request the
+     * GetThirdpartyTransactionRequests
+     * @description The HTTP request `GET /thirdpartyRequests/transactions/{ID}` is used to request the
      * retrieval of a third party transaction request.
      */
     GetThirdpartyTransactionRequests: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -3714,46 +3088,38 @@ export interface operations {
         };
     };
     /**
-     * The HTTP request `PUT /thirdpartyRequests/transactions/{ID}` is used by the DFSP to inform the client about
+     * UpdateThirdPartyTransactionRequests
+     * @description The HTTP request `PUT /thirdpartyRequests/transactions/{ID}` is used by the DFSP to inform the client about
      * the status of a previously requested thirdparty transaction request.
      *
      * Switch(Thirdparty API Adapter) -> PISP
      */
     UpdateThirdPartyTransactionRequests: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+                "Content-Length"?: components["parameters"]["Content-Length"];
+            };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        requestBody: {
+            content: {
                 /**
-                 * 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).
+                 * @example {
+                 *   "transactionRequestState": "RECEIVED"
+                 * }
                  */
-                "Content-Length"?: components["parameters"]["Content-Length"];
+                "application/json": components["schemas"]["ThirdpartyRequestsTransactionsIDPutResponse"];
             };
         };
         responses: {
@@ -3767,55 +3133,42 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ThirdpartyRequestsTransactionsIDPutResponse"];
-            };
-        };
     };
     /**
-     * The HTTP request `PATCH /thirdpartyRequests/transactions/{ID}` is used to
+     * NotifyThirdpartyTransactionRequests
+     * @description The HTTP request `PATCH /thirdpartyRequests/transactions/{ID}` is used to
      * notify a thirdparty of the outcome of a transaction request.
      *
      * Switch(Thirdparty API Adapter) -> PISP
      */
     NotifyThirdpartyTransactionRequests: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+                "Content-Length"?: components["parameters"]["Content-Length"];
+            };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        requestBody: {
+            content: {
                 /**
-                 * 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).
+                 * @example {
+                 *   "transactionRequestState": "ACCEPTED",
+                 *   "transactionState": "COMMITTED"
+                 * }
                  */
-                "Content-Length"?: components["parameters"]["Content-Length"];
+                "application/json": components["schemas"]["ThirdpartyRequestsTransactionsIDPatchResponse"];
             };
         };
         responses: {
@@ -3829,54 +3182,37 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ThirdpartyRequestsTransactionsIDPatchResponse"];
-            };
-        };
     };
     /**
-     * If the server is unable to find the transaction request, or another processing error occurs,
+     * ThirdpartyTransactionRequestsError
+     * @description If the server is unable to find the transaction request, or another processing error occurs,
      * the error callback `PUT /thirdpartyRequests/transactions/{ID}/error` is used.
      * The `{ID}` in the URI should contain the `transactionRequestId` that was used for the creation of
      * the thirdparty transaction request.
      */
     ThirdpartyTransactionRequestsError: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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 Error information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -3889,49 +3225,33 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Error information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** The HTTP request **POST /thirdpartyRequests/authorizations** is used to request the validation by a customer for the transfer described in the request. */
+    /**
+     * PostThirdpartyRequestsAuthorizations
+     * @description The HTTP request **POST /thirdpartyRequests/authorizations** is used to request the validation by a customer for the transfer described in the request.
+     */
     PostThirdpartyRequestsAuthorizations: {
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
+        /** @description Authorization request details */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ThirdpartyRequestsAuthorizationsPostRequest"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -3943,50 +3263,30 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Authorization request details */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ThirdpartyRequestsAuthorizationsPostRequest"];
-            };
-        };
     };
     /**
-     * The HTTP request **GET /thirdpartyRequests/authorizations/**_{ID}_ is used to get information relating
+     * GetThirdpartyRequestsAuthorizationsById
+     * @description The HTTP request **GET /thirdpartyRequests/authorizations/**_{ID}_ is used to get information relating
      * to a previously issued authorization request. The *{ID}* in the request should match the
      * `authorizationRequestId` which was given when the authorization request was created.
      */
     GetThirdpartyRequestsAuthorizationsById: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -4001,7 +3301,8 @@ export interface operations {
         };
     };
     /**
-     * After receiving the **POST /thirdpartyRequests/authorizations**, the PISP will present the details of the
+     * PutThirdpartyRequestsAuthorizationsById
+     * @description After receiving the **POST /thirdpartyRequests/authorizations**, the PISP will present the details of the
      * transaction to their user, and request that the client sign the `challenge` field using the credential
      * they previously registered.
      *
@@ -4009,40 +3310,27 @@ export interface operations {
      */
     PutThirdpartyRequestsAuthorizationsById: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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 Signed authorization object */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ThirdpartyRequestsAuthorizationsIDPutResponseRejected"] | components["schemas"]["ThirdpartyRequestsAuthorizationsIDPutResponseFIDO"] | components["schemas"]["ThirdpartyRequestsAuthorizationsIDPutResponseGeneric"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -4055,15 +3343,10 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Signed authorization object */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ThirdpartyRequestsAuthorizationsIDPutResponseRejected"] | components["schemas"]["ThirdpartyRequestsAuthorizationsIDPutResponseFIDO"] | components["schemas"]["ThirdpartyRequestsAuthorizationsIDPutResponseGeneric"];
-            };
-        };
     };
     /**
-     * The HTTP request `PUT /thirdpartyRequests/authorizations/{ID}/error` is used by the DFSP or PISP to inform
+     * PutThirdpartyRequestsAuthorizationsByIdAndError
+     * @description The HTTP request `PUT /thirdpartyRequests/authorizations/{ID}/error` is used by the DFSP or PISP to inform
      * the other party that something went wrong with a Thirdparty Transaction Authorization Request.
      *
      * The PISP may use this to tell the DFSP that the Thirdparty Transaction Authorization Request is invalid or doesn't
@@ -4074,40 +3357,27 @@ export interface operations {
      */
     PutThirdpartyRequestsAuthorizationsByIdAndError: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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 Error information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -4120,49 +3390,33 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Error information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
-    /** The HTTP request `POST /thirdpartyRequests/verifications` is used by the DFSP to verify a third party authorization. */
+    /**
+     * PostThirdpartyRequestsVerifications
+     * @description The HTTP request `POST /thirdpartyRequests/verifications` is used by the DFSP to verify a third party authorization.
+     */
     PostThirdpartyRequestsVerifications: {
         parameters: {
             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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
             };
         };
+        /** @description The thirdparty authorization details to verify */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ThirdpartyRequestsVerificationsPostRequestFIDO"] | components["schemas"]["ThirdpartyRequestsVerificationsPostRequestGeneric"];
+            };
+        };
         responses: {
             202: components["responses"]["202"];
             400: components["responses"]["400"];
@@ -4174,50 +3428,30 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** The thirdparty authorization details to verify */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ThirdpartyRequestsVerificationsPostRequestFIDO"] | components["schemas"]["ThirdpartyRequestsVerificationsPostRequestGeneric"];
-            };
-        };
     };
     /**
-     * The HTTP request `/thirdpartyRequests/verifications/{ID}` is used to get
+     * GetThirdpartyRequestsVerificationsById
+     * @description The HTTP request `/thirdpartyRequests/verifications/{ID}` is used to get
      * information regarding a previously created or requested authorization. The *{ID}*
      * in the URI should contain the verification request ID
      */
     GetThirdpartyRequestsVerificationsById: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
@@ -4232,45 +3466,38 @@ export interface operations {
         };
     };
     /**
-     * The HTTP request `PUT /thirdpartyRequests/verifications/{ID}` is used by the Auth-Service to inform the DFSP of a successful result in validating the verification of a Thirdparty Transaction Request.
+     * PutThirdpartyRequestsVerificationsById
+     * @description The HTTP request `PUT /thirdpartyRequests/verifications/{ID}` is used by the Auth-Service to inform the DFSP of a successful result in validating the verification of a Thirdparty Transaction Request.
      * If the validation fails, the auth-service will send back `PUT /thirdpartyRequests/verifications/{ID}` with `authenticationResponse: 'REJECTED'`.
      * In unplanned error cases the Auth-Service MUST use `PUT /thirdpartyRequests/verifications/{ID}/error`.
      */
     PutThirdpartyRequestsVerificationsById: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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"];
+                "Content-Length"?: components["parameters"]["Content-Length"];
+            };
+            path: {
+                ID: components["parameters"]["ID"];
+            };
+        };
+        /** @description The result of validating the Thirdparty Transaction Request */
+        requestBody: {
+            content: {
                 /**
-                 * 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).
+                 * @example {
+                 *   "authenticationResponse": "VERIFIED"
+                 * }
                  */
-                "Content-Length"?: components["parameters"]["Content-Length"];
+                "application/json": components["schemas"]["ThirdpartyRequestsVerificationsIDPutResponse"];
             };
         };
         responses: {
@@ -4284,53 +3511,35 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** The result of validating the Thirdparty Transaction Request */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ThirdpartyRequestsVerificationsIDPutResponse"];
-            };
-        };
     };
     /**
-     * The HTTP request `PUT /thirdpartyRequests/verifications/{ID}/error` is used by the Auth-Service to inform
+     * PutThirdpartyRequestsVerificationsByIdAndError
+     * @description The HTTP request `PUT /thirdpartyRequests/verifications/{ID}/error` is used by the Auth-Service to inform
      * the DFSP of a failure in validating or looking up the verification of a Thirdparty Transaction Request.
      */
     PutThirdpartyRequestsVerificationsByIdAndError: {
         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 must be set by the original sender of the request if the destination is known (valid for all services except GET /parties) so that any entities between the client and the server do not need to parse the payload for routing purposes. If the destination is not known (valid for service GET /parties), the field should be left empty. */
                 "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 Error information returned. */
+        requestBody: {
+            content: {
+                "application/json": components["schemas"]["ErrorInformationObject"];
+            };
         };
         responses: {
             200: components["responses"]["200"];
@@ -4343,13 +3552,5 @@ export interface operations {
             501: components["responses"]["501"];
             503: components["responses"]["503"];
         };
-        /** Error information returned. */
-        requestBody: {
-            content: {
-                "application/json": components["schemas"]["ErrorInformationObject"];
-            };
-        };
     };
 }
-export interface external {
-}