---
title: "Get providers"
method: GET
path: "/trading/providers"
tags: ["Trading"]
---

# Get providers

`GET /trading/providers`

## Request

- Base URL: `https://api.fireblocks.io/v1`
- URL: `https://api.fireblocks.io/v1/trading/providers`
- Auth: none declared
- TypeScript: <https://skmtc.dev/fireblocks/apis/fireblocks-api/docs/trading/providers/get.ts> (a function with typed inputs; its response is checked against the schema)

Retrieve a list of all available external providers supporting trading activities through the platform.

**Endpoint Permission:** Owner, Admin, Non-Signing Admin, Signer, Approver, Editor, Viewer.

For detailed information about error codes and troubleshooting, please refer to our [API Error Codes documentation](https://developers.fireblocks.com/reference/api-error-codes).

## Query parameters

- `pageSize` integer
- `pageCursor` string

## Response `200`

Providers response

- ProvidersListResponse
  - `data` TradingProvider[], required: List of available providers
    - union
      - AccountBasedAccessProvider: Provider integrated via Fireblocks connected accounts (`accountBased` is `true`).
        - `id` string, required: Unique identifier for the provider
        - `name` string, required: Display name of the provider
        - `logo` string: URL to the logo image of the provider
        - `accountBased` boolean, required: Indicates whether the provider access model is through accounts or directly
        - `manifest` Manifest, required: The manifest of the provider, describing its supported order, quote, and rate requirements.
          - `order` ManifestOrder, required: Defines requirements for the POST /orders endpoint.
            - `supported` boolean, required: Indicates whether the endpoint is supported by the provider
            - `participantsIdentificationPolicy` ParticipantsIdentificationPolicy: When present on a provider manifest, specifies KYC/AML identification requirements as JSON Schemas. `defaultSchema` is the baseline; `overrides` refine it by `asset`, `rail`, and/or `flowDirection` (see priority below). The most specific matching override applies its `schema` for that request context: it may fully replace `defaultSchema`, or partially override it—when the override `schema` is not provided as a complete standalone definition, fields and rules omitted there continue to follow `defaultSchema`. If this object is omitted from the manifest, the provider imposes no PII requirements through this policy. FirstParty participants are always exempt. Resolution: from overrides that match the request context, choose the most specific (most dimensions matched); break ties by earlier position in the `overrides` array; if none match, use `defaultSchema`. Priority (highest precedence first): 1. asset + rail + flowDirection 2. Any two dimensions: asset+rail, asset+flowDirection, rail+flowDirection 3. Any single dimension: asset, rail, or flowDirection 4. defaultSchema (no override matches)
              - …
            - `supportedParties` ParticipantRelationshipType[]: The participant party types the provider supports for this endpoint.
            - `settlementTypes` SettlementTypeEnum[]: Supported settlement types when creating an order. If present - settlement is required. If absent - no need to provide settlement.
            - `executionTypes` ExecutionRequestDetailsType[], required: Supported execution types when creating an order.
            - `requiresReasonForPayment` boolean: Information about the source and purpose of the funds being transacted. Used by providers that require additional context for compliance and reporting. Provide this field when the provider manifest indicates it is required.
          - `quote` ManifestQuote, required: Defines requirements for the POST /quotes endpoint.
            - `supported` boolean, required: Indicates whether the endpoint is supported by the provider
            - `participantsIdentificationPolicy` ParticipantsIdentificationPolicy: When present on a provider manifest, specifies KYC/AML identification requirements as JSON Schemas. `defaultSchema` is the baseline; `overrides` refine it by `asset`, `rail`, and/or `flowDirection` (see priority below). The most specific matching override applies its `schema` for that request context: it may fully replace `defaultSchema`, or partially override it—when the override `schema` is not provided as a complete standalone definition, fields and rules omitted there continue to follow `defaultSchema`. If this object is omitted from the manifest, the provider imposes no PII requirements through this policy. FirstParty participants are always exempt. Resolution: from overrides that match the request context, choose the most specific (most dimensions matched); break ties by earlier position in the `overrides` array; if none match, use `defaultSchema`. Priority (highest precedence first): 1. asset + rail + flowDirection 2. Any two dimensions: asset+rail, asset+flowDirection, rail+flowDirection 3. Any single dimension: asset, rail, or flowDirection 4. defaultSchema (no override matches)
              - …
            - `supportedParties` ParticipantRelationshipType[]: The participant party types the provider supports for this endpoint.
            - `settlementTypes` DVPSettlementType[]: Supported settlement types when requesting a quote. If present - settlement is required. If absent - no need to provide settlement.
          - `rate` ManifestBase, required: Base manifest schema with common properties
            - `supported` boolean, required: Indicates whether the endpoint is supported by the provider
            - `participantsIdentificationPolicy` ParticipantsIdentificationPolicy: When present on a provider manifest, specifies KYC/AML identification requirements as JSON Schemas. `defaultSchema` is the baseline; `overrides` refine it by `asset`, `rail`, and/or `flowDirection` (see priority below). The most specific matching override applies its `schema` for that request context: it may fully replace `defaultSchema`, or partially override it—when the override `schema` is not provided as a complete standalone definition, fields and rules omitted there continue to follow `defaultSchema`. If this object is omitted from the manifest, the provider imposes no PII requirements through this policy. FirstParty participants are always exempt. Resolution: from overrides that match the request context, choose the most specific (most dimensions matched); break ties by earlier position in the `overrides` array; if none match, use `defaultSchema`. Priority (highest precedence first): 1. asset + rail + flowDirection 2. Any two dimensions: asset+rail, asset+flowDirection, rail+flowDirection 3. Any single dimension: asset, rail, or flowDirection 4. defaultSchema (no override matches)
              - …
            - `supportedParties` ParticipantRelationshipType[]: The participant party types the provider supports for this endpoint.
        - `connected` boolean, required: Whether the provider is currently connected.
        - `accounts` AccountBase[], required
          - `id` string, required: The ID of the account
          - `name` string, required: The name of the account
      - DirectAccessProvider: Provider used without per-account linking (`accountBased` is `false`).
        - `id` string, required: Unique identifier for the provider
        - `name` string, required: Display name of the provider
        - `logo` string: URL to the logo image of the provider
        - `accountBased` boolean, required: Indicates whether the provider access model is through accounts or directly
        - `manifest` Manifest, required: The manifest of the provider, describing its supported order, quote, and rate requirements.
          - `order` ManifestOrder, required: Defines requirements for the POST /orders endpoint.
            - `supported` boolean, required: Indicates whether the endpoint is supported by the provider
            - `participantsIdentificationPolicy` ParticipantsIdentificationPolicy: When present on a provider manifest, specifies KYC/AML identification requirements as JSON Schemas. `defaultSchema` is the baseline; `overrides` refine it by `asset`, `rail`, and/or `flowDirection` (see priority below). The most specific matching override applies its `schema` for that request context: it may fully replace `defaultSchema`, or partially override it—when the override `schema` is not provided as a complete standalone definition, fields and rules omitted there continue to follow `defaultSchema`. If this object is omitted from the manifest, the provider imposes no PII requirements through this policy. FirstParty participants are always exempt. Resolution: from overrides that match the request context, choose the most specific (most dimensions matched); break ties by earlier position in the `overrides` array; if none match, use `defaultSchema`. Priority (highest precedence first): 1. asset + rail + flowDirection 2. Any two dimensions: asset+rail, asset+flowDirection, rail+flowDirection 3. Any single dimension: asset, rail, or flowDirection 4. defaultSchema (no override matches)
              - …
            - `supportedParties` ParticipantRelationshipType[]: The participant party types the provider supports for this endpoint.
            - `settlementTypes` SettlementTypeEnum[]: Supported settlement types when creating an order. If present - settlement is required. If absent - no need to provide settlement.
            - `executionTypes` ExecutionRequestDetailsType[], required: Supported execution types when creating an order.
            - `requiresReasonForPayment` boolean: Information about the source and purpose of the funds being transacted. Used by providers that require additional context for compliance and reporting. Provide this field when the provider manifest indicates it is required.
          - `quote` ManifestQuote, required: Defines requirements for the POST /quotes endpoint.
            - `supported` boolean, required: Indicates whether the endpoint is supported by the provider
            - `participantsIdentificationPolicy` ParticipantsIdentificationPolicy: When present on a provider manifest, specifies KYC/AML identification requirements as JSON Schemas. `defaultSchema` is the baseline; `overrides` refine it by `asset`, `rail`, and/or `flowDirection` (see priority below). The most specific matching override applies its `schema` for that request context: it may fully replace `defaultSchema`, or partially override it—when the override `schema` is not provided as a complete standalone definition, fields and rules omitted there continue to follow `defaultSchema`. If this object is omitted from the manifest, the provider imposes no PII requirements through this policy. FirstParty participants are always exempt. Resolution: from overrides that match the request context, choose the most specific (most dimensions matched); break ties by earlier position in the `overrides` array; if none match, use `defaultSchema`. Priority (highest precedence first): 1. asset + rail + flowDirection 2. Any two dimensions: asset+rail, asset+flowDirection, rail+flowDirection 3. Any single dimension: asset, rail, or flowDirection 4. defaultSchema (no override matches)
              - …
            - `supportedParties` ParticipantRelationshipType[]: The participant party types the provider supports for this endpoint.
            - `settlementTypes` DVPSettlementType[]: Supported settlement types when requesting a quote. If present - settlement is required. If absent - no need to provide settlement.
          - `rate` ManifestBase, required: Base manifest schema with common properties
            - `supported` boolean, required: Indicates whether the endpoint is supported by the provider
            - `participantsIdentificationPolicy` ParticipantsIdentificationPolicy: When present on a provider manifest, specifies KYC/AML identification requirements as JSON Schemas. `defaultSchema` is the baseline; `overrides` refine it by `asset`, `rail`, and/or `flowDirection` (see priority below). The most specific matching override applies its `schema` for that request context: it may fully replace `defaultSchema`, or partially override it—when the override `schema` is not provided as a complete standalone definition, fields and rules omitted there continue to follow `defaultSchema`. If this object is omitted from the manifest, the provider imposes no PII requirements through this policy. FirstParty participants are always exempt. Resolution: from overrides that match the request context, choose the most specific (most dimensions matched); break ties by earlier position in the `overrides` array; if none match, use `defaultSchema`. Priority (highest precedence first): 1. asset + rail + flowDirection 2. Any two dimensions: asset+rail, asset+flowDirection, rail+flowDirection 3. Any single dimension: asset, rail, or flowDirection 4. defaultSchema (no override matches)
              - …
            - `supportedParties` ParticipantRelationshipType[]: The participant party types the provider supports for this endpoint.
        - `approved` boolean: Whether the provider was approved for use
        - `hasTermsOfService` boolean, required: Whether the provider has terms of service
        - `termsOfServiceUrl` string: URL to the terms of service document
        - `privacyPolicyUrl` string: URL to the privacy policy document
  - `total` integer, required: Total number of providers matching the query.
  - `next` string: A cursor for the next page of results, if available.

## Other responses

- `401`: Unauthorized. Missing / invalid JWT token in Authorization header.
- `403`: Forbidden: insufficient permissions, disabled feature, or restricted access.
- `429`: Rate limit exceeded: slow down and retry later.
- `5XX`: Internal error while processing the request.
- `default`: Error Response

---

[API](https://skmtc.dev/fireblocks/apis/fireblocks-api.md) - [All operations](https://skmtc.dev/fireblocks/apis/fireblocks-api/llms.txt) - [OpenAPI document](https://skmtc.dev/fireblocks/apis/fireblocks-api/revisions/4eba9965659a?raw)