Create decision — POST /v1/compliance/accreditation/{id}/decision

POST /v1/compliance/accreditation/{id}/decision

Compliance → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/compliance/accreditation/{id}/decision`
Method	`POST`
Operation	`post_compliance_accreditation_by_id_decision`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Records an org reviewer's decision on an accreditation record — a reviewer confirmation, a provider verification the reviewer has evidence of (a CPA/attorney letter, a verifier report), a rejection, or an expiry. ROLE-GATED (an org admin or platform reviewer) and ATTRIBUTED: the reviewer's identity is recorded as ReviewerSub and audited. Human-in-the-loop: the platform never confirms on its own, and even a provider_verified state carries the reviewer who recorded it.

Request

3 fields, body application/json (required).

Field	In	Type	Required	Description
`id`	path	string	yes	ID is the accreditation record to decide, from the path.
`id`	body	string	—	ID is the accreditation record to decide, from the path.
`status`	body	string	—	Status is the decision being recorded: reviewer_confirmed, provider_verified, rejected, or expired.

Response

Status	Body	Meaning
`200`	compliance.accView	ok
`default`	problem-details	refused

200 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 decision <id>

.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.postComplianceAccreditationByIdDecision({ id: 'id', id: "<id>", status: "<status>" });

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_by_id_decision(id='id', id="<id>", status="<status>")

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

resp, _, err := client.ComplianceAPI.PostComplianceAccreditationByIdDecision(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_by_id_decision(&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).postComplianceAccreditationByIdDecision();

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

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?

PreviousList verifications NextCreate accreditation