Inv - Mark Assets Batch as Wired
Throughout the API flows, an asset represents multiple shares, or a lot, of a given security. The investing organization can mark a batch of securities to indicate funds have been wired.
Details
/external/v1/primary/batch-mark-wired
Synopsis
This route is used to trigger the process to mark a list of confirmed assets of a given security as wired.
This should be called by the asset owner as the notification of the funds covering the investment being wired.
If the security is a money market fund, this should be called by the asset account owner.
This can be called for all security types except non-unitized security types with capital calls enabled.
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 if the security is in one of the following statuses: ["active","paused"].
This endpoint can be invoked if the assets in the payload are the following statuses: confirmed.
This endpoint can be invoked by organizations that have at least one of the following roles on this security: ["issuer","investor"].
This endpoint can't be invoked if the security is restricted.
This endpoint can be called by applications with access to scope "markSubscriptionWired".
This property contains the transactional data information, i.e. the security id to which all the asset ids in the list belong to
{"securityId":"USS3JKS01I00","signer":{"email":"[email protected]","name":"John Doe"}}
The list of the unique identifiers of the digital assets to apply action to.
The entries on this list need to be consistent with the security id in the transaction data
["USS3JKS01I00","US9QIMAOAS1Q"]
PUT /external/v1/primary/batch-mark-wired HTTP/1.1
Host:
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 152
{
"transactionData": {
"securityId": "USS3JKS01I00",
"signer": {
"email": "[email protected]",
"name": "John Doe"
}
},
"assetIds": [
"USS3JKS01I00",
"US9QIMAOAS1Q"
]
}
{
"processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
"orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf"
}
Last updated
Was this helpful?