This route is used to trigger the process to mark a list of assets of a given security as accepted.
This means the issuer has accepted the investments and the assets will move on to the next stage of the lifecycle.
This triggers an asynchronous process (the id of which is returned on the success response) to 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 are in one of the following statuses: ["created","remediation_pending","remediated","modified"].
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 "acceptSubscription".
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-accepted 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"
}