/external/v1/security-admin/extend-end-date
See Blockchain Transaction Tracking for information on using orchestrationId and processId.
This route is used to update the end date of an offering.
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 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 "extendOfferingEndDate".
This property contains the transactional data information, i.e. which is the security where the end date is being extended
{"securityId":"USS3JKS01I00","signer":{"email":"[email protected]","name":"John Doe"}}The new date. Must be after end date.
2024-09-12T00:00:00.000ZDate-time string
2024-09-12T00:00:00.000ZDate string
1980-01-01Epoch timestamp (milliseconds)
1185106460000PUT /external/v1/security-admin/extend-end-date HTTP/1.1
Host:
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 146
{
"transactionData": {
"securityId": "USS3JKS01I00",
"signer": {
"email": "[email protected]",
"name": "John Doe"
}
},
"endDate": "2024-09-12T00:00:00.000Z"
}{
"processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
"orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf"
}