Corporate Actions are events initiated by issuers of instruments to the investors who holds certain units of these instruments as holdings. These events give opportunities to the investors to receive benefits or take part in certain activities. These events could be
Cash Dividend (DVCA): Distribution of cash to shareholders, in proportion to their equity holding. Ordinary dividends are recurring and regular. Shareholder must take cash and may be offered a choice of currency.
- Dividend Option (DVOP): Distribution of a dividend to shareholders with a choice of benefit to receive. Shareholders may choose to receive shares or cash. To be distinguished from DRIP as the company creates new share capital in exchange for the dividend rather than investing the dividend in the market.
- Conversion (CONV): Conversion of securities (generally convertible bonds or preferred shares) into another form of securities (usually common shares) at a pre-stated price/ratio.
Corporate Action events can be categorized into two types: Mandatory events and Voluntary events.
- Mandatory events take effect automatically so that it is not necessary for the investors to respond;
- Voluntary events require investors to respond. Together with the events, companies usually provides several options to investors so that investors can decide which option to choose by an election.
An investor can also set Standing Instructions in advance so that election will be automatically made to choose the default options on specific instruments.
Get Active Events
Below is an example of how to get active events and their detailed information.
The response is equivalent to the Overview/Details views of Corporate Actions in SAXO TraderGo.
Similarly, you can get Past or Upcoming events by the below requests:
Create an Election
The event 8667626 above is allowed for election since it is an Active Voluntary event which has two options. Below is an example of how to elect the second option of Event 8667626.
The request is equivalent to the "Election ticket" in SAXO TraderGo.
Existing elections can be canceled by changing them into an empty array. Here an empty array stands for "No Option". Once the election has been cancelled, the ElectionStatus in the Holdings field of the event will be "NotElected" and the ElectedAmount will be 0.
A Holding means how many event-related shares a client has and what options a client has elected. The ElectionStatus is NotElected if a client hasn't made any election. Once elected, the ElectionStatus will be Elected and elected options will be included in the response.
Manage Standing Instructions
A client can create multiple standing instructions for automatic elections on specific accounts or instruments.
Below is an example of how to create a new standing instruction to elect "Receive securities" for all the Apple Inc. shares in all the accounts.
The request is equivalent to the "Add instruction" in SAXO TraderGo.
An existing standing instruction can be deleted but not updated. An investor can delete the old standing instruction and recreate a new one for modification. Below is an example of how to delete a standing instruction:
The request is equivalent to the "Delete standing instruction" in SAXO TraderGo.
Top Level Client: Get Events and Holdings of My End Clients
A top level client is usually a company who owns lots of end clients while the top level client itself doesn't trade. From the perspective of a top level client, an event can affect many end clients while each client has different holdings and makes different elections . Therefore a top level client needs to know
- What events are affecting end clients and how many clients are affected by each event. This is achievable by the /events endpoint.
- How many shares are Eligible for each client and what options have been made for each event. This is achievable by the /holdings endpoint.
Get Events of My End Clients
The below example shows as a top level client owning lots of end clients, how can I get all their Active events by using IncludeSubAccounts=true.
The response indicates that
- There are totally 71 Active events in the response
- The second event, whose EventId is 8740953, affects only 2 accounts of my end clients. The aggregated holdings of these accounts is 4000.
- The first event, whose EventId is 8772995, is affecting 42 accounts of my end clients. The aggregated holdings of these accounts is 2025.
- To find out the details these 42 or 2 accounts, it is necessary to make a further query to the /holdings endpoint
Get Holdings of My End Clients
The next step for the top level client is to find out who are the clients affected by each event and what are the status of them.
To continue the above example, in order to find out who owns the 2 accounts affected by event 8740953, a top level can query the /hodings endpoint as below:
The response lists the details of the two accounts affected by event 8740953. Their collective Amount is 4000 which equals to the EligibleHoldings in the response of the previous /events query.
Similarly, in order to know the details of the 42 accounts affected by event 8772995, the top level client needs to make a second query as below: