OpenapiCaptable
Create investments
Records one investor's money into an open round. The round must be OPEN; investing into a closed one is refused.
POST /v1/captable/rounds/{id}/investments
| Address | https://api.hanzo.ai/v1/captable/rounds/{id}/investments |
| Method | POST |
| Operation | post_captable_rounds_by_id_investments |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Records one investor's money into an open round.
The round must be OPEN; investing into a closed one is refused. Where the round carries a price per share, the investment also issues the shares it buys and the answer names them.
Request
6 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
id | path | string | yes | ID is the round to invest in. The URL is the addressing authority — a path segment binds after the body and after the query — so the address decides which… |
amount | body | any | — | Amount is the money invested, in the round's own currency. |
comments | body | any | — | Comments is a free-text note kept with the investment. |
date | body | any | — | Date is when the investment was made, YYYY-MM-DD. |
id | body | string | — | ID is the round to invest in. The URL is the addressing authority — a path segment binds after the body and after the query — so the address decides which… |
stakeholderId | body | any | — | StakeholderID is the investor. |
Response
| Status | Body | Meaning |
|---|---|---|
201 | captableInvested | created |
201 body — 4 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
id | body | string | — | ID is the investment record's id. |
message | body | string | — | Message is the human sentence the cap table wrote. |
newShareId | body | string | — | NewShareID names the certificate the investment issued, when the round carries a price per share. |
success | body | boolean | — | Success is true when the investment was recorded. |
Failure carries the platform error shape — see Errors.
Examples
hanzo captable rounds investments <id>import { Configuration, CaptableApi } from 'hanzoai';
const api = new CaptableApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postCaptableRoundsByIdInvestments({ id: 'id', amount: "<amount>", comments: "<comments>" });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_rounds_by_id_investments(id='id', amount="<amount>", comments="<comments>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.CaptableAPI.PostCaptableRoundsByIdInvestments(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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_rounds_by_id_investments(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.CaptableApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new CaptableApi(client).postCaptableRoundsByIdInvestments();curl -X POST https://api.hanzo.ai/v1/captable/rounds/<id>/investments \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"amount": "<amount>",
"comments": "<comments>"
}'MCP reaches captable through the captable tool, which names its 31 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"
}
}
}'How is this guide?