Once an investor funds a capital call, that fact needs to be recorded in the Corastone portal. Here, an asset represents multiple shares, or a lot, of the corresponding security.
/external/v1/capital-events/{capitalEventId}/assets/fund
See Blockchain Transaction Tracking for information on using orchestrationId and processId.
This route is used to trigger the funding of the capital event by investors (specific to capital calls) on a batch of assets.
This should be called to let the issuer know when the investors meet their capital obligations
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","completed","approved_revert_to_active","closed"].
This endpoint can be invoked if the capital event is in one of the following statuses: ["active","closed"]
This endpoint can be invoked by organizations that have at least one of the following roles on this security: ["investor"].
This endpoint can be called by applications with access to scope "manageCapitalEvent".
The id that uniquely identifies the capital event on the ledger.
TEST5678This property contains the transactional data information, i.e. which is the security where the capital event is happening
{"securityId":"USS3JKS01I00","signer":{"email":"[email protected]","name":"John Doe"}}PUT /external/v1/capital-events/{capitalEventId}/assets/fund HTTP/1.1
Host:
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 271
{
"transactionData": {
"securityId": "USS3JKS01I00",
"signer": {
"email": "[email protected]",
"name": "John Doe"
}
},
"assetsData": [
{
"assetId": "US9QIMAOAS1Q",
"settlementData": {
"amount": 1000,
"date": "2024-09-12T00:00:00.000Z"
},
"extraData": {
"whatever": "Extra Data that is needed"
}
}
]
}{
"processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
"orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf"
}