@mojaloop/api-snippets 12.8.0 → 13.0.2

package/thirdparty/openapi3/components/schemas/ThirdpartyRequestsTransactionsIDPutResponse.yaml

@@ -2,10 +2,7 @@ title: ThirdpartyRequestsTransactionsIDPutResponse
 type: object
 description: 'The object sent in the PUT /thirdPartyRequests/transactions/{ID} request.'
 properties:
-  transactionId:
-    $ref: ./CorrelationId.yaml
   transactionRequestState:
     $ref: ./TransactionRequestState.yaml
 required:
-  - transactionId
   - transactionRequestState

package/thirdparty/openapi3/components/schemas/ThirdpartyRequestsTransactionsPostRequest.yaml

@@ -6,9 +6,9 @@ properties:
     allOf:
       - $ref: ./CorrelationId.yaml
     description: >
-      Common ID between the FSPs for the transaction request object. The ID
-      should be reused for resends of the same transaction request. A new ID
-      should be generated for each new transaction request.
+      Common ID between the PISP and the Payer DFSP for the transaction request object.
+      The ID should be reused for resends of the same transaction request. 
+      A new ID should be generated for each new transaction request.
   payee:
     allOf:
       - $ref: ./Party.yaml
@@ -29,6 +29,11 @@ properties:
     allOf:
       - $ref: ./TransactionType.yaml
     description: Type of transaction.
+  note:
+    type: string
+    minLength: 1
+    maxLength: 256
+    description: A memo that will be attached to the transaction.
   expiration:
     type: string
     description: >

package/thirdparty/openapi3/components/schemas/ThirdpartyRequestsVerificationsPostRequestFIDO.yaml

@@ -16,11 +16,11 @@ properties:
       the signed challenge against.
   signedPayloadType:
     $ref: ./SignedPayloadTypeFIDO.yaml
-  signedPayload:
+  fidoSignedPayload:
     $ref: ./FIDOPublicKeyCredentialAssertion.yaml
 required:
   - verificationRequestId
   - challenge
   - consentId
   - signedPayloadType
-  - signedPayload
+  - fidoSignedPayload

package/thirdparty/openapi3/components/schemas/ThirdpartyRequestsVerificationsPostRequestGeneric.yaml

@@ -16,11 +16,11 @@ properties:
       the signed challenge against.
   signedPayloadType:
     $ref: ./SignedPayloadTypeGeneric.yaml
-  signedPayload:
+  genericSignedPayload:
     $ref: ./BinaryString.yaml
 required:
   - verificationRequestId
   - challenge
   - consentId
   - signedPayloadType
-  - signedPayload
+  - genericSignedPayload

package/thirdparty/openapi3/components/schemas/Uri.yaml

@@ -0,0 +1,8 @@
+title: Uri
+type: string
+pattern: '^(([^:/?#]+):)?(//([^/?#]*))?([^?#]*)(\?([^#]*))?(#(.*))?'
+minLength: 1
+maxLength: 512
+description: >
+  The API data type Uri is a JSON string in a canonical format that is restricted by a \
+  regular expression for interoperability reasons.

package/thirdparty/openapi3/openapi.yaml

@@ -50,18 +50,6 @@ paths:
     $ref: paths/accounts_ID.yaml
   /accounts/{ID}/error:
     $ref: paths/accounts_ID_error.yaml
-  # Note: this resource is deprecated in the latest API Draft, and will
-  # be removed in the next MAJOR version release of API-Snippets
-  # Please use /thirdpartyRequests/authorizations instead
-  # TODO: remove in next major version release
-  /authorizations:
-    $ref: paths/authorizations.yaml
-  # Note: this resource is deprecated in the latest API Draft, and will
-  # be removed in the next MAJOR version release of API-Snippets
-  # Please use /thirdpartyRequests/authorizations/{ID} instead
-  # TODO: remove in next major version release
-  /authorizations/{ID}:
-    $ref: paths/authorizations_ID.yaml
   /health:
     $ref: paths/health.yaml
   /metrics:
