Create shares

Issues a share certificate to a stakeholder.

POST /v1/captable/shares

Captable → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/captable/shares`
Method	`POST`
Operation	`post_captable_shares`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Issues a share certificate to a stakeholder.

The certificate id must be UNIQUE within the company — a duplicate is refused 409, not silently merged — and both the stakeholder and the share class must belong to this company, so an id from another tenant is a 400 rather than a cross-company issuance.

Request

17 fields, body application/json (required).

Field	In	Type	Required	Description
`boardApprovalDate`	body	any	—	BoardApprovalDate is when the board approved the issuance, YYYY-MM-DD.
`capitalContribution`	body	any	—	CapitalContribution is cash paid for the shares.
`certificateId`	body	any	—	CertificateID is the certificate number.
`cliffYears`	body	any	—	CliffYears is how long before ANY of the grant vests.
`companyLegends`	body	any[]	—	CompanyLegends are the restrictive legends printed on the certificate.
`debtCancelled`	body	any	—	DebtCancelled is debt forgiven as consideration.
`ipContribution`	body	any	—	IPContribution is intellectual property assigned as consideration, valued in the company's currency.
`issueDate`	body	any	—	IssueDate is when the shares were issued, YYYY-MM-DD.
`otherContributions`	body	any	—	OtherContributions is any other consideration, valued in the company's currency.
`pricePerShare`	body	any	—	PricePerShare is what was paid per share.
`quantity`	body	any	—	Quantity is how many shares to issue.
`rule144Date`	body	any	—	Rule144Date is when the Rule 144 holding period starts, YYYY-MM-DD.
`shareClassId`	body	any	—	ShareClassID is the class being issued.
`stakeholderId`	body	any	—	StakeholderID is who receives the shares.
`status`	body	any	—	Status is ACTIVE, DRAFT, SIGNED or PENDING.
`vestingStartDate`	body	any	—	VestingStartDate is when vesting begins, YYYY-MM-DD.
`vestingYears`	body	any	—	VestingYears is the total vesting period.

Response

Status	Body	Meaning
`201`	captable.captableCreated	created
`default`	problem-details	refused

201 body — 3 fields.

Field	In	Type	Always	Description
`id`	body	string	—	ID is the created row's id.
`message`	body	string	—	Message is the human sentence the cap table wrote, e.g. "Share issued".
`success`	body	boolean	—	Success is true when the row was written.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo captable shares create

.ts

.py

.go

.rs

.java

import { Configuration, CaptableApi } from 'hanzoai';

const api = new CaptableApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postCaptableShares({ boardApprovalDate: "<boardApprovalDate>", capitalContribution: "<capitalContribution>" });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import CaptableApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = CaptableApi(client).post_captable_shares(board_approval_date="<boardApprovalDate>", capital_contribution="<capitalContribution>")

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.CaptableAPI.PostCaptableShares(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, captable_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = captable_api::post_captable_shares(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.CaptableApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new CaptableApi(client).postCaptableShares();

curl -X POST https://api.hanzo.ai/v1/captable/shares \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "boardApprovalDate": "<boardApprovalDate>",
       "capitalContribution": "<capitalContribution>"
     }'

MCP reaches captable through the captable tool, which names its 30 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_captable_classes"
         }
       }
     }'

Captable API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousCreate transfer NextCreate stakeholders