This file event notifies your application when a file’s tag has been changed either by constraints set within the pipeline or manually by a human validator.
When the verification step is enabled for a given tag, a user with the validator role has the ability of setting a different tag. This is an explicit action that is performed through a context menu in our web application. You can access this option via the File Verification view.
Example JSON Payload
{
"event_id": "(UUID format) - Unique identifier for the event.",
"event_type": "Describes the type of event that occurred.",
"event_time": "(floating-point numeric timestamp) - Unix timestamp representing the time when the event occurred, including milliseconds.",
"event": {
"event_name": "Name of the specific event.",
"event_type": "Type of the event, often matching or related to the outer event_type.",
"company_id": "(UUID format) - Unique identifier for the company involved in the event.",
"company_name": "Name of the company involved in the event.",
"file_id": "(UUID format) - Unique identifier for the file associated with the event.",
"previous_tag_id": "(UUID format) - Unique identifier for the file's previous tag.",
"previous_tag_name": "Textual description of the previous tag or 'null' if none existed.",
"proposed_tag_id": "(UUID format) - Unique identifier for the proposed new tag for the file.",
"classification_score": "(floating-point numeric value) - Score representing the confidence or relevance of the new tag, typically between 0.0 and 1.0.",
"new_tag_id": "(UUID format) - Unique identifier for the newly assigned tag to the file.",
"new_tag_name": "Name of the newly assigned tag."
}
}
