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.

Routes that add new history

These routes add new history entries.

• Stock actions:
  • POST /transactions/issuance/stock
  • POST /transactions/transfer/stock
  • POST /transactions/cancel/stock
  • POST /transactions/retract/stock
  • POST /transactions/reissue/stock
  • POST /transactions/repurchase/stock
  • POST /transactions/accept/stock
• Authorized share adjustments:
  • POST /transactions/adjust/issuer/authorized-shares
  • POST /transactions/adjust/stock-class/authorized-shares

Routes that only save data

These routes save data for later use but do not add history on their own.

• Equity compensation and convertibles:
  • POST /transactions/issuance/equity-compensation
  • POST /transactions/issuance/convertible
• Supporting records:
  • POST /stock-legend/create
  • POST /stock-plan/create
  • POST /valuation/create
  • POST /vesting-terms/create

How to verify a new history entry

• If the route changes holdings or authorized share counts, it should appear in history.
• If the route only saves a supporting input, it will not appear there by itself.

1. Send the route.
2. Wait for it to be processed.
3. Fetch GET /historical-transactions/issuer-id/<YOUR_ISSUER_ID> again.
4. Look for the new date, security_id, and transaction entry.

What’s next?

Use Transfer, Cancel, and Reissue Stock for routes that add new history. Use Save Equity Compensation and Convertibles for routes that save data without adding history.