---
title: "Get the Crypto screener dataset"
method: GET
path: "/v2/datasets/crypto_screener"
tags: ["Datasets"]
---

# Get the Crypto screener dataset

`GET /v2/datasets/crypto_screener`

Use this endpoint to retrieve the Crypto screener dataset. You can get the whole dataset by omitting all parameters.

Metrics use the following pattern in the response body: `<metric_id>_<interval>_<aggregation>`.

Metric IDs are the same as the ones used in the `/v2/metrics` endpoint.
Intervals are `24h`, `7d`, `30d`, `90d`, `180d`, `365d`, `max`.
Aggregations  are `trend`, `change`, `avg`, `ath`, `atl`.

## Query parameters

- `project_ids` string[]
- `market_sector_ids` string[]
- `order_by` string, string
- `order_direction` string, string
- `limit` number

## Response `200`

OK

- object
  - `data` object — The object containing the data for a successful response. Metric columns are not shown here due to abundant amount of metrics.
    - `project_name` string — The name of the project
    - `project_id` string — The ID of the project
    - `market_sector_id` string — The market sector's ID
    - `market_sector_name` string — The market sector's name

---

[API](https://skmtc.dev/tokenterminal/apis/token-terminal-api.md) · [All operations](https://skmtc.dev/tokenterminal/apis/token-terminal-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/tokenterminal/token-terminal-api/revisions/02245ad77f39/schema)