This route is used to update the value of the isRepLetterProvided field for the organization on the exclusivity list.
This should only be triggered by the organization that owns the security.
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".
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"}}The id of the organization. Used to uniquely identify the organization on the ledger
US9QIMASet this value to true if the issuer of the security has a rep letter from the distribution partner being assigned to the exclusivity list.
falseExample: truePUT /external/v1/exclusivity/update-rep-letter-provided HTTP/1.1
Host:
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 154
{
"transactionData": {
"securityId": "USS3JKS01I00",
"signer": {
"email": "[email protected]",
"name": "John Doe"
}
},
"orgId": "US9QIMA",
"isRepLetterProvided": true
}{
"processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
"orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf"
}