Skip to main content
For new banking report implementations, use Banking Verifications. These endpoints are documented for existing integrations. See Verifications vs. Data APIs to choose your implementation path.
Example reports:
PDFReport PDF
Image of Verification of Assets (VOA) banking report.
PDFReport PDF
Image of Verification of Income (VOI) banking report.
PDFReport PDF
Image of Verification of Assets & Income (VOAI) banking report.

The report object

Report object.

id
string<uuid>

Unique ID of the report object.

user
string<uuid>

ID of the user associated with the report.

reference_id
string<uuid>
deprecated

Report PDF identifier.

generated_at
string<date-time>
deprecated

Timestamp (ISO 8601) when the report was requested.

created_at
string<date-time>

Timestamp (ISO 8601) when the report was requested.

type
enum<string>

The type of report.

  • voa - Verification of Assets
  • voi - Verification of Income
  • voai - Verification of Assets and Income
Available options:
voa,
voi,
voai
status
enum<string>

Progress of report generation.

  • generating - The report is being generated.
  • generated - The report is ready to download.
Available options:
generating,
generated
file_url
string

Download link to the report PDF. Requires Argyle authentication headers.

json_url
string

Download link to the report in JSON. Requires Argyle authentication headers.

accounts
object[]

Not used in banking reports.

last_synced_at
string<date-time> | null

Not used in banking reports.

external_id
string | null

The external_id of the user, otherwise null.

source
string

The source of the report data.

metadata
object

Additional info.