FruxonDocs
ApiKnowledge bases

Settles a contradiction by recording a fix, archiving an article, or having the editor rewrite the articles.

`method` says how, with an optional `note`: <list type="bullet"><item>`MARK_FIXED` (the default) — the person already fixed the articles; nothing is written. It becomes RESOLVED, and while the articles read the same later runs do not raise it again.</item><item>`ARCHIVE` with `documentId` — the article is out of date as a whole. It is archived at once and leaves search at the next publish; the contradiction becomes RESOLVED.</item><item>`ALIGN_TO_SIDE` with `documentId` — that article is right. The base's editor rewrites each of the others to agree with it.</item><item>`ADD_CONDITION` with `condition` — each is right depending on it. The editor adds it to every article.</item></list> The editor's rewrites run in the background: the contradiction becomes RESOLVING, each rewritten article keeps serving what it says now, and each rewrite is held for review in Suggested changes. Once every rewrite is decided it becomes RESOLVED if all were approved, and OPEN again otherwise, with what the editor did with each article in `corrections`. Refused with 400 when the base's editor cannot run, and 409 when it is no longer open.

POST
/v1/tenants/{tenant}/knowledgeBases/{knowledgeBase}/contradictions/{contradiction}:resolve

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

knowledgeBase*string

The knowledge base id.

Formatuuid
contradiction*string

The contradiction id.

Formatuuid
tenant*string

The tenant identifier

Request Body

How to settle it, and an optional note.

note?string|null

Why, in the person's words — what they fixed, or why the articles do not actually disagree. Optional.

method?string

How: MARK_FIXED (the default — the person already fixed it), ALIGN_TO_SIDE, ADD_CONDITION or ARCHIVE.

Value in"UNSPECIFIED" | "MARK_FIXED" | "ALIGN_TO_SIDE" | "ADD_CONDITION" | "ARCHIVE"
documentId?string|null

For ALIGN_TO_SIDE, the article that is right; for ARCHIVE, the article that is out of date.

Formatuuid
condition?string|null

For ADD_CONDITION, what both articles' being right depends on — "if the supplier card names a channel".

[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/knowledgeBases/497f6eca-6276-4993-bfeb-53cbbbba6f08/contradictions/497f6eca-6276-4993-bfeb-53cbbbba6f08:resolve" \  -H "Content-Type: application/json" \  -d '{}'
{
  "id": "00000000-0000-0000-0000-000000000000",
  "knowledgeBaseId": "00000000-0000-0000-0000-000000000000",
  "origin": "FACT_CHECK",
  "title": "string",
  "points": [
    {
      "about": "string",
      "sides": []
    }
  ],
  "documents": [
    {
      "documentId": "00000000-0000-0000-0000-000000000000",
      "title": "string",
      "sectionTitle": "string",
      "status": "DRAFT",
      "changedSince": false
    }
  ],
  "changedSince": false,
  "status": "OPEN",
  "resolution": "BY_PERSON",
  "resolutionNote": "string",
  "resolvedBy": "string",
  "resolvedAt": 0,
  "chosenDocumentId": "00000000-0000-0000-0000-000000000000",
  "condition": "string",
  "resolutionRequestedAt": 0,
  "resolutionCompletedAt": 0,
  "corrections": [
    {
      "documentId": "00000000-0000-0000-0000-000000000000",
      "documentTitle": "string",
      "outcome": "APPLIED",
      "reason": "string",
      "executionRecordId": "00000000-0000-0000-0000-000000000000",
      "review": "WAITING"
    }
  ],
  "runId": "00000000-0000-0000-0000-000000000000",
  "executionRecordId": "00000000-0000-0000-0000-000000000000",
  "firstSeenAt": 0,
  "lastSeenAt": 0
}
{
  "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
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}