Skip to main content

Shareholder Updates

Send up to 50 shareholder updates per request, scoped to one eventId. Use it only for Voluntary Corporate Actions events where VOTR captures shareholder elections.

How it works​

  1. Send all shareholders who hold shares with POST /shareholders. No changes to that API.
  2. Until the election cutoff, keep sending changes with POST /shareholders/updates, so VOTR can deliver to new shareholders and capture or flag their elections.
What happenedtransactionTypetotalShares
Existing account bought moreBUYNew total settled position
Existing account sold someSELLRemaining settled position
Existing account sold everythingSELL0
New shareholder boughtBUYTheir settled position. Send all shareholder data, same as POST /shareholders

Tips​

  • transactionType is required on every record. Everything else follows the same rules as POST /shareholders.
  • Send the full record when you have it. All POST /shareholders fields are accepted, for new and existing shareholders.
  • totalShares is the total after the change, not the number of shares bought or sold.
  • Send only accounts that changed. Do not resend the whole list.
  • Election cutoff. After the event's election cutoff you'll get 403 and updates are no longer accepted.

Data rules​

  • Settled data only. Broker-dealers must send settled positions only.
  • Elections are not adjusted. If a shareholder submits an election and then buys or sells, VOTR does not add to or reduce the election. VOTR flags it for review.
  • Send valid data. VOTR does not check records for data issues, for example a BUY where totalShares goes down. Broker-dealers are responsible for sending valid data.
  • One account number, one shareholder. Each account number must always belong to the same shareholder. A duplicate account number for the same CUSIP, or the same account number used by two different brokers, causes data and reporting issues.
Loading playground…