# Get linked account verifications

Endpoint: GET /linked_accounts/{id}/verifications
Version: 3.63.5
Security: auth_token, api-key

## Path parameters:

  - `id` (string, required)
    The unique identifier of the linked account.

## Query parameters:

  - `offset` (integer)
    The offset value for paging, indicating the initial item number to be returned from the data set satisfying the given criteria. Leave out to fetch the first page of results.

  - `limit` (integer)
    The limit of the results for paging, starting at the offset. Limit is always capped at 100.

  - `state` (array)
    Enum: "PENDING", "VERIFIED", "REJECTED"

## Response 200 fields (application/json):

  - `verificationRuns` (array)

  - `verificationRuns.id` (string)
    The unique identifier of the linked account verification

  - `verificationRuns.state` (string, required)
    The state of the linked account verification
    Enum: "PENDING", "VERIFIED", "REJECTED"

  - `verificationRuns.completedTimestamp` (integer)
    The timestamp when the verification was completed, expressed in Epoch timestamp using millisecond precision.

  - `verificationRuns.verificationSteps` (array)

  - `verificationRuns.verificationSteps.step` (string)
    Enum: "TRANSFER_INSTRUCTION", "USER_DECLARATION_SCA_CHALLENGE", "INTERNAL_CHECKS", "MICRO_DEPOSIT"

  - `verificationRuns.verificationSteps.details` (any)

  - `verificationRuns.verificationSteps.status` (string)
    Enum: "PENDING_USER", "PENDING_REVIEW", "PENDING_EXECUTION", "REJECTED", "COMPLETED"

  - `verificationRuns.verificationSteps.completedTimestamp` (integer)
    The timestamp when the card will be renewed, expressed in Epoch timestamp using millisecond precision.

  - `verificationRuns.overriddenReason` (string)
    Optional field for users to provide a reason for overriding the verification steps

  - `count` (integer)
    The total number of records (excluding the paging limit).

  - `responseCount` (integer)
    The total number of records returned in this response (always capped at 100).

## Response 400 fields (application/json):

  - `message` (string)
    When present helps to identify and fix the problem.

  - `syntaxErrors` (object)
    Is returned as part of an HTTP error response whenever a syntax error is detected. A list of the fields together with their syntax error will be provided.

  - `syntaxErrors.invalidFields` (array)

  - `syntaxErrors.invalidFields.params` (array)

  - `syntaxErrors.invalidFields.fieldName` (string)

  - `syntaxErrors.invalidFields.error` (string)
    Enum: "REQUIRED", "HAS_TEXT", "REQUIRES", "SIZE", "RANGE", "IN", "NOT_IN", "REGEX", "EXACTLY", "AT_LEAST", "AT_MOST", "ALL_OR_NONE"

## Response 403 fields (application/json):

  - `errorCode` (string)
    Enum: "STEP_UP_REQUIRED", "ACCESS_TOKEN_REQUIRED"

## Response default fields (application/json):

  - `code` (string)

  - `message` (string)


## Response 401 fields

## Response 429 fields

## Response 500 fields

## Response 503 fields