---
title: "Attempt object"
method: GET
path: "/attempts/{attempt_id}"
tags: ["Attempts"]
---

# Attempt object

`GET /attempts/{attempt_id}`

Returns a single attempt object.

## Path parameters

- `attempt_id` string, required — the `id` of attempt

## Query parameters

- `connection_id` string, required — the `id` of the connection whose attempts are to be fetched

## Response `200`

OK

- AttemptResponse
  - `data` Attempt
    - `api_mode` 'app' | 'service', required — the API mode of the customer that queried the API.
    - `api_version` string, required — the API version in which the attempt was created
    - `automatic_fetch` boolean, required — whether the connection related to the attempt can be automatically fetched
    - `daily_refresh` boolean, required — latest assigned value for `daily_refresh` in connection
    - `categorize` boolean, required — whether attempt is categorized
    - `created_at` string, date-time, required — when the attempt was made
    - `custom_fields` object, required — the custom fields that had been sent when creating connection/connect\_session/oauth\_provider
    - `device_type` 'desktop' | 'tablet' | 'mobile', required — the type of the device that created the attempt.
    - `remote_ip` string, required — the IP of the device that created the attempt
    - `exclude_accounts` string[], required — the `ids` of accounts that do not need to be refreshed
    - `user_present` boolean, required — whether the request was initiated by the end-user of your application
    - `customer_last_logged_at` string, date-time, required — the datetime when user was last active in your application
    - `fail_at` string, date-time, required — when the attempt failed to finish
    - `fail_error_class` string, required — class of error that triggered the fail for attempt
    - `fail_message` string, required — message that describes the error class
    - `fetch_scopes` string[], required — fetching mode.
    - `finished` boolean, required — whether the connection had finished fetching
    - `finished_recent` boolean, required — whether the connection had finished data for recent range
    - `from_date` string, date, required — date from which the data had been fetched
    - `id` string, required — `id` of the attempt
    - `interactive` boolean, required — whether the connection related to the attempt is interactive
    - `locale` string, required — the language of the Connect widget and of the returned error message(s) in the <a href='http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes' target="_blank">ISO 639-1</a> format. Possible values are: `bg`, `cz`, `de`, `en`, `es-MX`, `es`, `fi`, `fr`, `he`, `hr`, `hu`, `it`, `nl`, `pl`, `pt-BR`, `pt`, `ro`, `ru`, `si`, `sk`, `sv`, `tr`, `uk`, `zh-HK`(Traditional), `zh`(Simplified). Defaults to `en`.
    - `partial` boolean, required — whether the connection was partially fetched
    - `store_credentials` boolean, required — whether the credentials were stored on our side
    - `success_at` string, date-time, required — when the attempt succeeded and finished
    - `to_date` string, date-time, required — date until which the data has been fetched
    - `updated_at` string, date-time, required — when last attempt update occurred
    - `show_consent_confirmation` boolean, required — whether any consent was given for this connection
    - `include_natures` string[], required — the natures of the accounts that need to be fetched
    - `stages` Stage[], required — information about [stages](#attempts-stages) through which the connection has passed
      - `created_at` string, date-time, required — when the stage was created
      - `id` string, required — the `id` of the stage
      - `interactive_fields_names` string[], nullable — the interactive fields that are currently required by the provider. Appears only for the interactive connections
      - `interactive_html` string, nullable — HTML code that shows the current interactive state of the connection. Appears only for the interactive connections
      - `name` 'start' | 'connect' | 'interactive' | 'fetch_holder_info' | 'fetch_accounts' | 'fetch_recent' | 'fetch_full' | 'disconnect' | 'finish', required — the name of the stage.
      - `updated_at` string, date-time, required — when the stage was last updated
    - `unduplication_strategy` string — This parameter mandates how duplicated transactions are managed. Possible values include: `mark_as_pending`, `mark_as_duplicate`, `delete_transactions`. The default is set to `mark_as_pending`. The provided value remains unchanged until another value is sent during [connect_session/reconnect](/account_information/v5/#connections-reconnect) or [connect_session/refresh](/account_information/v5/#connections-refresh). - `mark_as_pending`: leaves identified duplicated transactions in `Pending` status for clients that establish connections with providers having a non-null `custom_pendings_period`. - `mark_as_duplicate`: identifies transactions as duplicated and sets the `duplicated` flag to `true`. - `delete_transactions`: removes identified duplicated transactions.

---

[API](https://skmtc.net/saltedge/apis/salt-edge-account-information-api.md) · [All operations](https://skmtc.net/saltedge/apis/salt-edge-account-information-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/saltedge/salt-edge-account-information-api/revisions/f18f4f36d0b3/schema)