@@ -94,8 +82,6 @@ paths:
     $ref: paths/services_ServiceType_error.yaml
   /thirdpartyRequests/transactions:
     $ref: paths/thirdpartyRequests_transactions.yaml
-  /thirdpartyRequests/transactions-tsa:
-    $ref: paths/thirdpartyRequests_transactions_tsa.yaml
   /thirdpartyRequests/transactions/{ID}:
     $ref: paths/thirdpartyRequests_transactions_ID.yaml
   /thirdpartyRequests/transactions/{ID}/error:

package/thirdparty/openapi3/paths/consentRequests.yaml

@@ -16,7 +16,8 @@ post:
   operationId: CreateConsentRequest
   summary: CreateConsentRequest
   description: |
-    A request from a PISP to a DFSP to start the process of delegating consent
+    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.
   parameters:
     - $ref: ../components/parameters/Accept.yaml
     - $ref: ../components/parameters/Content-Length.yaml

package/thirdparty/openapi3/paths/consentRequests_ID.yaml

@@ -11,6 +11,37 @@ parameters:
   - $ref: ../components/parameters/FSPIOP-Signature.yaml
   - $ref: ../components/parameters/FSPIOP-URI.yaml
   - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
+get:
+  operationId: GetConsentRequestsById
+  summary: 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.
+  tags:
+    - consentRequests
+    - sampled
+  parameters:
+    - $ref: ../components/parameters/Accept.yaml
+  responses:
+    202:
+      $ref: ../components/responses/202.yaml
+    400:
+      $ref: ../components/responses/400.yaml
+    401:
+      $ref: ../components/responses/401.yaml
+    403:
+      $ref: ../components/responses/403.yaml
+    404:
+      $ref: ../components/responses/404.yaml
+    405:
+      $ref: ../components/responses/405.yaml
+    406:
+      $ref: ../components/responses/406.yaml
+    501:
+      $ref: ../components/responses/501.yaml
+    503:
+      $ref: ../components/responses/503.yaml
 put:
   tags:
     - consentRequests
@@ -18,10 +49,15 @@ put:
   operationId: UpdateConsentRequest
   summary: UpdateConsentRequest
   description: |
-    DFSP updates auth channels and/or auth uri in response to consentRequest.
+    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.
 
