List documents

Returns the org's generated documents, newest first, WITHOUT their rendered content — fetch one document to read its body.

GET /v1/legal/documents

Addresshttps://api.hanzo.ai/v1/legal/documents
MethodGET
Operationget_legal_documents
AuthAuthorization: Bearer $HANZO_API_KEY

Returns the org's generated documents, newest first, WITHOUT their rendered content — fetch one document to read its body.

The response is marked no-store: these records name the counterparties an org is contracting with, and must not sit in a shared cache.

Request

1 field.

FieldInTypeRequiredDescription
limitqueryinteger—Limit bounds the page.

Response

StatusBodyMeaning
200legal.documentPageok
defaultproblem-detailsrefused

200 body — 12 fields.

FieldInTypeAlwaysDescription
databodylegal.documentSummary[]—Data are the documents, WITHOUT their rendered content — fetch one to read it.
data[].categorybodystring—Category is the template's category: formation, equity, ops or sales.
data[].createdAtbodyinteger (int64)—CreatedAt is when the document was generated, in unix seconds.
data[].esignProviderbodystring—EsignProvider names the e-signature provider handling it, absent until a signature has been requested.
data[].idbodystring—ID is the document's server-minted handle, "doc_"-prefixed.
data[].signedAtbodyinteger (int64)—SignedAt is when the provider reported completion, in unix seconds.
data[].statusbodystring—Status is the lifecycle state: draft, out_for_signature, signed or voided.
data[].templateIdbodystring—TemplateID is the template it was rendered from.
data[].templateVersionbodyinteger (int64)—TemplateVersion is WHICH version of that template rendered it, so the document is reproducible and auditable.
data[].titlebodystring—Title is the document's title, inherited from the template.
data[].updatedAtbodyinteger (int64)—UpdatedAt is when it last changed, in unix seconds.
disclaimerbodystring—Disclaimer is the boundary made visible on the wire.

Failure carries the platform error shape — see Errors.

Examples

hanzo legal documents list
import { Configuration, LegalApi } from 'hanzoai';

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

resp, _, err := client.LegalAPI.GetLegalDocuments(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::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::get_legal_documents(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.LegalApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new LegalApi(client).getLegalDocuments();
curl https://api.hanzo.ai/v1/legal/documents \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches legal through the legal tool, which names its 10 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_legal_documents"
         }
       }
     }'

Legal API · All Hanzo APIs · Interactive reference

Was this page useful?