# List all bank account validations

Returns the bank account validations your business has run, sorted by creation date with the most
recent first. Because `POST /bank_account_validation` is chargeable, use this to check whether an
account has already been validated before paying to validate it again.
`country` is matched against the country recorded on the validation request, not against the
beneficiary's current country, so editing a beneficiary does not move its past validations between
filters.

Endpoint: GET /bank_account_validation
Version: 1.0.0
Security: JWT

## Security:

  - `JWT` (unknown)
    http bearer JWT

## Query parameters:

  - `beneficiary_account_id` (string)
    The ID of the beneficiary bank account to filter validations

  - `country` (string)
    The ISO 3166-1 alpha-3 code of the country to filter validations

  - `before` (string)
    Return only resources created at or before this time. Send an [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp with an offset, such as `2025-02-18T12:03:44Z` or `2025-02-18T17:33:44+05:30`. A timestamp without an offset is read as UTC. A bare date (`YYYY-MM-DD`) means the end of that day in UTC (`23:59:59.999999Z`). An invalid value returns `400 Bad Request`. Use this to avoid page drift. See [Pagination parameters](/platform/pagination#parameters) for more details.

  - `after` (string)
    Return only resources created at or after this time. Send an [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp with an offset, such as `2025-01-18T12:03:44Z` or `2025-01-18T17:33:44+05:30`. A timestamp without an offset is read as UTC. A bare date (`YYYY-MM-DD`) means the start of that day in UTC (`00:00:00Z`). An invalid value returns `400 Bad Request`. Use this to avoid page drift. See [Pagination parameters](/platform/pagination#parameters) for more details.

  - `per_page` (integer)
    Number of resources per page. Should be between 1 and 100.

  - `page` (integer)
    Page number for pagination. Starts from 1. Get the next page number from the `next` field in the response.

## Response 200:

  - `200` (unknown)
    List of bank account validations matching the filters

## Response 200 fields (application/json):

  - `data` (array)

  - `data.id` (string)
    The unique identifier for the bank account validation.
    Example: aval_5JU9yv0lGSUP

  - `data.status` (string)
    The status of the bank account validation. This does not mean the bank account is valid or invalid. It means the validation process was successful or failed.
    Enum: "success", "failed"

  - `data.validation_message` (string)
    The message returned by the bank account validation process.
    Example: The account is registered to John Doe

  - `data.fee_charged` (object | null)
    The fee charged for the bank account validation. `null` when no fee was charged.

  - `data.fee_charged.cents` (integer)
    The fee in the smallest unit of `currency_iso` (cents for USD). `100` is $1.00 when `currency_iso` is USD.
    Example: 100

  - `data.fee_charged.currency_iso` (string)
    The currency of the fee, as an uppercase [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) code. Always `USD`.
    Example: USD

  - `page_meta` (object)

  - `page_meta.current` (integer)
    The current page number.
    Example: 2

  - `page_meta.previous` (integer | null)
    The previous page number.
    Example: 1

  - `page_meta.next` (integer | null)
    The next page number.
    Example: 3

  - `page_meta.per_page` (integer)
    The number of items per page.
    Example: 20

  - `page_meta.pages` (integer)
    The total number of pages.
    Example: 10

  - `page_meta.count` (integer)
    The total number of items.
    Example: 200

## Response 400:

  - `400` (unknown)
    Bad Request

## Response 400 fields (application/json):

  - `error` (string)
    Enum: "Bad Request"

  - `message` (string)
    Error message indicating which parameter was invalid