Create close

Closes one of the caller org's fundraising rounds, recording the close date and moving its status to CLOSED.

POST /v1/captable/rounds/{id}/close

Addresshttps://api.hanzo.ai/v1/captable/rounds/{id}/close
MethodPOST
Operationpost_captable_rounds_by_id_close
AuthAuthorization: Bearer $HANZO_API_KEY

Closes one of the caller org's fundraising rounds, recording the close date and moving its status to CLOSED. Only an OPEN round can be closed: a round that is already closed — like an id this org does not hold — is not found. Closing a round does not change what was invested in it.

Request

3 fields, body application/json (required).

FieldInTypeRequiredDescription
idpathstringyesID is the round to close.
closeDatebodyany—CloseDate is the date to record the round as closed on.
idbodystring—ID is the round to close.

Response

StatusBodyMeaning
200captable.captableUpdatedok
defaultproblem-detailsrefused

200 body — 2 fields.

FieldInTypeAlwaysDescription
messagebodystring—Message is the human sentence the cap table wrote, e.g. "Company updated".
successbodyboolean—Success is true when the update was applied.

Failure carries the platform error shape — see Errors.

Examples

hanzo captable rounds close <id>
import { Configuration, CaptableApi } from 'hanzoai';

const api = new CaptableApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postCaptableRoundsByIdClose({ id: 'id', closeDate: "<closeDate>", id: "<id>" });
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_close(id='id', close_date="<closeDate>", id="<id>")
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.CaptableAPI.PostCaptableRoundsByIdClose(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_rounds_by_id_close(&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).postCaptableRoundsByIdClose();
curl -X POST https://api.hanzo.ai/v1/captable/rounds/<id>/close \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "closeDate": "<closeDate>",
       "id": "<id>"
     }'

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?