> ## Documentation Index > Fetch the complete documentation index at: https://tokenterminal.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get asset metrics breakdown > Use this endpoint to retrieve aggregated breakdown data for asset metrics across different dimensions (projects, chains, market sectors, etc.). If an empty `metric_ids` array is provided, it defaults to `['asset_price']`. ## OpenAPI ````yaml /api-reference/openapi.json post /v2/assets/{asset_id}/metrics-breakdown openapi: 3.0.0 info: title: Token Terminal API termsOfService: https://tokenterminal.com/terms version: 2.0.0 servers: - url: https://api.tokenterminal.com security: - bearerAuth: [] tags: [] paths: /v2/assets/{asset_id}/metrics-breakdown: post: tags: - Assets summary: Get asset metrics breakdown description: > Use this endpoint to retrieve aggregated breakdown data for asset metrics across different dimensions (projects, chains, market sectors, etc.). If an empty `metric_ids` array is provided, it defaults to `['asset_price']`. parameters: - name: asset_id in: path description: | ID of the asset Allows you to select one of the assets available. The full list is available on the assets endpoint (see above). required: true schema: type: string requestBody: required: true content: application/json: schema: type: object required: - metric_ids - group_by - interval properties: metric_ids: type: array description: > List of metrics to include according to asset metric availability. Allows you to select one or more of the metrics available for a specific asset. If an empty array is provided, it defaults to `['asset_price']`. items: type: string example: - asset_price - asset_holders group_by: type: string description: > Dimension to group the breakdown by. Available options: `assets`, `projects`, `product`, `chains`, `market-sector`, `chain-asset`, `chain-project`, `product+chain`. enum: - assets - projects - product - chains - market-sector - chain-asset - chain-project - product+chain example: assets interval: type: string description: > Time interval for aggregation. Intervals are `24h`, `7d`, `30d`, `90d`, `180d`, `365d`, `max`. enum: - 24h - 7d - 30d - 90d - 180d - 365d - max example: 30d data_ids: type: array description: > List of project data IDs to filter by. Allows you to select one or more projects. When including multiple projects, separate each one with a comma. items: type: string example: - ethereum product_ids: type: array description: > List of product IDs to filter by. Allows you to select one or more products. When including multiple products, separate each one with a comma. items: type: string example: - usdc asset_ids: type: array description: > List of asset IDs to filter by. Allows you to select one or more assets. When including multiple assets, separate each one with a comma. items: type: string chain_ids: type: array description: > List of chain IDs to filter by. Allows you to select one or more chains. When including multiple chains, separate each one with a comma. items: type: string example: - ethereum - base market_sector_ids: type: array description: > List of market sector IDs to filter by. Allows you to select one or more market sectors. When including multiple market sectors, separate each one with a comma. The full list of available market sectors can be retrieved from the `/v2/market-sectors` endpoint. items: type: string example: - blockchains-l1 - lending includeSelf: type: boolean description: | Include the asset itself in the breakdown results. If not specified, defaults to `false`. default: false start: type: string format: date description: > Start date for the breakdown. Allows you to select the start date for the query. If not specified, uses the default start date. end: type: string format: date description: > End date for the breakdown. Allows you to select the end date for the query. If not specified, uses the latest available date. ignore_threshold: type: boolean description: | Ignore metric thresholds when calculating breakdowns. If not specified, defaults to `false`. default: false responses: '200': description: OK content: application/json: schema: type: object properties: data: type: array items: type: object properties: asset_id: type: string nullable: true description: Asset ID (present when group_by includes assets). data_id: type: string nullable: true description: >- Project data ID (present when group_by includes projects). product_id: type: string nullable: true description: >- Product ID (present when group_by includes products). chain_id: type: string nullable: true description: Chain ID (present when group_by includes chains). market_sector_id: type: string nullable: true description: >- Market sector ID (present when group_by includes market sectors). metrics: type: object description: Map of metric IDs to their breakdown data. additionalProperties: type: object properties: latest: type: number description: Latest value for the metric. avg: type: number description: >- Average value for the metric over the interval. sum: type: number description: >- Sum of values for the metric over the interval. change: type: number nullable: true description: >- Percentage change compared to the previous period. trend: type: number nullable: true description: Trend indicator comparing two time windows. errors: type: array items: oneOf: - type: object required: - code - field - value properties: code: type: string enum: - NOT_FOUND description: Error code indicating the entity was not found field: type: string enum: - project_ids - metric_ids - chain_ids - product_ids - market_sector_ids description: >- The request parameter field that contained the invalid value value: type: string description: The invalid ID value that was not found example: code: NOT_FOUND field: project_ids value: invalid-project - type: object required: - code - project_id - metric_id properties: code: type: string enum: - METRIC_NOT_AVAILABLE description: >- Error code indicating the metric is not available for the specified project project_id: type: string description: >- The project ID that does not have the metric available metric_id: type: string description: >- The metric ID that is not available for the project example: code: METRIC_NOT_AVAILABLE project_id: aave metric_id: tvl '400': description: Bad Request content: application/json: schema: type: object properties: code: type: string message: type: string meta: type: object components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: string ````