# Get assets

Query for assets available on the exchange by specific asset ID or name.  If no query parameters are supplied than ALL available assets will be returned.

Endpoint: GET /api/v1/assets
Version: v1.0.3

## Query parameters:

  - `id` (string)
    ID of asset to query for.

  - `name` (string)
    Filters assets by name. Returns assets where the name is an exact match or contains the provided substring. Matching is case-sensitive.

## Response 200 fields (application/json):

  - `id` (string)
    Exchange assigned ID of asset.
    Example: "78901949717282824"

  - `status` (string)
    Current asset state.
    Enum: "DISABLED", "ACTIVE", "INVALID"

  - `fields` (object)

  - `fields.name` (string)
    Human readable name of the asset.
    Example: "BTC"

  - `fields.min_transfer_qty` (string)
    The minimum amount of an asset that can be transferred in a single transaction, specific to each asset.
    Example: "1000.01"

  - `fields.max_transfer_qty` (string)
    The maximum amount of an asset that can be transferred in a single transaction, specific to each asset.
    Example: "9999.99"

  - `fields.flags` (array)
    A platform-defined value that provides additional metadata or classification for the asset. This flag is used to denote specific attributes or roles associated with the asset within the exchange ecosystem.
-  Indicates that the asset is the default reference asset for the exchange. It serves as the primary asset for settling trades by default and is used as the basis for calculating fees.
-  Indicates if the asset is a stablecoin (value pegged to a external source such as fiat currency.
    Enum: "REFERENCE_ASSET", "STABLECOIN"

## Response 400 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 500 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).

## Response 503 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type.
    Example: "about:blank"

  - `title` (string, required)
    A short, human-readable summary of the problem type.
    Example: "An Error Occured"

  - `status` (integer, required)
    The HTTP status code generated by the origin server.
    Example: 400

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.
    Example: "A more detailed sentence about the error"

  - `instance` (string)
    A URI reference that identifies the specific occurrence of the problem.
    Example: "/api/v1/endpoint"

  - `extensions` (object)
    A map for extension members (custom fields not defined by the RFC).