AM - Reject Assignment to Exclusive Offering
Details
/external/v1/exclusivity/reject
Synopsis
This route is used for an investing organization to reject the assignment to an exclusive offering (i.e. when the exclusivity type of the offering is set to "private").
This can be invoked if the current organization has been assigned as an investing org to this particular security.
Use this endpoint to express that you will not be performing investments in this security. This can be reverted by using the "accept" endpoint.
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 called by applications with access to scope "manageExclusivityOptions".
For registered products with multiple share classes, use this as a filter to specify to which share classes the action applies to.
If not provided, then all will be affected the same way.
This should only be provided if the security has multiple share classes (e.g. security with multiple share classes and accepting/rejecting the assignment to just a subset of them).
["USS3JKS01I00"]
This property contains the transactional data information, i.e. which is the security being affected by this action
{"securityId":"USS3JKS01I00","signer":{"email":"[email protected]","name":"John Doe"}}
PUT /external/v1/exclusivity/reject HTTP/1.1
Host:
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 150
{
"shareClassSecurityIds": [
"USS3JKS01I00"
],
"transactionData": {
"securityId": "USS3JKS01I00",
"signer": {
"email": "[email protected]",
"name": "John Doe"
}
}
}
{
"processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
"orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf"
}
Important Notes
Revert using the /accept endpoint.
See Blockchain Transaction Tracking for information on using orchestrationId and processId.
Last updated
Was this helpful?