AM/TA - Approve Tender Offer Price

Details

/external/v1/tender-offers/{tenderOfferId}/price/approve

Synopsis

Approve Tender Offer Price

put

This route is used to trigger the process to approve the tender offer price and total number of shares accepted. It triggers an asynchronous process that will persist this information on the blockchain, which can be monitored using the "Transactions API" endpoints. For self-managed funds (i.e. securities without any assigned fund admin) tender offer will be moved to the 'price_approved' state after the first call. If the asset manager that owns this security has a fund admin assigned to this offering, then both organizations need to call this endpoint one after the other. The first organization that calls this will move the tender offer to 'price_pending". After the second approval the tender offer will be moved to the 'price_approved' state and the process to apply the close price to all tender requests is triggered. 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 if the tender offer is in one of the following statuses: ["price_set","price_pending"]. 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 "manageTenderOffer".

Required scopes

This endpoint requires the following scopes:

• : manageTenderOffer

Authorizations

oauth2

OAuth2clientCredentialsRequired

Token URL:

Path parameters

tenderOfferIdanyRequired

The id that uniquely identifies the tender offer on the ledger.

Example: TEST6688

Body

application/json

processIdstringOptional

This is an externally provided id that can be used to identify the asynchronous process that will be triggered by this action. It is optional. If not provided the system will generate a unique id for this. If provided, it must have a v4 UUID format.

Example: 2159457f-0167-4e93-a969-9cf0db05e0bf

securityIdstringOptional

This is the security unique identifier on the ledger. It uniquely identifies a particular security on the blockchain. It is optional. Either "securityId" or "securityCorrelationData" must be provided, but not both.

Example: USS3JKS01I00

Responses

200

Successfully triggered the price approval of the tender offer

application/json

processIdstringRequired

This is used to uniquely identity a transaction process on this system.

Example: 2159457f-0167-4e93-a969-9cf0db05e0bf

orchestrationIdstringRequired

The orchestration id. It is used to uniquely identity a group of transactions that are being orchestrated following an action request.If a processId was passed as an input to the action, it will be returned on this property.

Example: 2159457f-0167-4e93-a969-9cf0db05e0bf

400

The following error codes can be returned: - GN0002 - IS0008 - IS0106 - TO0002 Please refer to the error code dictionary for the details of each error code.

application/json

401

The following error codes can be returned: - AU0001 - AU0003 Please refer to the error code dictionary for the details of each error code.

application/json

403

The following error codes can be returned: - AU0002 - IS0099 Please refer to the error code dictionary for the details of each error code.

application/json

404

The following error codes can be returned: - TO0001 Please refer to the error code dictionary for the details of each error code.

application/json

409

The following error codes can be returned: - IS0119 - IS0013 - IS0012 - IS0010 - IS0002 - IS0018 - IS0117 - TO0003 - TO0005 - TO0004 Please refer to the error code dictionary for the details of each error code.

application/json

put

/external/v1/tender-offers/{tenderOfferId}/price/approve

HTTPcURLJavaScriptPython

PUT /external/v1/tender-offers/{tenderOfferId}/price/approve HTTP/1.1
Authorization: Bearer YOUR_OAUTH2_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 217

{
  "signer": {
    "email": "[email protected]",
    "name": "John Doe"
  },
  "processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
  "securityId": "USS3JKS01I00",
  "securityCorrelationData": {
    "correlationId": "USS3JKS01I00",
    "orgId": "US9QIMA"
  }
}

{
  "processId": "2159457f-0167-4e93-a969-9cf0db05e0bf",
  "orchestrationId": "2159457f-0167-4e93-a969-9cf0db05e0bf"
}

Important Notes

• See Blockchain Transaction Tracking for information on using orchestrationId and processId.