The first step in the flow for a capital call or distribution is to create a capital event.
securityId: uniquely identifies the fund/offering. See Managing the SecurityId.
See Blockchain Transaction Tracking for information on using orchestrationId and processId.
This route is used to trigger the creation of a capital event (capital call or distribution) on the blockchain for a particular security.
It triggers an asynchronous process that will persist this information on the blockchain, which can be monitored using the "Transactions API" endpoints.
This will trigger either 1 or 2 transactions depending on the input (if assetDetails property is passed then it will be 2 transactions)
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 by organizations that have at least one of the following roles on this security: ["issuer","service_provider"].
This endpoint can't be invoked if the security is restricted.
This endpoint can be called by applications with access to scope "manageCapitalEvent".
This property contains the transactional data information, i.e. which is the security where the capital event is being created
{"securityId":"USS3JKS01I00","signer":{"email":"[email protected]","name":"John Doe"}}This property contains the details of the capital event that is to be created
{"type":"capitalCall","endDate":"2024-09-12T00:00:00.000Z","amountCalled":100000,"expenses":2000,"breakdown":[{"category":{"bookedCategoryId":"USS3JKS01I00","data":{"type":"investments","flowType":"againstCommitment","extraData":{"some":"Custom Data"}}},"amount":90000,"extraData":{"some":"Global data"}},{"category":{"data":{"type":"managementFeeInsideCommitment","flowType":"againstCommitment"}},"amount":10000},{"category":{"data":{"type":"managementFeeOutsideCommitment","flowType":"expenses","extraData":{"other":"Specific Data field"}}},"amount":2000},{"category":{"categoryId":"USS3JKS01I00"},"amount":4000}]}This is the booked unique identifier of the capital event. It is optional. If not provided, a new unique identifier will be generated.
USS3JKS01I00POST /external/v1/capital-events HTTP/1.1
Host:
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 776
{
"transactionData": {
"securityId": "USS3JKS01I00",
"signer": {
"email": "[email protected]",
"name": "John Doe"
}
},
"eventData": {
"type": "capitalCall",
"endDate": "2024-09-12T00:00:00.000Z",
"amountCalled": 100000,
"expenses": 2000,
"breakdown": [
{
"category": {
"bookedCategoryId": "USS3JKS01I00",
"data": {
"type": "investments",
"flowType": "againstCommitment",
"extraData": {
"some": "Custom Data"
}
}
},
"amount": 90000,
"extraData": {
"some": "Global data"
}
},
{
"category": {
"data": {
"type": "managementFeeInsideCommitment",
"flowType": "againstCommitment"
}
},
"amount": 10000
},
{
"category": {
"data": {
"type": "managementFeeOutsideCommitment",
"flowType": "expenses",
"extraData": {
"other": "Specific Data field"
}
}
},
"amount": 2000
},
{
"category": {
"categoryId": "USS3JKS01I00"
},
"amount": 4000
}
]
},
"bookedCapitalEventId": "USS3JKS01I00"
}{
"processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
"orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
"capitalEventId": "US9QIMAOAS1Q",
"breakdownCategoriesIds": [
"USS3JKS01I00"
]
}