Publish puts an item on the caller org's trust centre and answers with it.

POST /v1/dataroom/trust/artifacts

Dataroom → · All API references → · Six flows, four surfaces →


Address	`https://api.hanzo.ai/v1/dataroom/trust/artifacts`
Method	`POST`
Operation	`post_dataroom_trust_artifacts`
Auth	`Authorization: Bearer $HANZO_API_KEY`

The item is GATED unless it says otherwise, so a kind nobody has thought of yet arrives private and someone has to release it deliberately — that default is what keeps an auditor's report from becoming readable because a field went unset. An item whose attester is "auditor" cannot be public at all: the database refuses the pair, so no path through this API can publish one.

A file is optional and is uploaded FIRST, through POST /v1/dataroom/documents, then named here — the data room is the one place bytes enter, so a trust centre document is an ordinary data-room document and inherits its storage, its grants and its page-by-page access record. A gated item that has a file is added to the org's release room, which is what lets a party be granted the whole gated tier in one link.

Only an admin of the org may call it.

Request

8 fields, body application/json (required).

Field	In	Type	Required	Description
`attester`	body	string	—	Attester is who vouched for it: "self" for anything the org states itself, or "auditor" for anything an independent auditor put their name to.
`body`	body	string	—	Body is the item's content for the kinds that are text rather than a file: an article, a subprocessor entry, a dated note.
`document`	body	string	—	Document is a data-room document holding the item's bytes, uploaded first through POST /v1/dataroom/documents. Optional: an item can be content with no file.
`framework`	body	string	—	Framework is the standard it speaks to.
`kind`	body	string	—	Kind is what the item is: report, letter, policy, questionnaire, subprocessor, article or update.
`name`	body	string	—	Name is the item's title.
`summary`	body	string	—	Summary is a line about it.
`tier`	body	string	—	Tier is who may read it: "public" or "gated".

Response

Status	Body	Meaning
`200`	trustItemView	ok

200 body — 12 fields.

Field	In	Type	Always	Description
`attester`	body	string	—	Attester is who vouched for it: self or auditor.
`body`	body	string	—	Body is the item's content for the kinds that are text rather than a file.
`createdAt`	body	integer	—	CreatedAt is when it was published, in unix milliseconds.
`document`	body	string	—	Document is the data-room document holding its bytes, empty when it has none.
`framework`	body	string	—	Framework is the standard it speaks to, when it speaks to one.
`id`	body	string	—	ID addresses the item.
`kind`	body	string	—	Kind is what it is.
`name`	body	string	—	Name is its title.
`retired`	body	boolean	—	Retired is whether it has been withdrawn. A retired item is absent from the public centre and cannot be granted; it is kept because a grant already made over…
`summary`	body	string	—	Summary is a line about it.
`tier`	body	string	—	Tier is public or gated.
`updatedAt`	body	integer	—	UpdatedAt is when it last changed, in unix milliseconds.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

import { Configuration, DataroomApi } from 'hanzoai';

const api = new DataroomApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postDataroomTrustArtifacts({ attester: "<attester>", body: "<body>" });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import DataroomApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = DataroomApi(client).post_dataroom_trust_artifacts(attester="<attester>", body="<body>")

cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)

resp, _, err := client.DataroomAPI.PostDataroomTrustArtifacts(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_cloud::apis::{configuration::Configuration, dataroom_api};

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

let result = dataroom_api::post_dataroom_trust_artifacts(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.DataroomApi;

ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));

var result = new DataroomApi(client).postDataroomTrustArtifacts();

The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

curl -X POST https://api.hanzo.ai/v1/dataroom/trust/artifacts \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "attester": "<attester>",
       "body": "<body>"
     }'

The door reaches dataroom through the dataroom tool, which names its 17 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": "get_dataroom_analytic_dataroom"
         }
       }
     }'

Dataroom API · All Hanzo APIs · Interactive reference

Publish puts an item on the caller org's trust centre and answers with it.

Request

Response

Examples

On this page