Skip to main content
GET
Get Run Output

Behavior

  • Returns the run’s structured output as the JSON response body. There is no separate download step.
  • Every object key in the output is snake_case, the same convention as the rest of the API. Values (names, comments, ids, URLs) are returned exactly as the Flow produced them.
  • The fields depend on the Flow. A Name Screening remediation Flow, for example, returns status, alert_id, hits_processed, per_hit (one entry per hit with verdict, reason, basis, rule_resolution, hit_facts, hit_sources and comment), needs_human_review and synced.
  • Only call this once Get Run shows output_ref set on the run.
  • Returns 404 with code RUN_NOT_FOUND if runId does not exist, or belongs to a different customer.
  • Returns 404 with code OUTPUT_NOT_AVAILABLE if the run has not captured structured output — for example if it has not completed yet, or if the Flow doesn’t produce structured output.
  • Returns 413 with code OUTPUT_TOO_LARGE if the output is too large to return in one response. Contact your Diligent representative if you see this.

Authorizations

X-API-KEY
string
header
required

Path Parameters

runId
string
required

The run's id

Response

OK

The structured output of the run. Its fields depend on the Flow; every object key is snake_case.