Skip to main content
Most Astra API endpoints return localized text fields such as displayName and description. By default, these fields are returned in English (US). You can request a different locale by adding a language query parameter to any supported endpoint, making it straightforward to build apps for audiences around the world.

​
Using the language parameter

Append ?language=<locale> to any supported endpoint. For example, to fetch agent data in Japanese: 
curl "https://astra.teamfortuna.xyz/v1/agents?language=ja-JP" \
  -H "User-Agent: my-app/1.0.0 (+https://example.com)"

​
Supported locales

Locale codeLanguage / Region
ar-AEArabic (UAE)
de-DEGerman (Germany)
en-USEnglish (US) — default
es-ESSpanish (Spain)
es-MXSpanish (Mexico)
fr-FRFrench (France)
id-IDIndonesian (Indonesia)
it-ITItalian (Italy)
ja-JPJapanese (Japan)
ko-KRKorean (Korea)
pl-PLPolish (Poland)
pt-BRPortuguese (Brazil)
ru-RURussian (Russia)
th-THThai (Thailand)
tr-TRTurkish (Turkey)
vi-VNVietnamese (Vietnam)
zh-CNChinese Simplified (China)
zh-TWChinese Traditional (Taiwan)

​
Fetching all locales at once

Pass ?language=all to receive data for every supported locale in a single response. When you use this option, string fields like displayName and description are returned as objects keyed by locale code instead of plain strings. 
curl "https://astra.teamfortuna.xyz/v1/agents?language=all" \
  -H "User-Agent: my-app/1.0.0 (+https://example.com)"
Example response with ?language=all: 
{
  "status": 200,
  "data": [
    {
      "uuid": "e370fa57-4757-3604-3648-499e1f642d3f",
      "displayName": {
        "ar-AE": "بريمو",
        "de-DE": "Primo",
        "en-US": "Primo",
        "es-ES": "Primo",
        "ja-JP": "プリモ",
        "ko-KR": "프리모",
        "zh-CN": "普里莫",
        "zh-TW": "普里莫"
      },
      "description": {
        "en-US": "A duelist who manipulates earth and granite...",
        "ja-JP": "地球と花崗岩を操るデュエリスト..."
      }
    }
  ]
}
When the language parameter is omitted, the API returns en-US by default.

​
Localization string tables

Raw locale string data for all in-game text is available via the /v1/locres endpoint. This is useful if you need low-level access to the game’s full localization tables rather than per-asset translations. See the locres API reference for details.