-    PISP updates the consentRequest to include authorization token from their user,
-    which the DFSP is to then verify.
+    When a PISP requests a series of permissions from a DFSP on behalf of a DFSP’s customer, not all 
+    the permissions requested may be granted by the DFSP. Conversely, the out-of-band authorization 
+    process  may result in additional privileges being granted by the account holder to the PISP. The
+    **PUT /consentRequests/**_{ID}_ resource returns the current state of the permissions relating to a 
+    particular authorization request.
   parameters:
     - $ref: ../components/parameters/Content-Length.yaml
   requestBody:
@@ -58,8 +94,8 @@ patch:
   operationId: PatchConsentRequest
   summary: PatchConsentRequest
   description: >
-    PISP sends user's OTP token to a DFSP to verify user trusts
-    aforementioned PISP
+    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.
   parameters:
     - $ref: ../components/parameters/Accept.yaml
     - $ref: ../components/parameters/Content-Length.yaml

package/thirdparty/openapi3/paths/consents.yaml

@@ -16,8 +16,8 @@ post:
   operationId: PostConsents
   summary: PostConsents
   description: >
-    DFSP sends this request to the PISP after granting consent.
-    DFSP sends this request to an Auth service to validate a signed consent.
+    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.
   parameters:
     - $ref: ../components/parameters/Accept.yaml
     - $ref: ../components/parameters/Content-Length.yaml

package/thirdparty/openapi3/paths/consents_ID.yaml

@@ -13,9 +13,9 @@ parameters:
   - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
 get:
   description: >
-    The HTTP request `GET /consents/{ID}` is used to get information regarding a consent object created or requested earlier.
-    The `{ID}` in the URI should contain the `{ID}` that was used in the `POST /consents`.
-    summary: GetConsent
+    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.
   tags:
     - consents
   operationId: GetConsent
@@ -135,9 +135,12 @@ put:
       $ref: ../components/responses/503.yaml
 delete:
   description: |
-    The HTTP request `DELETE /consents/{ID}` is used to mark as deleted a previously created consent.
+    Used by PISP, DFSP
 
-    - Called by a PISP when a user wants to remove their consent.
+    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; 
+    instead, information relating to the consent should be marked as deleted and requests relating to the
+    consent should not be honoured.
   operationId: DeleteConsentByID
   parameters:
     - $ref: ../components/parameters/Accept.yaml

package/thirdparty/openapi3/paths/thirdpartyRequests_authorizations.yaml

@@ -11,8 +11,8 @@ parameters:
   - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
 post:
   description:  >
-    The HTTP request `POST /thirdpartyRequests/authorizations` is used to request the Payer to enter the
-    applicable credentials in the PISP system.
+    The HTTP request **POST /thirdpartyRequests/authorizations** is used to request the validation by a
+    customer for the transfer described in the request.
   operationId: PostThirdpartyRequestsAuthorizations
   summary: PostThirdpartyRequestsAuthorizations
   tags:
@@ -28,39 +28,12 @@ post:
       application/json:
         schema:
           $ref: ../components/schemas/ThirdpartyRequestsAuthorizationsPostRequest.yaml
-        example:
-          authorizationRequestId: 33333333-0000-0000-0000-000000000000
-          transactionRequestId: '00000000-0000-0000-0000-000000000000'
-          challenge: '<base64 encoded binary - the encoded challenge>'
-          transferAmount:
-            amount: "100"
-            currency: "USD"
-          payeeReceiveAmount:
-            amount: "99"
-            currency: "USD"
-          fees:
-            amount: "1"
-            currency: "USD"
-          payee:
-            partyIdInfo:
-              partyIdType: 'MSISDN'
-              partyIdentifier: '+44 1234 5678'
-              fspId: 'dfspb'
-          payer:
-            partyIdType: 'THIRD_PARTY_LINK'
-            partyIdentifier: 'qwerty-123456'
-            fspId: 'dfspa'
-          transactionType:
-            scenario: "TRANSFER"
-            initiator: "PAYER"
-            initiatorType: "CONSUMER"
-          expiration: "2020-06-15T12:00:00.000"
   responses:
     202:
       $ref: ../components/responses/202.yaml
     400:
       $ref: ../components/responses/400.yaml
-    401:
+    401: 
       $ref: ../components/responses/401.yaml
     403:
       $ref: ../components/responses/403.yaml

package/thirdparty/openapi3/paths/thirdpartyRequests_authorizations_ID.yaml

@@ -11,11 +11,44 @@ parameters:
   - $ref: ../components/parameters/FSPIOP-Signature.yaml
   - $ref: ../components/parameters/FSPIOP-URI.yaml
   - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
+get:
+  description: |
+    The HTTP request **GET /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.
+  operationId: GetThirdpartyRequestsAuthorizationsById
+  summary: GetThirdpartyRequestsAuthorizationsById
+  tags:
+    - authorizations
+  parameters:
+    - $ref: ../components/parameters/Accept.yaml
+  responses:
+    202:
+      $ref: ../components/responses/202.yaml
+    400:
+      $ref: ../components/responses/400.yaml
+    401:
+      $ref: ../components/responses/401.yaml
+    403:
+      $ref: ../components/responses/403.yaml
+    404:
+      $ref: ../components/responses/404.yaml
+    405:
+      $ref: ../components/responses/405.yaml
+    406:
+      $ref: ../components/responses/406.yaml
+    501:
+      $ref: ../components/responses/501.yaml
+    503:
+      $ref: ../components/responses/503.yaml
 put:
   description: |
-    The callback PUT /thirdpartyRequests/authorizations/{ID} is used to inform the client of the
-    result of a previously-requested authorization. The ID in the URI should
-    contain the one that was used in the POST /authorizations/ requestBody.transactionRequestId @ OUTBOUND
+    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.
+
+    The signed challenge will be sent back by the PISP in **PUT /thirdpartyRequests/authorizations/**_{ID}_:
+
   operationId: PutThirdpartyRequestsAuthorizationsById
   summary: PutThirdpartyRequestsAuthorizationsById
   tags:
@@ -32,17 +65,6 @@ put:
             - $ref: '../components/schemas/ThirdpartyRequestsAuthorizationsIDPutResponseRejected.yaml'
             - $ref: '../components/schemas/ThirdpartyRequestsAuthorizationsIDPutResponseFIDO.yaml'
             - $ref: '../components/schemas/ThirdpartyRequestsAuthorizationsIDPutResponseGeneric.yaml'
-        example:
-          signedPayloadType: FIDO
-          signedPayload:
-            id: 45c-TkfkjQovQeAWmOy-RLBHEJ_e4jYzQYgD8VdbkePgM5d98BaAadadNYrknxgH0jQEON8zBydLgh1EqoC9DA
-            rawId: 45c+TkfkjQovQeAWmOy+RLBHEJ/e4jYzQYgD8VdbkePgM5d98BaAadadNYrknxgH0jQEON8zBydLgh1EqoC9DA==
-            response:
-              authenticatorData: SZYN5YgOjGh0NBcPZHZgW4/krrmihjLHmVzzuoMdl2MBAAAACA==
-              clientDataJSON: eyJ0eXBlIjoid2ViYXV0aG4uZ2V0IiwiY2hhbGxlbmdlIjoiQUFBQUFBQUFBQUFBQUFBQUFBRUNBdyIsIm9yaWdpbiI6Imh0dHA6Ly9sb2NhbGhvc3Q6NDIxODEiLCJjcm9zc09yaWdpbiI6ZmFsc2UsIm90aGVyX2tleXNfY2FuX2JlX2FkZGVkX2hlcmUiOiJkbyBub3QgY29tcGFyZSBjbGllbnREYXRhSlNPTiBhZ2FpbnN0IGEgdGVtcGxhdGUuIFNlZSBodHRwczovL2dvby5nbC95YWJQZXgifQ==
-              signature: MEUCIDcJRBu5aOLJVc/sPyECmYi23w8xF35n3RNhyUNVwQ2nAiEA+Lnd8dBn06OKkEgAq00BVbmH87ybQHfXlf1Y4RJqwQ8=
-            type: 'public-key'
-
   responses:
     200:
       $ref: ../components/responses/200.yaml

package/thirdparty/openapi3/paths/thirdpartyRequests_transactions.yaml

@@ -10,6 +10,11 @@ parameters:
   - $ref: ../components/parameters/FSPIOP-URI.yaml
   - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
 post:
+  operationId: ThirdpartyRequestsTransactionsPost
+  summary: ThirdpartyRequestsTransactionsPost
+  description: The HTTP request POST `/thirdpartyRequests/transactions` is used by a PISP to initiate a 3rd party Transaction request with a DFSP
+  tags:
+    - thirdpartyRequests
   parameters:
     #Headers
     - $ref: ../components/parameters/Accept.yaml
@@ -21,26 +26,6 @@ post:
       application/json:
         schema:
           $ref: ../components/schemas/ThirdpartyRequestsTransactionsPostRequest.yaml
-        example:
-          transactionRequestId: '8d34f91d-d078-4077-8263-2c047876fcf6'
-          payee:
-            partyIdInfo:
-              partyIdType: 'MSISDN'
-              partyIdentifier: '+44 1234 5678'
-              fspId: 'dfspb'
-          payer:
-            partyIdType: 'THIRD_PARTY_LINK'
-            partyIdentifier: 'qwerty-123456'
-            fspId: 'dfspa'
-          amountType: 'SEND'
-          amount:
-            amount: '100'
-            currency: 'USD'
-          transactionType:
-            scenario: 'TRANSFER'
-            initiator: 'PAYER'
-            initiatorType: 'CONSUMER'
-          expiration: '2020-07-15T22:17:28.985-01:00'
   responses:
     202:
       $ref: ../components/responses/202.yaml
@@ -59,10 +44,4 @@ post:
     501:
       $ref: ../components/responses/501.yaml
     503:
-      $ref: ../components/responses/503.yaml
-  operationId: CreateThirdpartyTransactionRequests
-  summary: CreateThirdpartyTransactionRequests
-  description: The HTTP request POST `/thirdpartyRequests/transactions` is used by a PISP to initiate a 3rd party Transaction request with a DFSP
-  tags:
-    - thirdpartyRequests
-    - sampled
+      $ref: ../components/responses/503.yaml

package/thirdparty/openapi3/paths/thirdpartyRequests_transactions_ID.yaml

@@ -64,7 +64,6 @@ put:
         schema:
           $ref: ../components/schemas/ThirdpartyRequestsTransactionsIDPutResponse.yaml
         example:
-          transactionId: '11111111-0000-0000-0000-000000000000'
           transactionRequestState: 'RECEIVED'
   responses:
     200:
@@ -106,7 +105,6 @@ patch:
         schema:
           $ref: ../components/schemas/ThirdpartyRequestsTransactionsIDPatchResponse.yaml
         example:
-          transactionId: '11111111-0000-0000-0000-000000000000'
           transactionRequestState: 'ACCEPTED'
           transactionState: 'COMMITTED'
   responses:

package/thirdparty/openapi3/paths/thirdpartyRequests_verifications.yaml

@@ -29,19 +29,6 @@ post:
             oneOf:
               - $ref: ../components/schemas/ThirdpartyRequestsVerificationsPostRequestFIDO.yaml
               - $ref: ../components/schemas/ThirdpartyRequestsVerificationsPostRequestGeneric.yaml
-        example:
-          verificationRequestId: '44444444-0000-0000-0000-000000000000'
-          challenge: '<base64 encoded binary - the encoded challenge>'
-          consentId: '8d34f91d-d078-4077-8263-2c0498dhbjr'
-          signedPayloadType: FIDO
-          signedPayload:
-            id: 45c-TkfkjQovQeAWmOy-RLBHEJ_e4jYzQYgD8VdbkePgM5d98BaAadadNYrknxgH0jQEON8zBydLgh1EqoC9DA
-            rawId: 45c+TkfkjQovQeAWmOy+RLBHEJ/e4jYzQYgD8VdbkePgM5d98BaAadadNYrknxgH0jQEON8zBydLgh1EqoC9DA==
-            response:
-              authenticatorData: SZYN5YgOjGh0NBcPZHZgW4/krrmihjLHmVzzuoMdl2MBAAAACA==
-              clientDataJSON: eyJ0eXBlIjoid2ViYXV0aG4uZ2V0IiwiY2hhbGxlbmdlIjoiQUFBQUFBQUFBQUFBQUFBQUFBRUNBdyIsIm9yaWdpbiI6Imh0dHA6Ly9sb2NhbGhvc3Q6NDIxODEiLCJjcm9zc09yaWdpbiI6ZmFsc2UsIm90aGVyX2tleXNfY2FuX2JlX2FkZGVkX2hlcmUiOiJkbyBub3QgY29tcGFyZSBjbGllbnREYXRhSlNPTiBhZ2FpbnN0IGEgdGVtcGxhdGUuIFNlZSBodHRwczovL2dvby5nbC95YWJQZXgifQ==
-              signature: MEUCIDcJRBu5aOLJVc/sPyECmYi23w8xF35n3RNhyUNVwQ2nAiEA+Lnd8dBn06OKkEgAq00BVbmH87ybQHfXlf1Y4RJqwQ8=
-            type: 'public-key'
   responses:
     202:
       $ref: ../components/responses/202.yaml

package/thirdparty/openapi3/paths/thirdpartyRequests_verifications_ID.yaml

@@ -11,6 +11,38 @@ parameters:
   - $ref: ../components/parameters/FSPIOP-Signature.yaml
   - $ref: ../components/parameters/FSPIOP-URI.yaml
   - $ref: ../components/parameters/FSPIOP-HTTP-Method.yaml
+get:
+  tags:
+    - thirdpartyRequests
+    - sampled
+  operationId: GetThirdpartyRequestsVerificationsById
+  summary: 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 
+  parameters:
+    #Headers
+    - $ref: ../components/parameters/Accept.yaml
+  responses:
+    202:
+      $ref: ../components/responses/202.yaml
+    400:
+      $ref: ../components/responses/400.yaml
+    401:
+      $ref: ../components/responses/401.yaml
+    403:
+      $ref: ../components/responses/403.yaml
+    404:
+      $ref: ../components/responses/404.yaml
+    405:
+      $ref: ../components/responses/405.yaml
+    406:
+      $ref: ../components/responses/406.yaml
+    501:
+      $ref: ../components/responses/501.yaml
+    503:
+      $ref: ../components/responses/503.yaml
 put:
   tags:
     - thirdpartyRequests

package/thirdparty/openapi3/thirdparty-dfsp-api.template.yaml

@@ -0,0 +1,53 @@
+openapi: 3.0.2
+info:
+  title: Mojaloop Third Party API (DFSP)
+  version: '1.0'
+  description: >
+    A Mojaloop API for DFSPs supporting Third Party functions.
+
+    DFSPs who want to enable Payment Initiation Service Providers
+    (PISPs) to perform actions on behalf of a DFSP's user should 
+    implement this API.
+
+    PISPs should implement the accompanying API - Mojaloop Third 
+    Party API (PISP) instead.
+  license:
+    name: Open API for FSP Interoperability (FSPIOP) (Implementation Friendly Version)
+    url: https://github.com/mojaloop/mojaloop-specification/blob/master/LICENSE.md
+servers:
+  - url: /
+paths:
+  /accounts/{ID}:
+    $ref: 'paths/accounts_ID.yaml'
+  /accounts/{ID}/error:
+    $ref: 'paths/accounts_ID_error.yaml'
+  /consentRequests:
+    $ref: 'paths/consentRequests.yaml'
+  /consentRequests/{ID}:
+    $ref: 'paths/consentRequests_ID.yaml'
+  /consentRequests/{ID}/error:
+    $ref: 'paths/consentRequests_ID_error.yaml'
+  /consents:
+    $ref: 'paths/consents.yaml'
+  /consents/{ID}:
+    $ref: 'paths/consents_ID.yaml'
+  /consents/{ID}/error:
+    $ref: 'paths/consents_ID_error.yaml'
+  /thirdpartyRequests/authorizations:
+    $ref: 'paths/thirdpartyRequests_authorizations.yaml'
+  /thirdpartyRequests/authorizations/{ID}:
+    $ref: 'paths/thirdpartyRequests_authorizations_ID.yaml'
+  /thirdpartyRequests/authorizations/{ID}/error:
+    $ref: 'paths/thirdpartyRequests_authorizations_ID_error.yaml'
+  /thirdpartyRequests/transactions:
+    $ref: 'paths/thirdpartyRequests_transactions.yaml'
+  /thirdpartyRequests/transactions/{ID}:
+    $ref: 'paths/thirdpartyRequests_transactions_ID.yaml'
+  /thirdpartyRequests/transactions/{ID}/error:
+    $ref: 'paths/thirdpartyRequests_transactions_ID_error.yaml'
+  /thirdpartyRequests/verifications:
+    $ref: 'paths/thirdpartyRequests_verifications.yaml'
+  /thirdpartyRequests/verifications/{ID}:
+    $ref: 'paths/thirdpartyRequests_verifications_ID.yaml'
+  /thirdpartyRequests/verifications/{ID}/error:
+    $ref: 'paths/thirdpartyRequests_verifications_ID_error.yaml'