AxonFlow · Schema
HITLCreateRequest
Body for POST /api/v1/hitl/queue. Org/tenant identity comes from the `X-Org-ID` / `X-Tenant-ID` headers, not the body. Source of truth: `platform/agent/hitl/handler.go` (CreateRequestInput).
CompanyAI GovernanceAI AgentsPolicy EnforcementAudit LoggingComplianceMCPOpen Source
Properties
| Name | Type | Description |
|---|---|---|
| client_id | string | |
| user_id | string | |
| original_query | string | The query/action awaiting human review |
| request_type | string | Request classification (e.g. `mcp_query`, `llm_chat`) |
| request_context | object | |
| triggered_policy_id | string | |
| triggered_policy_name | string | |
| trigger_reason | string | |
| severity | string | |
| eu_ai_act_article | string | |
| compliance_framework | string | |
| risk_classification | string | |
| expires_in_seconds | integer | TTL before the request auto-expires |
| notify_url | string | Optional outbound webhook URL fired asynchronously after the request transitions to a terminal state (approved / rejected / overridden / expired). Must use `https://` or `http://`. The platform signs |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/axonflow/json-schema/axonflow-hitlcreate-request-schema.json",
"title": "HITLCreateRequest",
"description": "Body for POST /api/v1/hitl/queue. Org/tenant identity comes from the\n`X-Org-ID` / `X-Tenant-ID` headers, not the body. Source of truth:\n`platform/agent/hitl/handler.go` (CreateRequestInput).\n",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/axonflow-hitl-api-openapi.yml#/components/schemas/HITLCreateRequest",
"type": "object",
"required": [
"client_id",
"original_query",
"request_type",
"triggered_policy_id",
"triggered_policy_name",
"trigger_reason"
],
"properties": {
"client_id": {
"type": "string"
},
"user_id": {
"type": "string"
},
"original_query": {
"type": "string",
"description": "The query/action awaiting human review"
},
"request_type": {
"type": "string",
"description": "Request classification (e.g. `mcp_query`, `llm_chat`)"
},
"request_context": {
"type": "object",
"additionalProperties": true
},
"triggered_policy_id": {
"type": "string"
},
"triggered_policy_name": {
"type": "string"
},
"trigger_reason": {
"type": "string"
},
"severity": {
"type": "string",
"enum": [
"low",
"medium",
"high",
"critical"
]
},
"eu_ai_act_article": {
"type": "string"
},
"compliance_framework": {
"type": "string"
},
"risk_classification": {
"type": "string"
},
"expires_in_seconds": {
"type": "integer",
"description": "TTL before the request auto-expires"
},
"notify_url": {
"type": "string",
"format": "uri",
"description": "Optional outbound webhook URL fired asynchronously after the request\ntransitions to a terminal state (approved / rejected / overridden /\nexpired). Must use `https://` or `http://`. The platform signs the\nenvelope with HMAC-SHA256 over the body keyed by the deployment's\n`AXONFLOW_HITL_WEBHOOK_SIGNING_KEY`, sent as\n`X-AxonFlow-Signature: sha256=<hex>`. See the HITLWebhookEnvelope\nschema and `docs.getaxonflow.com/docs/governance/hitl` for the full\nshape + verification recipe.\n"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/axonflow-hitlcreate-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.