Create accreditation

Records an ASSERTED accreditation state for a subject — the subject's own assertion, with no verifier.

POST /v1/compliance/accreditation

Compliance → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/compliance/accreditation`
Method	`POST`
Operation	`post_compliance_accreditation`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Records an ASSERTED accreditation state for a subject — the subject's own assertion, with no verifier. Every CONFIRMED state (provider_verified, reviewer_confirmed) and every rejected/expired state is a DECISION recorded via the decision endpoint, attributed to the reviewer — a create can never stamp a confirmation. The underlying figures (income, net worth) are never stored; only the method, category, and state.

Request

7 fields, body application/json (required).

Field	In	Type	Required	Description
`basis`	body	string	—	Basis is the qualification category: income, net_worth, professional_license, or entity.
`evidenceDocId`	body	string	—	EvidenceDocID references an evidence document in the org's sealed data room.
`expiresAt`	body	integer (int64)	—	ExpiresAt is the unix second a confirmation ages out; 0 means none.
`method`	body	string	—	Method is how the state was established: self_attested, third_party_letter, or provider_verified.
`note`	body	string	—	Note is a non-PII operator note.
`status`	body	string	—	Status may only be "asserted" (empty reads as asserted); every confirmed, rejected or expired state is recorded via the decision endpoint.
`subjectId`	body	string	—	SubjectID names the subject this record is about; it must exist within the org.

Response

Status	Body	Meaning
`201`	compliance.accView	created
`default`	problem-details	refused

201 body — 11 fields.

Field	In	Type	Always	Description
`basis`	body	string	—	Basis is the qualification category: income, net_worth, professional_license, or entity.
`createdAt`	body	integer (int64)	—	CreatedAt is the unix second the record was created.
`evidenceDocId`	body	string	—	EvidenceDocID references an evidence document in the org's sealed data room.
`expiresAt`	body	integer (int64)	—	ExpiresAt is the unix second a confirmation ages out; 0 means none.
`id`	body	string	—	ID is the accreditation record's opaque id.
`method`	body	string	—	Method is how the state was established: self_attested, third_party_letter, or provider_verified.
`note`	body	string	—	Note is a non-PII operator note.
`reviewerSub`	body	string	—	ReviewerSub is the org user who recorded a decision on this record.
`status`	body	string	—	Status is the tracked state: asserted, provider_verified, reviewer_confirmed, rejected, or expired.
`subjectId`	body	string	—	SubjectID is the opaque id of the subject the record is about.
`updatedAt`	body	integer (int64)	—	UpdatedAt is the unix second the record last changed.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo compliance accreditation create

.ts

.py

.go

.rs

.java

import { Configuration, ComplianceApi } from 'hanzoai';

const api = new ComplianceApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postComplianceAccreditation({ basis: "<basis>", evidenceDocId: "<evidenceDocId>" });

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ComplianceApi(client).post_compliance_accreditation(basis="<basis>", evidence_doc_id="<evidenceDocId>")

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

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

use hanzo_client::apis::{configuration::Configuration, compliance_api};

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

let result = compliance_api::post_compliance_accreditation(&cfg, Default::default()).await?;

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

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

var result = new ComplianceApi(client).postComplianceAccreditation();

curl -X POST https://api.hanzo.ai/v1/compliance/accreditation \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "basis": "<basis>",
       "evidenceDocId": "<evidenceDocId>"
     }'

MCP reaches compliance through the compliance tool, which names its 16 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_compliance_accreditation"
         }
       }
     }'

Compliance API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousCreate decision — POST /v1/compliance/accreditation/{id}/decision NextCreate subjects