Get doctypes

Returns one DocType definition — its fields, naming rule, permissions and lifecycle flags.

GET /v1/framework/doctypes/{name}

Addresshttps://api.hanzo.ai/v1/framework/doctypes/{name}
MethodGET
Operationget_framework_doctypes_by_name
AuthAuthorization: Bearer $HANZO_API_KEY

Returns one DocType definition — its fields, naming rule, permissions and lifecycle flags. Scoped to the caller's org, so another tenant's DocType of the same name is simply not found.

Request

1 field.

FieldInTypeRequiredDescription
namepathstringyesName is the DocType's ADDRESS — "module.name", e.g. "kb.page".

Response

StatusBodyMeaning
200framework.DocTypeok
defaultproblem-detailsrefused

200 body — 29 fields.

FieldInTypeAlwaysDescription
autonamebodystring—
createdAtbodyinteger (int64)—
fieldsbodyframework.DocField[]—
fields[].defaultbodystring—
fields[].fetchFrombodystring—
fields[].fieldnamebodystring—
fields[].fieldtypebodystring—
fields[].hiddenbodyboolean—
fields[].inListViewbodyboolean—
fields[].labelbodystring—
fields[].optionsbodystring—
fields[].readOnlybodyboolean—
fields[].reqdbodyboolean—
fields[].uniquebodyboolean—
immutablebodyboolean—
isSinglebodyboolean—
isSubmittablebodyboolean—
modulebodystring—
namebodystring—
permissionsbodyframework.DocPerm[]—
permissions[].cancelbodyboolean—
permissions[].createbodyboolean—
permissions[].deletebodyboolean—
permissions[].readbodyboolean—
permissions[].rolebodystring—
permissions[].submitbodyboolean—
permissions[].writebodyboolean—
titleFieldbodystring—
updatedAtbodyinteger (int64)—

Failure carries the platform error shape — see Errors.

Examples

hanzo framework doctypes get <name>
import { Configuration, FrameworkApi } from 'hanzoai';

const api = new FrameworkApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getFrameworkDoctypesByName({ name: 'name' });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import FrameworkApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = FrameworkApi(client).get_framework_doctypes_by_name(name='name')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.FrameworkAPI.GetFrameworkDoctypesByName(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, framework_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = framework_api::get_framework_doctypes_by_name(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.FrameworkApi;

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

var result = new FrameworkApi(client).getFrameworkDoctypesByName();
curl https://api.hanzo.ai/v1/framework/doctypes/<name> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches framework through the framework tool, which names its 14 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": "get_framework_by_doctype"
         }
       }
     }'

Framework API · All Hanzo APIs · Interactive reference

Was this page useful?