Skip to main content
POST
Validate intent against platform requirements

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.

Body

application/json
intent_id
string
required

Minted at the decision and carried unchanged into every destination record. Fits a 64-character client-supplied id field, which is how the same id finds the record in either direction.

Pattern: ^[A-Za-z0-9_-]{10,64}$
Example:

"itn_7f3aK2mQ9xLp"

platform
string
required

Response

OK

intent_id
string
required

Minted at the decision and carried unchanged into every destination record. Fits a 64-character client-supplied id field, which is how the same id finds the record in either direction.

Pattern: ^[A-Za-z0-9_-]{10,64}$
Example:

"itn_7f3aK2mQ9xLp"

platform
string
required
profile
string
required

The MappingProfile validated against.

ok
boolean
required
missing_fields
string[]
required