Funds

Fund Metric Names

GET/v2/funds/metrics/names

Returns every metric name available on /v2/funds/metrics, with the unit and a description for each name. Metric families such as calendar year returns are returned as name patterns. Any name that matches a listed pattern is a valid metric name, for example calendar_year_return_2025.

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

No fund identifier is required.

Free in every plan, including the trial.

Authentication

Send your API key in the x-api-key header on every request to https://api.bavest.co. The samples read it from the BAVEST_API_KEY environment variable. Get an API key · Authentication guide

Parameters

This route takes no path or query parameters.

Try it

This route takes no parameters.

GET /v2/funds/metrics/names

Sent only to api.bavest.co for this request; not stored.

Sign in to sendGet an API keySends with the key above, or sign in to use your account's key. Each request counts as one API call.

Response 200

Successful response · application/json

  • dataobject
    • countinteger

      Number of exact metric names (name-pattern families are listed separately and not included in the count)

      Example 51

    • metricsarray of object
    • patternsarray of object

      Metric-name families accepted in addition to the exact names

  • metaobject

    Response envelope metadata.

    • timeinteger

      Server-side processing time in milliseconds

      Example 17

    • parametersobject

      Echo of the request parameters the endpoint resolved

Errors

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

For AI agents: this page as Markdown at /docs/v2_funds_metric_names.md, every route in /llms.txt, the OpenAPI spec at /openapi.json.