Skip to main content
POST
Generate destination plan from Channel Map + intent

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"

channel
string

Work channel to route. Defaults to payload.channel on the intent.

Examples:

"contingent_hire"

"services_sow"

"permanent_hire"

"signature"

"contract"

"purchase"

platform
string

Explicit destination override, bypassing the Channel Map.

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"

intent_version
integer
required
Required range: x >= 1
channel
string
required
destinations
object[]
required
rationale
string
required

Why this destination was chosen. Deterministic and explainable.