FruxonDocs
Agent NetworkParticipants

Infers the enrollment target application for a directory import from the source config.

Walks the config's inbound doorways (manual channel bindings and active messaging endpoints) to the active messaging entry points they materialized, and returns the owning application(s). When the config feeds exactly one application, it is returned as the suggestion the sync wizard pre-answers with; zero or several candidates leave the suggestion empty and the UI shows a picker. The tenant's Default application is never suggested by fallback — only when the config explicitly routes to it.

GET
/v1/tenants/{tenant}/directory/importTarget

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

tenant*string

The tenant identifier

Query Parameters

integrationConfigId?string

The tenant integration config the import would enumerate.

Formatuuid

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/directory/importTarget"
{
  "suggestedNetworkId": "00000000-0000-0000-0000-000000000000",
  "suggestedNetworkName": "string",
  "candidates": [
    {
      "networkId": "00000000-0000-0000-0000-000000000000",
      "name": "string",
      "isDefault": false
    }
  ]
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Gets a directory import run by id — poll it to track progress and read the final counters.

Use this endpoint after `POST directory/import` returns `202 Accepted`. It reads the durable import job row for the current tenant and returns the current lifecycle status plus counters captured by the background worker. Pending and running imports have progress metadata only; completed imports include participant-created/existing/failed counts and the bounded failure sample, while failed imports include the captured error message for operator triage.

Audits every network participant in the tenant against the single-turn invariant.

For each agent wired as a network participant, classifies its current revision's `FlowShape` and reports the non-Agent-shaped ones. `findings` is the remediation list; `compliantCount` counts the eligible (Agent-shaped) participants. The tenant scope is applied automatically by the query layer.