Runs one bounded pass of a source's implementation now.
Scans and processes within ceilings rather than draining the source: a request that names none gets a small default, because the first sync an operator presses is usually against a source that has never run, and finding out whether it works should not cost a whole backlog. Draining is what resuming the schedule does. A paused source syncs — a pause withholds the automatic pass, not the operator's own — and the pass is the automation's own, so it takes the same lock, admits idempotently, and is recorded in the same fire log with its cost. The response echoes the ceilings, because a capped pass and a caught-up source otherwise report the same zeroes.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The knowledge base id.
uuidThe knowledge source id.
uuidThe tenant identifier
Optional per-pass ceilings.
Stop admitting after this many genuinely-new items.
int32Stop claiming after this many items across every stage of the pass.
int32Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/knowledgeBases/497f6eca-6276-4993-bfeb-53cbbbba6f08/sources/497f6eca-6276-4993-bfeb-53cbbbba6f08:sync" \ -H "Content-Type: application/json" \ -d '{}'{
"sourceId": "00000000-0000-0000-0000-000000000000",
"triggerId": "00000000-0000-0000-0000-000000000000",
"admitted": 0,
"dispatched": 0,
"alreadyRunning": false,
"maxAdmit": 0,
"maxDispatch": 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
}