Japanese and English

Company names are returned as nameJa / nameEn, sector names as sectorJa / sectorEn (the sector code is sector or sectorCode), and labels such as report reasons as labelJa / labelEn. There is no need to request each language separately: use the Japanese name for matching against other Japanese sources and the English name for display.

{
  "symbol": "7203",
  "nameJa": "トヨタ自動車",
  "nameEn": "TOYOTA MOTOR CORPORATION",
  "sector": "3700"
}

// /stable/available-sectors?lang=ja
{
  "sectorCode": "3700",
  "sectorJa": "輸送用機器",
  "sectorEn": "Transportation Equipment",
  "label": "輸送用機器"
}

Besides the bilingual fields, some objects carry a single label value (the label in the sector list, the label in the extraordinary-report reason list and similar), and you can choose its language. The order is: the lang parameter (ja / en), then the Accept-Language header (the highest-priority ja or en), then English. With neither, it is English; for Japanese add lang=ja or send Accept-Language: ja. Responses carry Vary: Accept-Language.

# English labels (default)
curl "https://api.zenithcode.net/stable/available-sectors" \
  -H "x-api-key: YOUR_API_KEY"

# Japanese labels
curl "https://api.zenithcode.net/stable/available-sectors?lang=ja" \
  -H "x-api-key: YOUR_API_KEY"

lang only changes label. Bilingual pairs such as nameJa / nameEn and sectorJa / sectorEn are always returned in full regardless of lang.

The OpenAPI document (openapi.json) is written in English; Japanese descriptions sit alongside in the x-description-ja extension. These docs and the API Viewer show whichever matches your display language.