Skip to Content

History Routes

The poller writes history rows when it sees a stock transaction onchain, whether the server key or the issuer’s wallet sent it. Records saved only in MongoDB never add rows, and the API has no route to edit or delete past rows.

Writes that add rows

WriteRows
Issue stock: POST /transactions/issuance/stock, or Issue stock in the appOne StockIssuance
Transfer stock: POST /transactions/transfer/stock, or Transfer in the appFor each security the transfer uses: a StockIssuance for the recipient, a StockIssuance for the sender’s remainder if the security was only partly used, and a StockTransfer
POST /transactions/cancel/stockA StockCancellation, plus a StockIssuance for the remainder of a partial cancel
POST /transactions/repurchase/stockA StockRepurchase, plus a StockIssuance for the remainder of a partial repurchase
POST /transactions/retract/stockOne StockRetraction
POST /transactions/reissue/stockOne StockReissuance
POST /transactions/accept/stockOne StockAcceptance
POST /transactions/adjust/issuer/authorized-sharesOne IssuerAuthorizedSharesAdjustment
POST /transactions/adjust/stock-class/authorized-sharesOne StockClassAuthorizedSharesAdjustment

Writes that add no rows

WriteWhat happens instead
Create a stakeholder or stock class, from the API or the appThe poller marks the record is_onchain_synced.
POST /stakeholder/add-wallet, POST /stakeholder/remove-walletThe change is onchain only; MongoDB doesn’t store wallets.
POST /issuer/create, POST /issuer/registerThe poller starts following the cap table.
Stock legends, stock plans, valuations, vesting terms, equity compensation, and convertiblesSaved in MongoDB only.
mintSharesAuthorized and mintActivePositions, called directly on the contractSeeded positions create no transactions, so they never appear in history.

What’s next?

Last updated on