# ETF Sector Exposure

> Returns sector allocation percentages.

`GET https://api.bavest.co/v2/etfs/sectors`

Group: ETFs. Route id: `v2_etfs_sectors`. Included in: Pro, Growth.

## 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

| Name | In | Type | Required | Description |
|---|---|---|---|---|
| `symbol` | query | string | one of symbol, isin | ETF ticker symbol (e.g., `IWDA.AS`). Provide exactly one of symbol or isin; clear the ISIN example before using a symbol. |
| `isin` | query | string | one of symbol, isin | ETF ISIN code (e.g., `IE00B4L5Y983`, iShares Core MSCI World UCITS ETF). Provide exactly one of symbol or isin. Example `IE00B4L5Y983`. |
| `view` | query | string | no | Allocation view. `display` (default) hides rows with negative exposure and scales the remainder to 100. `raw` returns the stored rates, where swap/bond legs and short positions are legitimately negative. Unrecognized values fall back to `display`. One of `display`, `raw`. Default `display`. |

Required: one of `symbol`, `isin`.

## Response

200 Successful response (`application/json`).

| Field | Type | Always present | Description |
|---|---|---|---|
| `data` | object | no |  |
| `data.atDate` | string (date) | no | Observation date for the exposure data. |
| `data.sectorExposure` | array of ETFSectorExposure | no |  |
| `data.sectorExposure[].sector` | string | yes | Sector name. Example: `Technology`. |
| `data.sectorExposure[].exposure` | number (double) | yes | Exposure percentage. Example: `35.62`. |
| `data.sectorExposure[].synthetic` | boolean | no | `true` when the row is Bavest-generated rather than scraped from an issuer breakdown. Applies to products with no published sector allocation to scrape — chiefly crypto and commodity funds. Example: `false`. |
| `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/sectors?isin=IE00B4L5Y983&view=display' \
  -H "x-api-key: $BAVEST_API_KEY"
```

## Example response

```json
{
  "data": {
    "sectorExposure": [
      {
        "sector": "Information Technology",
        "synthetic": false,
        "exposure": 31.39
      },
      {
        "sector": "Financials",
        "synthetic": false,
        "exposure": 15.81
      }
    ],
    "atDate": "2026-09-30"
  },
  "meta": {
    "parameters": {
      "isin": "IE00B4L5Y983"
    },
    "time": 679
  }
}
```

## Errors

| Status | Meaning |
|---|---|
| 400 | Invalid request parameters. Returned when required query parameters are missing, have invalid types, or violate constraints (e.g., providing both symbol and isin when they are mutually exclusive). |
| 401 | Missing or invalid API key. |
| 404 | Resource not found. |
| 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. |
| 503 | Bavest cannot read its data store right now. The security may well have data; retry after the `Retry-After` header interval. |
| 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_sectors
- 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