Skip to main content
GET
/
openapi
/
v1
/
etf
/
{code}
/
prices-history
ETF price history
curl --request GET \
  --url https://api.hayinsights.com/openapi/v1/etf/{code}/prices-history \
  --header 'X-API-Key: <api-key>'
{
  "success": true,
  "statusCode": 200,
  "data": [
    {
      "id": 346280,
      "date": "2021-06-14",
      "etfCode": "1306",
      "open": 2065,
      "high": 2068,
      "low": 2051,
      "close": 2056,
      "volume": "573610.000000",
      "currency": "JPY"
    },
    {
      "id": 346281,
      "date": "2021-06-15",
      "etfCode": "1306",
      "open": 2060,
      "high": 2076,
      "low": 2059,
      "close": 2075,
      "volume": "2708520.000000",
      "currency": "JPY"
    }
  ],
  "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

Daily OHLCV price history 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
meta
object

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