KOkobaltlabs
internal

Create Dismissed Risk Label

Label one dismissed risk. 409 when it was already labeled.

The conflict comes from the UNIQUE constraint, not a preceding SELECT: two labelers submitting the same row would both pass a pre-check and one would silently overwrite the other.

post/internal/risk-labeling/labels/{risk_id}

Request

  • Base URL
    https://api.kobaltlabs.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.kobaltlabs.com/internal/risk-labeling/labels/{risk_id}
  • Auth
    none declared

Path parameters

risk_idstring uuid required

Request body

category'ocr_or_av_processing' | 'missing_file_context' | 'bad_guideline' | 'user_preference' | 'compliance_officer_wrong' | 'other' required

Root cause a labeler assigned to a dismissed marketing risk.

Two axes in one list, which is the point. The first three say Kobalt got something wrong. USER_PREFERENCE and COMPLIANCE_OFFICER_WRONG say it did not: the risk was real and correctly raised, and the dismissal is explained by the reviewer either declining it deliberately or getting it wrong. Without those two, both land in OTHER and an eval set reads every one of them as an unexplained false positive.

Stored as a plain VARCHAR (see the model), so adding a member here is a code change and needs no migration.

explanationstring required

Response

Successful Response

statusstring

Changes

No recorded changes to this operation across all 8 revisions of this API.