AM/TA - Request Transfer Remediation

Details

/external/v1/transfer/{transferId}/request-remediation

Synopsis

Request Transfer Remediation

put

This route is used to trigger a remediation request of the transfer details to the recipient investor organization. Asset manager that owns this security or fund admins assigned to this offering can execute this action, then once this call is completed the transfer will be marked as pending remediation on the ledger and the requesting organization will be able to amend the transfer request (e.g. provide further documents, amend ammounts, provide more details about the new investor/account). It triggers an asynchronous process that will persist this information on the blockchain, which can be monitored using the "Transactions API" endpoints. This endpoint can be invoked by organizations that have at least one of the following roles on this security: ["issuer","service_provider"]. This endpoint can be invoked if the security is in one of the following statuses: ["active","completed","approved_revert_to_active","closed"]. This endpoint can be invoked if the transfer is in one of the following statuses: ["created","remediated"]. This endpoint can't be invoked if the security is restricted. This endpoint can be called by applications with access to scope "manageTransfer"

Required scopes

This endpoint requires the following scopes:

• : manageTransfer

Authorizations

oauth2

OAuth2clientCredentialsRequired

Token URL:

Path parameters

transferIdanyRequired

The id that uniquely identifies the transfer on the ledger.

Example: TEST0000

Body

application/json

Responses

200

Successfully triggered the request for transfer data remediation.

application/json

processIdstringRequired

This is used to uniquely identity a transaction process on this system.

Example: 2159457f-0167-4e93-a969-9cf0db05e0bf

orchestrationIdstringRequired

The orchestration id. It is used to uniquely identity a group of transactions that are being orchestrated following an action request.If a processId was passed as an input to the action, it will be returned on this property.

Example: 2159457f-0167-4e93-a969-9cf0db05e0bf

transferIdstringRequired

The id that uniquely identifies the transfer on the ledger.

Example: US9QIMAOAS1Q

fileIdsstring[]Required

The created document(s) file ID(s). Each ID uniquely identifies a file on the ledger.

Example: ["US9QIFILE1","US9QIFILE2"]

400

The following error codes can be returned: - GN0002 - IS0008 - IS0106 - TR0002 - TR0043 Please refer to the error code dictionary for the details of each error code.

application/json

401

The following error codes can be returned: - AU0001 - AU0003 Please refer to the error code dictionary for the details of each error code.

application/json

403

The following error codes can be returned: - AU0002 - IS0099 Please refer to the error code dictionary for the details of each error code.

application/json

404

The following error codes can be returned: - IS0009 - TR0001 - OG0001 Please refer to the error code dictionary for the details of each error code.

application/json

409

The following error codes can be returned: - IS0119 - IS0063 - IS0013 - IS0002 - IS0012 - TR0003 - TR0006 - TR0004 Please refer to the error code dictionary for the details of each error code.

application/json

put

/external/v1/transfer/{transferId}/request-remediation

HTTPcURLJavaScriptPython

PUT /external/v1/transfer/{transferId}/request-remediation HTTP/1.1
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 394

{
  "transactionData": {
    "securityId": "USS3JKS01I00",
    "signer": {
      "email": "[email protected]",
      "name": "John Doe"
    }
  },
  "rejectReason": {
    "reason": [
      {
        "message": "reject reason",
        "category": "EC006",
        "documentWithIssues": [
          {
            "document": {
              "fileId": "FILE3JUS03I04"
            },
            "pages": [
              {
                "pageNumber": 1,
                "description": "The first page has an invalid signature"
              }
            ]
          }
        ]
      }
    ],
    "extraData": {
      "externalId": "123456789",
      "some": "Custom Property"
    }
  }
}

{
  "processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
  "orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
  "transferId": "US9QIMAOAS1Q",
  "fileIds": [
    "US9QIFILE1",
    "US9QIFILE2"
  ],
  "referenceData": {
    "account": {
      "accountId": "US9QIMAOAS1Q",
      "custodian": {
        "custodianId": "US9ZIMAOAS1Q"
      }
    },
    "investors": [
      {
        "investorId": "US9QIM123S1Q"
      }
    ]
  }
}

Important Notes

• See Blockchain Transaction Tracking for information on using orchestrationId and processId.