Update classes

Replaces one share class's terms.

PATCH /v1/captable/classes/{id}

Captable → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/captable/classes/{id}`
Method	`PATCH`
Operation	`patch_captable_classes_by_id`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Replaces one share class's terms.

It is a full REPLACE and not a merge, despite the PATCH: every field is written as sent, so a field omitted is written empty rather than left alone. Send the whole class. The method is PATCH because the resource is addressed by id, not because the body is partial — and getting that backwards silently blanks terms every later issuance prices against.

Request

15 fields, body application/json (required).

Field	In	Type	Required	Description
`id`	path	string	yes	ID addresses the resource.
`boardApprovalDate`	body	any	—	BoardApprovalDate is when the board approved the class, YYYY-MM-DD.
`classType`	body	any	—	ClassType is COMMON or PREFERRED.
`conversionRights`	body	any	—	ConversionRights is CONVERTS_TO_FUTURE_ROUND or CONVERTS_TO_SHARE_CLASS_ID.
`convertsToShareClassId`	body	any	—	ConvertsToShareClassID names the class this one converts into.
`id`	body	string	—	ID addresses the resource.
`initialSharesAuthorized`	body	any	—	InitialSharesAuthorized is how many shares this class may issue.
`liquidationPreferenceMultiple`	body	any	—	LiquidationPreferenceMultiple is the multiple of invested capital paid out before junior classes — 1 for a 1x preference.
`name`	body	any	—	Name is the share class's name, e.g. "Series A Preferred".
`parValue`	body	any	—	ParValue is the nominal per-share value on the certificate, in the company's currency.
`participationCapMultiple`	body	any	—	ParticipationCapMultiple caps participation after the preference is paid, as a multiple of invested capital.
`pricePerShare`	body	any	—	PricePerShare is the issue price for this class, in the company's currency.
`seniority`	body	any	—	Seniority orders liquidation preference: LOWER is more senior, so 1 is paid before 2.
`stockholderApprovalDate`	body	any	—	StockholderApprovalDate is when the stockholders approved it, YYYY-MM-DD.
`votesPerShare`	body	any	—	VotesPerShare is how many votes one share of this class carries.

Response

Status	Body	Meaning
`200`	captable.captableUpdated	ok
`default`	problem-details	refused

200 body — 2 fields.

Field	In	Type	Always	Description
`message`	body	string	—	Message is the human sentence the cap table wrote, e.g. "Company updated".
`success`	body	boolean	—	Success is true when the update was applied.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo captable classes update <id>

.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.patchCaptableClassesById({ id: 'id', boardApprovalDate: "<boardApprovalDate>", classType: "<classType>" });

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).patch_captable_classes_by_id(id='id', board_approval_date="<boardApprovalDate>", class_type="<classType>")

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

resp, _, err := client.CaptableAPI.PatchCaptableClassesById(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::patch_captable_classes_by_id(&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).patchCaptableClassesById();

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

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?

PreviousList summary NextUpdate stakeholders