Creates or replaces the Application's automatic-enrollment policy.
Full replace. The fallback must be `REQUEST_ACCESS` or `REJECT`, the environment rule must be specified, and the hourly cap at least 1 — anything else is a 400. Applies immediately: senders admitted under `PROVISION` are matched against this policy from the next message on. Save this before flipping an admission select to `PROVISION`; the Network PATCH refuses the enum with no policy in place.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The owning Application id.
uuidThe tenant identifier
The matcher to set.
Environment rule for automatic provisioning. Provider channels use provider-vouched directory facts; signed embed identities use signed host attributes. Only ANY admits a participant with no environment; other rules always assign an environment.
"UNSPECIFIED" | "MATCH_LIST" | "ANY" | "REQUIRE_ASSERTED"Application policy for a sender who does not yet have an access grant. Covers operator-selectable admission behavior; existing revocation and operational failures are handled independently.
"UNSPECIFIED" | "REQUEST_ACCESS" | "REJECT" | "PROVISION"int32Response Body
curl -X PUT "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/provisioningPolicy" \ -H "Content-Type: application/json" \ -d '{}'{
"networkId": "00000000-0000-0000-0000-000000000000",
"configured": false,
"environmentRule": "MATCH_LIST",
"environmentIds": [
"00000000-0000-0000-0000-000000000000"
],
"unmatchedFallback": "REQUEST_ACCESS",
"maxProvisionsPerHour": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Removes the Application's automatic-enrollment policy.
Refused (400) while either admission policy on the Network is still `PROVISION` — flip the admission setting first, so the behaviour change is the one the operator asked for rather than a silently degraded setting.
The Application's run outcomes, latency, tool errors and quality loop over an optional window.
Runs, deliveries, latency, tool calls and judge verdicts are the Application's own production runs, selected on the run's Application: cost-only bookkeeping (the relevance pre-gate, judges, reviews) is not a run, and pre-flight rejections are counted apart from the runs that started. Latency is over completed runs, the newest 20,000 when there are more (`sampled`). Tools are the eight most called plus any other with at least five errors at 10% or more. The review loop — reviews, findings, improvement cards awaiting a decision, the last finished evaluation run — is counted over the Application's runnable member agents. `from`/`to` are Unix ms (half-open), defaulting to the last 30 days; all time is `from=0`.