Querying administrator changes

administratorChanges wraps a list of AdministratorChange — an interface with two concrete implementations (BoardMemberChange and ExternalAdministratorChange). See the Administrator changes concept for the type hierarchy.

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

Walk the full change list

Use inline fragments to project the type‑specific fields under each concrete implementation.

query bankReportAdministratorChanges($id: UUID!) {
bankReportById(id: $id) {
  id
  administratorChanges {
    administratorChange {
      id
      isNew
      isLeaving
      isAuthorizedSignatory
      isAuthorizedSignatoryChanged
      hasRolesChanged
      hasChanged
      attorneyChanges {
        rights
        bankCard
        hasChanged
        bankAccount {
          accountName
          registrationNumber
          accountNumber
        }
      }
      ... on BoardMemberChange {
        boardMember {
          id
          user {
            id
            firstname
            lastname
          }
        }
        boardMemberRoleChanges {
          role
        }
      }
      ... on ExternalAdministratorChange {
        externalAdministrator {
          id
          user {
            id
            firstname
            lastname
          }
        }
        externalAdministratorRoleChanges {
          role
        }
      }
    }
  }
}
}

Project the per‑administrator attorney documents

Each administrator carries up to three files describing the attorney setup.

query administratorAttorneyFiles($id: UUID!) {
bankReportById(id: $id) {
  id
  administratorChanges {
    administratorChange {
      id
      informationFile { fileName }
      attorneysFile { fileName base64 }
      signedAttorneysFile { fileName base64 }
    }
  }
}
}

informationFile is a .txt with bookkeeping info. attorneysFile is the unsigned overview PDF, signedAttorneysFile is the signed version. Either or both can be null depending on whether the administrator has attorneys at all.