Records a filing of one or more of the org's documents with a state or agency,…
Records a filing of one or more of the org's documents with a state or agency, and returns the tracking record.
POST /v1/legal/filings
| Address | https://api.hanzo.ai/v1/legal/filings |
| Method | POST |
| Operation | post_legal_filings |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Records a filing of one or more of the org's documents with a state or agency, and returns the tracking record.
It is a TRACKING record, not an autonomous filing. With no filing partner wired the honest status is "manual" and the note says so: the documents were generated for signature, and the org files them through its registered agent. Nothing here invents a filing id it does not have.
Every document id must belong to the caller's org; one that does not is a 404 naming it, so a filing can never reach across tenants.
Request
2 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
documentIds | body | string[] | — | DocumentIDs are the documents to file. |
jurisdiction | body | string | — | Jurisdiction is the state or agency the filing is for, e.g. |
Response
| Status | Body | Meaning |
|---|---|---|
201 | filingReply | created |
201 body — 11 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
disclaimer | body | string | — | Disclaimer is the boundary made visible on the wire. |
filing | body | legalFiling | — | |
filing.createdAt | body | integer | — | |
filing.documentIds | body | string[] | — | |
filing.id | body | string | — | |
filing.jurisdiction | body | string | — | |
filing.note | body | string | — | |
filing.org | body | string | — | |
filing.provider | body | string | — | |
filing.status | body | string | — | |
filing.updatedAt | body | integer | — |
Failure carries the platform error shape — see Errors.
Examples
hanzo legal filings createimport { Configuration, LegalApi } from 'hanzoai';
const api = new LegalApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postLegalFilings({ documentIds: ["<documentIds>"], jurisdiction: "<jurisdiction>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import LegalApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = LegalApi(client).post_legal_filings(document_ids=["<documentIds>"], jurisdiction="<jurisdiction>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.LegalAPI.PostLegalFilings(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, legal_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = legal_api::post_legal_filings(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.LegalApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new LegalApi(client).postLegalFilings();curl -X POST https://api.hanzo.ai/v1/legal/filings \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"documentIds": [
"<documentIds>"
],
"jurisdiction": "<jurisdiction>"
}'The door reaches legal through the legal tool, which names its 11 operations with its own verbs — this one among them, under a name only the door 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_legal_documents"
}
}
}'How is this guide?