DEVELOPER GUIDE
Beta
Findings
Overview
A finding is one compliance result produced inside a workflow: a message for a person to read, an optional severity, and, depending on how the workflow owner configured it, a requirement that someone review and annotate it before the workflow can be considered complete.
You read findings, decide what to do about the ones that need attention, and — where you hold permission — record that decision back onto the finding: a note explaining why, then a mark that it’s been reviewed. This guide covers that whole loop, plus attaching supporting documents to a finding.
You manage findings through the Findings API, under this base URL:
https://api.pointservices.com/riskinsight-services-ws/resources
How it fits together
Workflow — the compliance review this whole API is scoped to. It has an id, wfpop_0000000000002082611 in these docs, which every call here takes. It’s the same workflow the Sessions and Workflows guide and the Webhooks guide already work with — findings are one more thing you can read and act on for a workflow you already have.
Finding — one compliance result inside that workflow. It has an id, fndg_0000000000006051384 in these docs. Read the same finding from the flat list, the categorized view, or a direct GET, and you get the same JSON back — the three ways of fetching a finding are interchangeable.
Category — a workflow owner’s own grouping of findings, configured per workflow. A display label, not a stable key — see Reviewing a Finding for why you shouldn’t switch on it.
Review — the state you move a finding through: unreviewed (waiting, or not required at all), then reviewed, with an explanatory note attached. Some findings require review before the workflow is considered complete; some don’t.
Attachment — a supporting document you or the system attached to a finding, such as a screenshot or a source PDF. Metadata and a download link live at their own address; the finding itself only signals whether any exist.
Getting started
New to this API? Start with Getting Started — it walks through fetching a workflow’s findings and reviewing the ones that need attention, start to finish.
Already reading findings and want the review lifecycle in depth, or need to attach documents? Jump to Reviewing a Finding or Attachments directly.