Querying screening

screening is populated only on bank reports whose type is SCREENING. See the Screening concept — the field is module‑gated by HasPrescreeningModule.

All examples require a JWT — get one from the homepage first.

Inspect the screening answers

query bankReportScreening($id: UUID!) {
bankReportById(id: $id) {
  id
  type
  screening {
    hasAdministratorsChanges
    hasBankAccountsChanges
    hasStatutesChanges
    signedFile {
      fileName
      fileExtension
      base64
    }
  }
}
}

The three has…Changes fields are the customer's pre‑screening declarations. signedFile is only generated when all three are false — in that case the screening is the deliverable and the customer signs it. If any flag is true, the bank report has transitioned into a full package and the customer is signing that instead, so screening.signedFile will be null. See the Screening concept for the full flow.

When type is not SCREENING, screening is null. When your bank doesn't have the pre‑screening module enabled, projecting screening returns an authorization error.

List recent screening reports

To pull only screening reports, filter on type. Note that bank‑report sort/filter bindings are limited to publishedTime and organizationId — to scope by type you'll need to project all reports and filter client‑side, or list per‑organization and check the type field.

query recentScreeningReports {
bankReports(order: [{ publishedTime: DESC }], first: 50) {
  nodes {
    id
    type
    publishedTime
  }
}
}