Skip to main content
GET
/
openapi
/
v1
/
etf
/
nav-growth
/
{code}
ETF NAV growth
curl --request GET \
  --url https://api.hayinsights.com/openapi/v1/etf/nav-growth/{code} \
  --header 'X-API-Key: <api-key>'
{
  "success": true,
  "statusCode": 200,
  "data": {
    "etf1": {
      "etfCode": "VNDAF",
      "data": {
        "3M": [
          {
            "date": "19-03-2026",
            "growthRate": 0,
            "nav": 19934.64
          },
          {
            "date": "20-03-2026",
            "growthRate": 0.07,
            "nav": 19948.69
          }
        ]
      }
    },
    "etf2": {
      "etfCode": "",
      "data": {}
    },
    "vnIndex": {
      "etfCode": "VNINDEX",
      "data": {
        "3M": [
          {
            "date": "19-03-2026",
            "growthRate": 0,
            "nav": 1699.13
          }
        ]
      }
    },
    "periodAvailability": {
      "1M": false,
      "3M": true,
      "6M": true,
      "1Y": true,
      "3Y": true
    },
    "startDate": "18-01-2018"
  },
  "meta": {
    "timestamp": "2026-06-19T08:50:39.000Z"
  }
}

Authorizations

​
X-API-Key
string
header
required

Your HayInsights API key (prefixed apk_). Create and manage keys in the HayInsights dashboard (Account → API keys).

Send it in the X-API-Key header on every request to /openapi/v1/*. Which data domains you may access and your request quota are both governed by the subscription plan attached to the key — see the Plans & features and Rate limits guides.

Path Parameters

​
code
string
required

Vietnamese fund certificate code.

Example:

"VESAF"

Response

NAV-growth series for the fund and the VN-Index.

Standard success envelope shared by every endpoint. Each operation's response wrapper extends this (via allOf) and adds a typed data property.

​
success
boolean
required

Always true for a successful response.

Example:

true

​
statusCode
integer
required

Mirrors the HTTP status code.

Example:

200

​
data
object
required

NAV-growth comparison payload. Returns the NAV-growth series for two funds (etf1, etf2) benchmarked against the VN-Index (vnIndex), the set of available period windows and the series start date. The single-fund endpoint populates etf1 and leaves etf2.etfCode empty.

​
meta
object

Response metadata. Always present; timestamp is the server time the response was generated.