Skip to main content
GET
/
openapi
/
v1
/
etf
/
{code}
/
info
ETF info
curl --request GET \
  --url https://api.hayinsights.com/openapi/v1/etf/{code}/info \
  --header 'X-API-Key: <api-key>'
{
  "success": true,
  "statusCode": 200,
  "data": {
    "id": 798,
    "listingDate": "2001-07-13",
    "etfCode": "1306",
    "etfName": "NEXT FUNDS TOPIX Exchange Traded Fund",
    "managementCompany": "Nomura Asset Management",
    "indexName": "TOPIX Total Return Index",
    "tradingUnit": 10,
    "trustFee": 0.0505,
    "etfNameJP": "ＮＥＸＴ ＦＵＮＤＳ ＴＯＰＩＸ連動型上場投信",
    "country": "jp",
    "distributionYield": 0.0176,
    "etfType": "Japanese Equity(Market)"
  },
  "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

Exchange ticker for the ETF (e.g. a TSE code like 1306).

Example:

"1306"

Response

Descriptive metadata for the ETF.

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

Core descriptive metadata for a single ETF.

​
meta
object

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