Create transfer

Moves shares from one stakeholder to another.

POST /v1/captable/shares/transfer

Addresshttps://api.hanzo.ai/v1/captable/shares/transfer
MethodPOST
Operationpost_captable_shares_transfer
AuthAuthorization: Bearer $HANZO_API_KEY

Moves shares from one stakeholder to another.

Omit quantity to transfer the whole certificate, which REASSIGNS it and mints no new share. Send a quantity below the amount held to SPLIT it — the source certificate keeps the remainder, and a split additionally requires certificateId for the new certificate, which must be unique in the company. A quantity outside 1..held is refused, so a transfer can never over-issue.

Both outcomes answer 200: a transfer records a movement between holders and mints no security of its own, which is why this is not a 201 the way an investment is.

Request

4 fields, body application/json (required).

FieldInTypeRequiredDescription
certificateIdbodyany—CertificateID names the NEW certificate a partial transfer issues, and is required for one — a partial transfer without it is refused 400.
quantitybodyany—Quantity is how many shares to move.
shareIdbodyany—ShareID is the certificate being transferred.
toStakeholderIdbodyany—ToStakeholderID is who receives them.

Response

StatusBodyMeaning
200captable.captableTransferredok
defaultproblem-detailsrefused

200 body — 4 fields.

FieldInTypeAlwaysDescription
messagebodystring—Message is the human sentence the cap table wrote, e.g. "Share transferred".
newShareIdbodystring—NewShareID names the certificate a PARTIAL transfer created.
successbodyboolean—Success is true when the transfer was applied.
transferredbodyinteger (int64)—Transferred is how many shares moved.

Failure carries the platform error shape — see Errors.

Examples

hanzo captable shares transfer
import { Configuration, CaptableApi } from 'hanzoai';

const api = new CaptableApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postCaptableSharesTransfer({ certificateId: "<certificateId>", quantity: "<quantity>" });
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_transfer(certificate_id="<certificateId>", quantity="<quantity>")
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.CaptableAPI.PostCaptableSharesTransfer(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_transfer(&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).postCaptableSharesTransfer();
curl -X POST https://api.hanzo.ai/v1/captable/shares/transfer \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "certificateId": "<certificateId>",
       "quantity": "<quantity>"
     }'

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?