> ## 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 metric data for multiple projects > Use this endpoint to retrieve metric data for multiple projects. You can get specific metric for all projects by omitting `project_ids` or using `project_ids=all`. This endpoint supports partial success - if some of the requested entities (projects, chains, or products) are invalid or if a metric is not available for a specific project, the endpoint will return data for the valid entities and include an `errors` array with details about the issues. ## OpenAPI ````yaml /api-reference/openapi.json get /v2/metrics/{metric_id} 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/metrics/{metric_id}: get: tags: - Metrics summary: Get metric data for multiple projects description: > Use this endpoint to retrieve metric data for multiple projects. You can get specific metric for all projects by omitting `project_ids` or using `project_ids=all`. This endpoint supports partial success - if some of the requested entities (projects, chains, or products) are invalid or if a metric is not available for a specific project, the endpoint will return data for the valid entities and include an `errors` array with details about the issues. parameters: - name: metric_id in: path description: >- Allows you to select one of the metrics available. The full list is available on the metrics endpoint (see above). required: true schema: type: string - name: project_ids in: query description: > Allows you to select one or more of the projects available for a specific metric. When including multiple projects, separate each one with a comma. Example: `aave,uniswap`. You can fetch all available projects for the respective metric by omitting this parameter or using value `all`. required: false explode: false schema: type: array items: type: string - name: chain_ids in: query description: > List of chains to include according to projects chain availability. Allows you to select one or more of the chains available for a specific project. When including multiple chains, separate each one with a comma. Example: `ethereum,base`. The full list of available chains can be retrieved from the projects/:project_id endpoint. explode: false schema: type: array items: type: string example: - ethereum - base - name: product_ids in: query description: > List of products to include according to projects product availability. Allows you to select one or more of the products available for a specific project. When including multiple products, separate each one with a comma. Example: `usdc,usdt`. The full list of available products can be retrieved from the projects endpoint. explode: false schema: type: array items: type: string example: - usdc - usdt - name: market_sector_ids in: query description: > List of market sector IDs to filter projects by. Allows you to select one or more market sectors to filter the results. Only projects belonging to any of the specified market sectors will be included. When including multiple market sectors, separate each one with a comma. Example: `blockchains-l1,lending`. The full list of available market sectors can be retrieved from the `/v2/market-sectors` endpoint. explode: false schema: type: array items: type: string example: - blockchains-l1 - lending - name: start in: query schema: type: string format: date description: >- Allows you to select the start date for the query. If no start is selected, the query defaults to launch date or the first date for which there is data available for the chosen metric(s). - name: end in: query schema: type: string format: date description: >- Allows you to select the end date for the query. If no end is selected, the query defaults to the latest date for which there is data available for the chosen metric(s). - name: assets_bridged in: query description: > Include bridged assets in asset metrics Controls whether bridged asset values are included when calculating asset-related metrics (e.g. `asset_market_cap_circulating`, `asset_transfer_volume`). Set to `false` to exclude bridged assets and only count native asset values. Defaults to `true`. schema: type: boolean default: true responses: '200': description: OK content: application/json: schema: type: object properties: data: type: array items: type: object properties: timestamp: type: string description: Returns the historical date for a given metric(s). project_id: type: string description: Returns the project ID. project_name: type: string description: >- Returns the project name used on the web application. metric_id: type: string description: Returns the chosen metric for the project(s). value: type: string description: Returns the value of the chosen metric. errors: type: array description: > Optional array of errors that occurred during request processing. Only present if some requested entities were invalid or unavailable. The endpoint returns data for valid entities even when errors are present, allowing partial success. 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 components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: string ````