---
title: "List of providers"
method: GET
path: "/providers"
tags: ["Providers"]
---

# List of providers

`GET /providers`

Returns all the providers we operate with.
If a provider becomes `disabled`, it is not included in the list.

## Query parameters

- `from_id` string, nullable — the `id` of the provider which the list starts with.
- `from_date` string, date, nullable — Filtering providers by the `updated_at` attribute, starting from this date.
- `country_code` string, nullable — filtering providers by country.
- `mode` 'oauth' | 'web' | 'api' | 'file' — filtering providers by mode.
- `include_fake_providers` boolean — whether you wish to fetch the fake providers.
- `include_provider_fields` boolean — whether you wish to include all provider fields in the provider objects.
- `provider_key_owner` 'client' | 'saltedge' — filtering providers by key owner. When value is set as `client`, only providers with client-set keys will be returned. Please see [Client Provider Keys](/account_information/v5/#client_provider_keys).
- `include_payments_fields` boolean — whether you wish to include `supported_payment_fields` and `required_payment_fields`

## Response `200`

OK

- ProvidersResponse
  - `data` Provider[]
    - `id` string, required — the `id` of the provider
    - `code` string, required — provider's code
    - `name` string, required — provider's name
    - `mode` string, required — possible values are: - `oauth` -- access through the bank's dedicated API (`regulated: true`). The user is redirected to the bank's page for authorization. For more details, check [OAuth providers](#oauth_providers). - `web` -- access through the bank's WEB interface using screen scraping technology. Therefore, the user undergoes the same authorization flow as in the bank's web interface with an identical set of credentials. - `api` -- access through a dedicated (`regulated: true`) or non-dedicated (`regulated: false`) bank's API. Some required credentials fields might be present which the user should complete (IBAN, username, etc.). In case of a dedicated API, an [interactive redirect](#connections-interactive) might be present, but there are required credentials fields which the user should complete (IBAN, username, etc.). Using these credentials, we authorize the user on the bank's side. - `file` -- access through uploading a file of certain format (XLS, CSV, etc.), which is processed to extract information about accounts and transactions.
    - `status` string, required — possible values: `active`, `inactive`, `disabled` - The providers with the `inactive` status are returned on the [providers list](#providers-list) endpoint, but are not visible on the Connect widget for the end-users. - The providers with `disabled` status are neither returned on the [providers list](#providers-list) endpoint, nor visible on the Connect widget for end-users.
    - `automatic_fetch` boolean, required — whether the provider's connections can be automatically fetched. However, its performance also depends on `optional_interactivity` flag
    - `dynamic_registration_code` string — the dynamic registration code assigned to the Provider
    - `group_code` string — the code of the group to which the Provider belongs
    - `group_name` string — it can be equal to `provider_code`, but may also change independently, regardless of the `provider_code`
    - `hub` string — the hub that the Provider is affiliated with
    - `customer_notified_on_sign_in` boolean, required — whether the provider will notify the customer on log in attempt
    - `interactive` boolean, required — whether the provider requires interactive input
    - `identification_mode` 'client' | 'saltedge', required — whether the request to the provider is made with your [authorization headers](/account_information/v5/#client_provider_keys) or with Salt Edge's.
    - `instruction` string, required — guidance on how to connect the bank
    - `home_url` string, required — the URL of the main page of the provider
    - `login_url` string, required — point of entrance to provider's login web interface
    - `logo_url` string, required — the URL for the provider logo, may have a placeholder for providers with missing logos
    - `country_code` string, required — code of the provider's country
    - `refresh_timeout` integer, required — amount of time (in minutes) after which the provider's connections are allowed to be refreshed
    - `holder_info` string[], required — contains information on the account holder details that can be fetched from this provider
    - `max_consent_days` integer, required — maximum allowed consent duration. If it is `null`, then there are no limits
    - `created_at` string, date-time, required — time and date when the provider was integrated
    - `updated_at` string, date-time, required — the last time when any of provider's attributes were changed
    - `timezone` string, required — time zone data of capital/major city in a region corresponding to the provider
    - `max_interactive_delay` integer, required — delay in seconds before `InteractiveAdapterTimeout` error will be raised
    - `optional_interactivity` boolean, required — provider which supports flipping of the `interactive` and `automatic_fetch` flags after connect
    - `regulated` boolean, required — Whether the provider is integrated via a regulated channel under Open Banking/PSD2
    - `max_fetch_interval` integer, required — Maximum period of days that a provider can return from its interface
    - `custom_pendings` boolean — Equals to `true` if the provider supports a custom pending logic. For example, when the transactions for the last 7 days are marked as pending. Usually implemented to avoid the generation of duplicated transactions due to inconsistent transaction information returned by the bank.
    - `custom_pendings_period` integer — Populated when `custom_pendings` is `true`. Shows the number of days according to the custom pending period implemented in the provider.
    - `supported_fetch_scopes` string[], required — array of strings with supported `fetch_scopes`
    - `supported_account_extra_fields` string[], required — array of possible [account extra](#accounts-extra) fields to be fetched
    - `supported_transaction_extra_fields` string[], required — array of possible [transaction extra](#transactions-extra) fields to be fetched
    - `supported_account_natures` string[], required — array of possible [account natures](#accounts-attributes) to be fetched
    - `supported_account_types` string[], required
    - `identification_codes` string[], required — List of codes identifying supported branches of a specific provider. It may include BLZ(Germany), ABI+CAB(Italy), Branch Codes(France) etc.
    - `bic_codes` string[], required — List of BIC codes identifying supported branches of a specific provider.
    - `supported_iframe_embedding` true | false, required
    - `payment_templates` string[], required — identifiers of the [payment templates](/payment_initiation/v1/#payment_templates) that are supported by this provider
    - `supported_payment_fields` object — if these fields are passed, they will be used by the provider. Otherwise, the payment will we processed even without them
    - `required_payment_fields` object — mandatory payment attributes. If any of these fields are not passed, the payment will not be initiated successfully
  - `meta` MetaObject — Metaobject that contains information about pagination.
    - `next_id` string
    - `next_page` string

## Other responses

- `400` — Sending a date value that does not fit in admissible range

---

[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/versions/f18f4f36d0b3/schema)