Add New History
Use this page when you need to know whether a route creates a new history entry or only saves data for later use.
⚠️
You can add new events to the history feed. You cannot rewrite past events through the TAP API.
Why two lists?
History entries are produced by the event poller after a contract transaction is mined. Routes that emit a contract event show up in history; routes that only write to MongoDB do not. Use the lists below to predict which side of the line a route falls on.
Routes that add new history
These routes submit an onchain transaction. After the poller processes the event (~20 s on Plume Mainnet), the entry appears in View History.
| Route | Resulting history |
|---|---|
POST /transactions/issuance/stock | New stock position |
POST /transactions/transfer/stock | Transfer and any balance position |
POST /transactions/cancel/stock | Cancellation |
POST /transactions/retract/stock | Retraction |
POST /transactions/reissue/stock | Reissuance |
POST /transactions/repurchase/stock | Repurchase |
POST /transactions/accept/stock | Acceptance |
POST /transactions/adjust/issuer/authorized-shares | Issuer authorized-share adjustment |
POST /transactions/adjust/stock-class/authorized-shares | Stock-class authorized-share adjustment |
Routes that only save data
These routes write a MongoDB record only. They never appear in history on their own.
| Route | Storage |
|---|---|
POST /transactions/issuance/equity-compensation | MongoDB equity-compensation record |
POST /transactions/issuance/convertible | MongoDB convertible record |
POST /stock-legend/create | MongoDB supporting record |
POST /stock-plan/create | MongoDB supporting record |
POST /valuation/create | MongoDB supporting record |
POST /vesting-terms/create | MongoDB supporting record |
Verify a new history entry
- Send the route.
- Wait for the poller (~20 s on Plume Mainnet).
- Fetch View History again and look for the new
date,security_id, andobject_type.