Skip to main content
POST
Store a complete Triage submission or follow-on revision

Authorizations

Authorization
string
header
required

Client credentials, the production model: server-to-server, short-lived tokens, least-privilege scopes, rotation by issuing a new client secret.

Scopes

intents:write

Create, patch, plan, preflight and enrich intents.

Body

application/json

Complete source-reported Triage capture. Semantic validation also checks answer types against definitions, branch visibility, option IDs, parent references and timings. Follow-ons preserve original diagnostics; change requests get a new linked Intent ID.

schema_version
any
required
environment
any
required
source
object
required
kind
enum<string>
required
Available options:
initial,
follow_on,
change_request
requester
object
required
context
object
required
questionnaire
any
required
responses
any[]
required
Required array length: 1 - 100 elements
events
object[]
required
Maximum array length: 2000
decision
any
required
target
object
required if kind = follow_on
work
any
required if kind = change_request
metadata
object

Response

Identical source revision replayed; no new record or revision.

intent_id
string
required
Pattern: ^[A-Za-z0-9_.:-]{1,160}$
intent_version
integer
required
Required range: x >= 1
stored_at
string<date-time>
required
content_sha256
string
required
Pattern: ^[a-f0-9]{64}$
replayed
boolean
required