# ETF Metric Names

> Returns every metric name available on `/v2/etfs/metrics`, with the unit and a description for each name.

`GET https://api.bavest.co/v2/etfs/metrics/names`

Group: ETFs. Route id: `v2_etfs_metrics_names`. Free in every plan, including the trial.

## Description

Returns every metric name available on `/v2/etfs/metrics`, with the unit
and a description for each name.

Use these names with the `fields` parameter of `/v2/etfs/metrics`. The
vocabulary is versioned with the API. New metric names may be added over
time and additions are backward compatible.

No ETF identifier is required.

## Authentication

Send your API key in the `x-api-key` header on every request. No key yet? Sign up at https://dashboard.bavest.co/sign-up (free trial). The examples read the key from the `BAVEST_API_KEY` environment variable.

## Parameters

None.

## Response

200 Successful response (`application/json`).

| Field | Type | Always present | Description |
|---|---|---|---|
| `data` | object | no |  |
| `data.count` | integer | no | Total number of registered metric names. Example: `92`. |
| `data.metrics` | array of object | no |  |
| `data.metrics[].name` | string | no | Canonical metric name (snake_case) Example: `beta_one_year_security`. |
| `data.metrics[].unit` | string | no | Unit of measurement (MetricUnitModel value) One of `CURRENCY`, `NUMERIC`, `PERCENTAGE`, `RATIO`, `DATE`, `BOOLEAN`, `YEARS`. Example: `RATIO`. |
| `data.metrics[].description` | string | no | Human-readable description of the metric. Example: `1-year beta of the fund versus S&P 500`. |
| `meta` | ResponseMeta | no | Response envelope metadata. Always present on a 200: `time` is set by `core/response.py` on every successful response. Errors carry the same block, built by the same code, so a client parses one meta shape whether the call succeeded or failed. |
| `meta.time` | integer | no | Server-side processing time in milliseconds. Example: `17`. |
| `meta.parameters` | object | no | Echo of the request parameters the endpoint resolved. |

## Example request

```bash
curl 'https://api.bavest.co/v2/etfs/metrics/names' \
  -H "x-api-key: $BAVEST_API_KEY"
```

## Example response

```json
{
  "data": {
    "count": 104,
    "metrics": [
      {
        "name": "alpha_five_years_category",
        "unit": "RATIO",
        "description": "5-year Jensen's alpha of the fund's category"
      },
      {
        "name": "alpha_five_years_security",
        "unit": "RATIO",
        "description": "5-year Jensen's alpha of the fund"
      }
    ]
  },
  "meta": {
    "time": 57
  }
}
```

## Errors

| Status | Meaning |
|---|---|
| 401 | Missing or invalid API key. |
| 429 | Rate limit exceeded. Retry after the `Retry-After` header interval. |
| 500 | An unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value. |
| 502 | Upstream data provider returned an error or is temporarily unavailable. Retry after a short delay. |
| 504 | The request timed out waiting for a response from the upstream data provider. This may occur for complex queries or during peak load. |
| default | An unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value. |

- `403` from the gateway: the API key is invalid or switched off.
- `429` with message `Limit Exceeded`: the monthly quota of the key is used up. With `Too Many Requests`: the key is throttled, or this route is not in the key's plan. Wait for `Retry-After` when it is sent.

## Links

- HTML page: https://dashboard.bavest.co/docs/v2_etfs_metrics_names
- OpenAPI: https://dashboard.bavest.co/openapi.json (YAML: https://dashboard.bavest.co/openapi.yaml)
- Authentication: https://dashboard.bavest.co/docs/authentication.md
- MCP server for AI agents: https://dashboard.bavest.co/docs/mcp.md
- All routes: https://dashboard.bavest.co/llms.txt