AM - Create and Start Tender Offer
Details
/external/v1/tender-offers/start
Synopsis
This route is used to trigger the creation and start of a tender offer on the blockchain for a particular security.
It is reserved for self-managed funds, i.e. securities without assigned fund admins.
It combines 2 actions (create and approve) so once this call is completed, the tender offer will be marked as active on the ledger.
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"].
This endpoint can't be invoked if the security is restricted.
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 "manageTenderOffer".
This property contains the transactional data information, i.e. which is the security where the tender offer is being created
{"securityId":"USS3JKS01I00","signer":{"email":"[email protected]","name":"John Doe"}}
This property contains the tender offer data
{"startDate":"2024-09-12T00:00:00.000Z","cutOffDate":"2024-09-12T00:00:00.000Z","closeDate":"2024-09-12T00:00:00.000Z","settlementDate":"2024-09-12T00:00:00.000Z"}
This is the booked unique identifier of the tender offer. It is optional. If not provided, a new unique identifier will be generated.
USS3JKS01I00
POST /external/v1/tender-offers/start HTTP/1.1
Host:
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 328
{
"transactionData": {
"securityId": "USS3JKS01I00",
"signer": {
"email": "[email protected]",
"name": "John Doe"
}
},
"tenderOfferData": {
"startDate": "2024-09-12T00:00:00.000Z",
"cutOffDate": "2024-09-12T00:00:00.000Z",
"closeDate": "2024-09-12T00:00:00.000Z",
"settlementDate": "2024-09-12T00:00:00.000Z"
},
"bookedTenderOfferId": "USS3JKS01I00"
}
{
"processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
"orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
"tenderOfferId": "US9QIMAOAS1Q"
}
Important Notes
See Blockchain Transaction Tracking for information on using orchestrationId and processId.
\
Last updated
Was this helpful?