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.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The import run id returned by the enqueue.
uuidThe tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/directory/importRuns/497f6eca-6276-4993-bfeb-53cbbbba6f08"{
"id": "00000000-0000-0000-0000-000000000000",
"provider": "string",
"integrationConfigId": "00000000-0000-0000-0000-000000000000",
"status": "PENDING",
"participantsCreated": 0,
"participantsUpdated": 0,
"participantsExisting": 0,
"participantsFailed": 0,
"contactsUnaffiliated": 0,
"sampleFailures": [
{
"address": "string",
"reason": "string"
}
],
"errorMessage": "string",
"createdAt": 0,
"modifiedAt": 0,
"startedAt": 0,
"completedAt": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Dry-runs a directory import — enumerates the integration's contacts and returns an aggregate report, writing nothing.
Reads the whole contact base of the given integration config through its `IParticipantDirectorySource`, runs each contact through the same environment resolver the live approve gate uses, and aggregates the result — how many contacts would affiliate with an environment, the standalone-vs-chain split, per-attribute coverage (e.g. how many carry a branch), and a sample of contacts that would stay unaffiliated. Use it to gauge data quality before running a real import.
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.