FeaturesManage Cap TableAdd Supporting Records

Add Supporting Records

When to use this page

Use this page when the stock class and stakeholder already exist and you need the supporting records around them.

Use Create Stock Class and Create Stakeholder for the first create flow.

Save a stock legend or stock plan

Use POST /stock-legend/create to save reusable legend text.

Use POST /stock-plan/create to save plan details that later equity compensation issuances can reference.

{
    "issuerId": "<YOUR_ISSUER_ID>",
    "data": {
        "plan_name": "Transfer Agent Protocol 2026 Plan",
        "board_approval_date": "2026-01-15",
        "stockholder_approval_date": "2026-01-20",
        "initial_shares_reserved": "1000000",
        "default_cancellation_behavior": "RETURN_TO_POOL",
        "stock_class_id": "<YOUR_STOCK_CLASS_ID>",
        "comments": []
    }
}

Use Save Valuations and Terms for fuller examples of both create routes.

Add or remove a stakeholder wallet

Use POST /stakeholder/add-wallet or POST /stakeholder/remove-wallet with this body:

{
    "id": "<YOUR_STAKEHOLDER_ID>",
    "wallet": "<YOUR_WALLET_ADDRESS>"
}

Both routes return "Success" when the wallet update is accepted. POST /stakeholder/add-wallet can also return "Wallet already added".

Read the records back

  • GET /stock-class/id/:id returns the stock class summary.
  • GET /stock-class/total-number returns the stock class count.
  • GET /stakeholder/id/:id returns the stakeholder summary.
  • GET /stakeholder/issuer_assigned_id/:id
  • GET /stakeholder/issuer/:issuerId/issuer_assigned_id/:id
  • GET /stakeholder/wallet/:address
  • GET /stakeholder/total-number
  • GET /stock-legend/id/:id and GET /stock-legend/total-number
  • GET /stock-plan/id/:id and GET /stock-plan/total-number

If you created a legend or plan, read it back by ID. If you changed a wallet, read the stakeholder by wallet address.

What to do next

Use Issue and Accept Stock.